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 t
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
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.
--
After Gnome Logout, Can't Log Back in
https://bugs.launchpad.net
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
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 (Ubuntu)
Status: Invalid => Incomplete
--
After Gnome Logout
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
