From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20031009 Description of problem: The evolution-wombat process appears to be related to (if not responsible for) several of the problems users have observed with the gnome-settings-daemon dropping applets after gdm login, as well as various hangs in evolution with some less updated systems. evolution-wombat appears to hang after logging out of GNOME. This has been observed by a number of members on fedora-test-list. I have found that after logging out of GNOME, switching to a text tty and killing the evolution-wombat process releases the bonobo-activation-server and restores GNOME to proper functioning at the next login. I'm not sure how to proceed further with this bug report other than to give some appropriate version numbers. The system is an Athlon Tbird-1.4GHz, FC-0.94 and kernel-2.4.22-1.2088.nptl with all updates as of this writing (i.e., practically 0.95 at this point). Other possibly related packages (?): libbonobo-2.4.0-1 gdm-2.4.4.3-5 control-center-2.4.0-1 gnome-panel-2.4.0-3 More information available upon request.... Version-Release number of selected component (if applicable): evolution-1.4.5-2 How reproducible: Always Steps to Reproduce: 1. Run evolution, then exit. 2. Log out of GNOME. 3. Log back in. 4. Gnome-settings-daemon produces numerous errors, including failure to load any user-setup applets in panel. 5. Repeat 1-3 as often as desired to repeatedly view problem. 6. Log out of GNOME. 7. Switch to text virtual terminal and kill evolution-wombat process. Note that bonobo-activation-server also quits at that time as well. 8. Switch back to X server and login to GNOME, at which time problem does not recur. Additional info: A screenshot will be inserted in the next comment showing both the initial error (at the upper left) and then the errors per applet (at the lower right).
Created attachment 95113 [details] Screenshot of gnome-settings-daemon errors.
Just killing the bonobo process works around this; nothing to do with wombat then I guess.
Apparently I don't understand the wombat/bonobo relation well, for which I apologize. When I log out of GNOME, if I switch to a tty and login there, I still see both the evolution-wombat and bonobo-activation-server processes alive. Killing wombat also ends the bonobo-a-s process, but killing b-a-s does not end the wombat process. Therefore I came to the tentative conclusion that the proper behavior was probably for wombat to be terminating in some courteous fashion during the logout process, allowing b-a-s to finish as well.
I don't understand it myself. I think you are probably right.
I experience this after every logout/login. Just killing b-a-s fixes things.
Same bad behavior in kernel-2.4.22-1.2096.nptl. Once again, the problem is not in the bonobo-activation-server. The wombat process does not end properly, which apparently means that bonobo-activation-server can't either. I can only hope Havoc understands this stuff. :-) I'm assuming from the relative silence that there's nothing else I can do to help track this down.
For additional information at GNOME's Bugzilla: http://bugzilla.gnome.org/show_bug.cgi?id=124707 Also, I have changed title to reflect reality. Should this be moved to UPSTREAM?
*** Bug 107580 has been marked as a duplicate of this bug. ***
Created attachment 95444 [details] implement session management for wombat Attached patch implements session management for evolution-wombat. Sent upstream for comments.
Added patch to evolution to fix this for FC1. Patch has been rejected by upstream, though as it adds a dependency on the DISPLAY for evolution-wombat.
Tested 1.4.5-7, appears to work just fine now. Thanks Jeremy.
FYI, rebuilt evolution-1.4.5-7 on rh9 *still* has the problem. -- Rex
This is what gnome's bugzilla claims to fix it (in libbonobo): diff -u -p -u -r1.41 bonobo-activation-activate.c --- bonobo-activation/bonobo-activation-activate.c 9 Jun 2003 13:17:55 -0000 1.41 +++ bonobo-activation/bonobo-activation-activate.c 29 Oct 2003 13:23:01 -0000 @@ -714,6 +714,7 @@ bonobo_activation_init_activation_env (v { "SESSION_MANAGER", NULL }, /* XSMP session manager */ { "AUDIODEV", NULL }, /* Audio device on Sun systems */ { "LANG", NULL }, /* Fallback locale name */ + { "XAUTHORITY", NULL }, { NULL, NULL } }; I applied this patch to rh9's bonobo-activation, but it didn't seem to help any. )-:
FYI, for the problem to go away on rh9, I had to upgrade other items as well: libbonobo-2.4.0 (patched as above), libbonoboui-2.4.0, GConf2-2.4.0, ORBit2-2.8.2 (and linc 1.0.3).
Not the end of the story, turns on the wombat patch made the Calendar non-functional. Rebuilding without it fixed the Calendar, and it turns out I'm not seeing the original problem either (perhaps it really was fixed solely by the bonobo-action/XAUTHORITY patch). OK, I'm really done this time. (-;
To follow up on Rex's comments, and add some new experience, the problem is recurring in FC1. The wombat process now stops politely, but bonobo-activation-server persists, causing the same problem. Havoc or Tim... should this bug be reopened at this point? Apparently other people are still seeing this as well, cf. #109449 for example.
Yes, I'm seeing this problem on FC1. I have NFS mounted home directories.