From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)
Description of problem:
If evolution is closed it leaves a bunch of processes behind that need
to be killed manually:
/usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=18
This happens also when exiting the configuration wizard that shows up
when evolution is started the forst time.
If a user aborts the wizard, ALL processes forked from it should be
killed - there`s no need to keep something like alarm notify running
if the user decided to abort the wizard and evolution remains
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. as a user that has never called evolution before, call it
2. exit the appaering wizard by clicking 'cancel' on it`s first page.
3. run ps ax
You`ll see four evolution related processes that are still running and
will do so until next reboot.
Expected Results: All processes spawned by evolution should be killed.
Only if the user completed the wizard the might be a alarm/notify
process running - but only if this is the default behaviour or the
user selected an appropiate option.
Unclean shutdowns seem to be quite common with gnome apps. :(
Thanks for the report. Are you running Gnome or KDE? (or something
else) The gconfd-2 and bonobo-activation-server processses are shared
by most Gnome apps, and so they should hang around in a typical gnome
Which version of evolution are you running? What does rpm -q
evolution say? It looks like an old (FC2) version of evolution is
running, whereas this bug report says FC3test2.
on fedora core 2, evolution-1.4.6-2, I see alot of users leaving
/usr/libexec/bonobo-activation-server --ac-activate --ior-output-fd=19
running even after they've logged out
Closing per lack of response to previous request for information. This bug was
originally filed against FC3 and has remained in NEEDINFO state for quite some
time. Many packages and bugfixes have been made since the last substantive bug
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.