Bug 977292 – 'evolution --force-shutdown' should kill e-d-s processes as well

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 977292 - 'evolution --force-shutdown' should kill e-d-s processes as well

Summary:	'evolution --force-shutdown' should kill e-d-s processes as well

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 6
Classification:	Red Hat
Component:	evolution (Show other bugs)
Sub Component:
Version:	6.4
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	rc
Target Release:	---
Assigned To:	Matthew Barnes
QA Contact:	Desktop QE
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	977395
	Show dependency tree / graph

Reported:	2013-06-24 04:55 EDT by David Jaša
Modified:	2014-01-02 06:12 EST (History)
CC List:	4 users (show)

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

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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

Groups: 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):
evolution-2.32.3-5.el6.x86_64
evolution-data-server-2.32.3-5.el6.x86_64

How reproducible:
always

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

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.

http://rhn.redhat.com/errata/RHSA-2013-1540.html

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