Bug 127969

Summary:	dbus: after rcdbus stop: restart does not work
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Danny Al-Gaaf <dalgaaf>
Component:	Basesystem	Assignee:	Timo Hoenig <thoenig>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	meissner
Version:	Beta 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Danny Al-Gaaf 2005-10-12 21:45:28 UTC

If you stop dbus on a system with a user logged in on KDE-session with rcdbus 
stop only the system daemon is stopped, not the session daemon. In this case you 
can't restart dbus with 'rcdbus (re)start' . You get no error message, it looks 
like succsessful started, but the daemon is not running. You need first to kill 
all other running dbus processes.

This should be fixed. The minimum fix: a error message. Not sure, but if the 
system dbusdaemon process is stopped also all sessionbus processes should maybe 
stopped.

Comment 1 Timo Hoenig 2005-10-12 22:01:06 UTC

The proposed minimum mix is no solution. We have to get dbus-daemon (the one for the system bus) 
 get killed and started again in case of rcdbus restarted. This has to work with and without other 
dbus-daemon processes represeting the users' session busses.

If {start,kill}proc can not help us we'll have to find a work around.

Comment 2 Danny Al-Gaaf 2005-11-17 15:01:16 UTC

This bug is already present in 10.1 after stop the dbus daemon there are some dbus processes left. You can't restart dbus.

Comment 3 Timo Hoenig 2005-11-17 15:08:24 UTC

I'll fix this one for 10.1.  Though it doesn't hurt anymore (services are reloaded at runtime).

Comment 4 Timo Hoenig 2006-01-19 20:05:08 UTC

Should be still present in 10.1.  Will have a look for a proper fix.

Comment 5 Timo Hoenig 2006-01-23 09:44:09 UTC

Fixed package submitted to stable.

Comment 6 Timo Hoenig 2006-01-26 13:01:01 UTC

*** Bug 145780 has been marked as a duplicate of this bug. ***

Comment 7 Timo Hoenig 2006-02-22 18:44:57 UTC

*** Bug 116700 has been marked as a duplicate of this bug. ***