Bonobo-activation-server sometimes is not killed after session restart, leading to many unexpected problems
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-session (Ubuntu) |
Invalid
|
Medium
|
Ubuntu Desktop Bugs | ||
Hardy |
Invalid
|
Medium
|
Ubuntu Desktop Bugs | ||
libbonobo (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I edit the description of this bug to reflect recent discovery.
After the first sucessfull login, X is restarted using Ctrl+Alt+Backspace or due to a crash, or sometimes even due to normal logout, then either logins don't work anymore, or you can login, but popups warn you that the settings daemon cannot be reached, and the overall aspect of the session changes.
In the first case, the login name/password are accepted by gdm but gnome hangs on load after the login. This does not affect TTY or SSH logins. Restarting X again with Ctrl+Alt+Backspace, but the issue persists. All the users that have logged in at least once can't start the graphical session anymore. In both cases, killing bonobo-
description: | updated |
Changed in gnome-session: | |
importance: | Undecided → Medium |
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 process:
12909 pts/1 S 0:00 /usr/lib/ libgconf2- 4/gconfd- 2 11 gnome-vfs- 2.0/gnome- vfs-daemon --oaf-activate- iid=OAFIID: GNOME_VFS_ Daemon_ Factory --oaf-ior-fd=26 nautilus- cd-burner/ mapping- daemon
12912 ? Sl 0:00 /usr/lib/
12929 pts/1 Sl 0:00 nautilus --browser
12932 pts/1 S 0:00 /usr/lib/
/var/log/syslog
Jun 13 22:16:32 oradio gconfd (radio-12909): comenzando (versión 2.14.0), pid 12909 usuario «radio» /etc/gconf/ gconf.xml. mandatory» a una fuente de configuración de sólo lectura en la posición 0 /home/radio/ .gconf» a una fuente de configuración escribible en la posición 1 /etc/gconf/ gconf.xml. defaults» a una fuente de configuración de sólo lectura en la posición 2Jun 13 22:16:32 oradio gconfd (radio-12909): Se resolvió la dirección «xml:readonly: /var/lib/ gconf/debian. defaults» a una fuente de configuración de sólo lectura en la posición 3 /var/lib/ gconf/defaults» a una fuente de configuración de sólo lectura en la posición 4
Jun 13 22:16:32 oradio gconfd (radio-12909): Se resolvió la dirección «xml:readonly:
Jun 13 22:16:32 oradio gconfd (radio-12909): Se resolvió la dirección «xml:readwrite:
Jun 13 22:16:32 oradio gconfd (radio-12909): Se resolvió la dirección «xml:readonly:
Jun 13 22:16:32 oradio gconfd (radio-12909): Se resolvió la dirección «xml:readonly:
I don't know what's up.