Bugzilla – Bug 340986
bonobo-activation-server still alive after a X crash makes applets unusable
Last modified: 2008-06-11 20:49:08 UTC
I killed the X server with Ctrl-Alt-Backspace. Now, after restarting GNOME, the default panel entries are gone. If I right-click the, then "Add to Panel", select "Main Menu" and "Add", the following message window appears: The panel encountered a problem while loading "OAFIID:GNOME_MainMenu". [ Don't deleste ] [ Delete ] And restoring the panel contents is not possible. I probably must kill 'gconfd' or something like that.
Run /usr/lib/gnome-main-menu/main-menu on the command line and add to the panel again. See if there are any errors.
/usr/lib/gnome-main-menu/main-menu seems to wait for a timeout; after approx. 60s. it exits without any message or visible effect.
Did you install from a live CD?
No, my current installation is a 10.2 -> 10.3 update and since ~2 weeks it worked nicely. Obviously, I destroyed something by pressing C-A-Backspace and thus forcing an X server crash. Later the day, I will probably reboot after running an online update. [BTW, it happened by accident ;) I remember we discussed disabling this keycombo--I hope we do this now for new installations.]
After rebooting I was able to add panel applications anew.
Not sure exactly what else to do with this one - maybe a process got kill with X at exactly the wrong time ie writing out I/O.
Timo observed a similar behavior in the past. I guess if you try several times in a row, you should be able to reproduce it.
Is this still an issue?
I do not know (maybe, qa guys can reproduce it). I merely described what happened to me. In the meantime I did not crash the X server again. I'll surely update my workstation vom 10.3 to 11.0. Let's see what happens
The problem most likely is that the bonobo activation server from the previous X session is still alive, and so applets don't work. It's still valid in 11.0, I believe (I can reproduce the problem in jhbuild from time to time). If someone who had this issue and who can reproduce this issue can confirm this (just do a ps before logging in again), that'd be great.
*** This bug has been marked as a duplicate of bug 331577 ***