Bug 475880 - messagebus restart kills gnome session
messagebus restart kills gnome session
Product: Fedora
Classification: Fedora
Component: dbus (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-10 16:47 EST by Pawel Salek
Modified: 2009-12-18 02:15 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:15:10 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pawel Salek 2008-12-10 16:47:52 EST
Description of problem:
I have been debugging dbus configuration problems (FWIW, bug 475815) and have run "service messagebus restart" to activate the changes. To my horror, this killed also my Xwindows/GNOME session, including firefox and editor with open notes. 

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

How reproducible:
Probably always.

Steps to Reproduce:
1. Log in to a gnome graphical session
2. run sudo service messagebus restart
Actual results:
You will find youreself staring at a text screen.

Expected results:
dbus service should restart without affecting the state of other programs.

Additional info:
What is interesting, the X session did not restart, I was left at a text streen. GDM started after logging in at the text console and running from there "service messagebus restart" again.

While this bug is not likely to be triggered by many users, it is certainly surprising and the associated data loss - annoying.
Comment 1 Pawel Salek 2008-12-10 16:49:35 EST
BTW, I have hoped "messagebus reload" would do the job without killing the graphical session. And yes, it does not affect the graphical session! In fact, it does not do anything apart from printing:
"Message bus can't reload its configuration, you have to restart it"
Comment 2 Matthias Clasen 2009-01-17 01:17:40 EST
dbus uses inotify to monitor its configuration files, so it should reload them automatically.
Comment 3 Bug Zapper 2009-11-18 05:26:02 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 4 Bug Zapper 2009-12-18 02:15:10 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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