Bug 49

Summary: DBus session bus doesn't exit when X session exits
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Ross Burton - Disabled <ross>
Component: meta-yoctoAssignee: Kevin Tian <kevin.tian>
Status: RESOLVED INVALID QA Contact:
Severity: normal    
Priority: Medium CC: poky.bs.watcher, poky.watcher, sgw
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Ross Burton - Disabled 2008-01-26 11:09:50 UTC
Because dbus-launch is started on its own, it doesn't know what the session is.  This needs to be changed so that dbus-launch starts X, so it can track the session.
Comment 1 Kevin Tian 2010-08-25 22:30:09 UTC
I can't reproduce this bug. Actually there's no clean way to exit X session from Sato environment. I tried to use "killall xinit" to bring X down. That way dbus-launch exits too.

I then check dbus-launch manual:

 --exit-with-session
              If  this  option  is provided, a persistent "babysitter" process
              will be created that watches stdin for HUP and tries to  connect
              to  the  X  server. If this process gets a HUP on stdin or loses
              its X connection, it kills the message bus daemon.

So far /etc/X11/Xsession does use "--exit-with-session". So I think this bug can be closed. If there's anything I misunderstand, please reopen it then.