Bug 518433

Summary: gconfd-2: no process killed when updating gnome-bluetooth with Anaconda
Product: Red Hat Enterprise Linux 5 Reporter: Alexander Todorov <atodorov>
Component: gnome-bluetoothAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED WONTFIX QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 5.4CC: borgan, dfediuck, lsmid, ovasik, rvokal
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-07 12:33:55 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alexander Todorov 2009-08-20 12:14:45 UTC 
Description of problem:
Upgrading gnome-bluetooth-0.7.0-10.2.el5.x86_64
gconfd-2: no process killed


Version-Release number of selected component (if applicable):
gnome-bluetooth-0.7.0-10.2.el5.x86_64

How reproducible:


Steps to Reproduce:
1. Install RHEL5.3 Client, @everything, Client, VT and Workstation repos
2. upgrade to RHEL 5.4 Client
3.
  
Actual results:
killall -HUP gconfd-2 from the package scriptlet causes the error to be printed because there's no such process running. 


Expected results:
No error is printed

Additional info:
There's been a discussion about this on fedora-packaging list 2 years ago:
http://markmail.org/message/rb52oh2kqurdxlku
Comment 3 RHEL Program Management 2009-11-06 19:05:21 UTC 
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. If you would like
this request to be reviewed for the next minor release, ask your
support representative to set the next rhel-x.y flag to "?".