GNOME Bugzilla – Bug 105958
bonobo-activation-server crashes on startup
Last modified: 2004-12-22 21:47:04 UTC
I updated some packages yesterday and today my gnome-session won't start properly, the gnome-settings daemon and panel fail to start because they cannot connect to the bonobo-activation-server. When I try to run that manually it segfaults. I recompiled with -O2 -g and got a not very spectacular backtrace (I should issue 'bt' to gdb, right?):
+ Trace 33784
This happens with both bonobo-activation 2.2.0 and 2.2.1 (and 2.2.0 worked fine yesterday). I found the function in question and there was this FIXME:log errors comment. Obviously any real error messages never get created. I think this is some sort of config error on my part, but I don't know where to start looking based on just this backtrace. It's a bug somewhere as well ofcourse, since programs should never crash.
This is rather odd. Where did you get your packages from ? Can you quit X, re-login using a failsafe-xterm session; do a 'bonobo-slay', then: strace -f bonobo-activation >& /tmp/log & and then run: gnome-session. And post a link to that log here. Thanks.
I have installed Gnome 2.2 from sources from the gnome ftp site. "Packages" means "official source packages". I fixed it already. I had symbolic links in the whatsitcalled (I'm not at home right now) directory holding the .server files leading nowhere, and removing those cured the crash. This is because I had removed my rpm-installed galeon 1.3.1 in favor of the CVS version, but not yet installed the new one from source. I had made those two symlinks from the /usr/local/whatever directory to the rpm-installed /usr/whatever dir to make something work (I can't remember). Now the actual files disappeared and the activation server crashed trying to follow symlinks into the void. It's still a bug that should be fixed. I can try to remember to recreate the symlinks and do the trace anyway next week so that we can find out where the thing crashes.
Created attachment 14476 [details] Requested strace log
I'll mark this as a duplicate of another similar case.
*** This bug has been marked as a duplicate of 90983 ***