After Gnome Logout, Can't Log Back in

Bug #158755 reported by Mike Mackintosh
6
Affects Status Importance Assigned to Milestone
meta-gnome2 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I suffer from, https://bugs.launchpad.net/ubuntu/+source/meta-gnome2/+bug/151544, also. I don't know if it has anything to do with it. A few people in the forums who are also experiencing the same problem have confirmed this behavior on their rigs too. When you log out, you are brought to the gdm login screen, that works fine. But, when you enter the credentials, and are authenticated, the login proccess begins, but no session is created. It sits without a desktop, no wallpaper, no gnome-panel, just a mouse that you can move around. i let it sit for an hour like that, and nothing happened. It happens if you logout, or restart the desktop manager (Using /etc/init.d/gdm restart or ctrl+alt+backspace). Requiers a a restart from the virtual terminal, because restarting it again, results in the same behavior. So if you want a gui, you have to completley restart.

Revision history for this message
Daniel Hahler (blueyed) wrote :

Thank you for reporting this bug.

You may want to try switching to a virtual console (ctrl-alt-f1), logging in there and then using "top" to see if there is some process hogging the CPU.

I'm marking this bug as duplicate, please refer to bug 151544 and see if you can provide any information there to fix the problem.

Revision history for this message
Daniel Hahler (blueyed) wrote :

Un-duping.
Bug 151544 seems to be about the first login/boot process only.
Are you sure, that this is the problem as you have?
(Please report back what "top" says in another console during the hanging)

Changed in meta-gnome2:
status: Invalid → Incomplete
Revision history for this message
Mike Mackintosh (mike-mackintosh) wrote :

All terminals, 1-6 respectivly, prompt me to login. If i login, and restart GDM, the same exact thing happens. It seems that only the first session is successful. I have this problem only on my AMD64 Laptop, whereas my i386 desktop is running fine.

Let me know if you need the dmesg output, .gnome2/session, .xsession-errors logs or not.

Revision history for this message
cutlerite (cutlerite) wrote :

I have the same issue. I can log in the first time, but if I log out, log in as a different user, I can't log back in as myself again.

I get logged in, but if I ever log out, I can never go back. I am running an AMD64 Desktop.

Revision history for this message
Boyakasha (tom-dalling) wrote :

I also have this issue on both my home computer (AMD64) and work computer (i386).

I went hunting through logs and all that stood out was "Refusing to initialise GTK+" in .xsession-errors, and something about how it shouldn't be run setuid or setgid.

I tried logging in with xdm instead of gdm but that didn't work either.

Revision history for this message
Andreas Moog (ampelbein) wrote : Old standing report

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.

 status incomplete
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkit6uMACgkQ06FgkPZwicSsAgCgkI25q3SE59BKf3jQf1mDwFDf
HHcAnA7QXkyZKXWPZM2JNL7bu9Zrincb
=LMeY
-----END PGP SIGNATURE-----

Revision history for this message
Andreas Moog (ampelbein) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in meta-gnome2:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.