It would seem like a quick workaround for this would be to have some
sort of sanity check script that kills hanging process(es) left over
after a crash. At the very least bonobo-activation-server, since killing
it seems to resolve the issue.
** Changed in: Ubuntu
Sourcepackagename: None =
No processes are left if I use the GNOME menu to log out. This problem
only occurs when the session crashes.
--
Ubuntu 6.06 (amd64), users can't login after restart.
https://launchpad.net/bugs/49594
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Changed in: Ubuntu
Status: Needs Info = Confirmed
--
Ubuntu 6.06 (amd64), users can't login after restart.
https://launchpad.net/bugs/49594
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I do not know whether the same thing happens if I use logout properly, because
I was unable to use logout properly until very recently -- bug 80343.
I'll check this soon.
Another thing: the same problem apparently occurs if the session crashes
(bug 70618). Breaking logins after a crash is not
This happens to me often:
1. I boot the machine, log in
2. after some time I press Ctrl+Alt+Backspace to log out quickly
3. I get a gdm login screen and log in again
4. I get a blank desktop and nothing happens.
If I use ps at point 3, I see a number of processes left over from my
Looks like bonobo-activation-server is at fault here. If I kill bonobo-
activation-server but leave gconfd running, I can log in.
--
Ubuntu 6.06 (amd64), users can't login after restart.
https://launchpad.net/bugs/49594
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Does the same problem happen when you log out *properly*? :) If this
only happens when you forcefully kill X, I doubt the Gnome developers
would be interested in looking into this issue, because recent versions
of gnome depend on a whole whack of background processes that don't get
killed off
Seems like a messed up Gnome configuration to me that's causing it to
hang. Can the users log in to a failsafe session? If so, tr y removing
(or backing up just in case) any .gnome* or .gconf* directories in the
home directories of the users that are having these issues, then restart
X
I've been investigating more and i think the problem is gconfd. I enter
the system by ssh (with X forwarding) and can execute graphical apps
like gftp and others but can't exec nautilus or evolution ,
applicactions of the gnome project. I start nautilus (in background) and
it hangs and i list the
