Bug 977292 - 'evolution --force-shutdown' should kill e-d-s processes as well
'evolution --force-shutdown' should kill e-d-s processes as well
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Matthew Barnes
Desktop QE
Depends On:
Blocks: 977395
  Show dependency treegraph
Reported: 2013-06-24 04:55 EDT by David Jaša
Modified: 2014-01-02 06:12 EST (History)
4 users (show)

See Also:
Fixed In Version: evolution-2.32.3-10.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 977395 (view as bug list)
Last Closed: 2013-11-20 23:53:29 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
GNOME Bugzilla 590245 None None None Never
Red Hat Product Errata RHSA-2013:1540 normal SHIPPED_LIVE Low: evolution security, bug fix, and enhancement update 2013-11-20 19:40:51 EST

  None (edit)
Description David Jaša 2013-06-24 04:55:34 EDT
Description of problem:
"evolution --force-shutdown" is sometimes used to bring evolution to clean state, but that's not possible without fresh start of e-d-s processes as well.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. look up evolution and e-{calendar,addressbook}-factory processes PIDs
2. invoke 'evolution --force-shutdown'

Actual results:
the original *factory processes continue to run

Expected results:
*factory processes are killed as well

Additional info:
Comment 4 Milan Crha 2013-06-25 03:23:45 EDT
evolution-alarm-notify process was missing in the list of "to be killed" processes, I added it for evolution-2.32.3-10.el6.
Comment 9 errata-xmlrpc 2013-11-20 23:53:29 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.