On Feb 16, 2008 3:48 AM, Brian J. Tarricone <[EMAIL PROTECTED]> wrote: > Patryk Zawadzki wrote: > See 'man dbus-launch', specifically the --exit-with-session option. > That should cause the session daemon to quit if X exits.
Sure but it sometimes fails (for example X segfaults). > > Having it started by > > ConsoleKit would remove the burden of having to start it in Xinit and > > would allow CK to notify dbus when the number of client sessions > > changes (so it only dies if there are no connected clients and no > > active sessions). This would allow new scenarios like logging in > > remotely using ssh and checking the printing queue that was started > > before leaving or using remote graphical login to fiddle with some > > other user service that was already started. > This somewhat highlights what IMHO is one of the worst things about > dbus: its reliance on environment variables to tell clients how to > contact the session bus. If CK starts the session bus, how do the > appropriate env vars propagate into the desktop session? You could > solve this by having CK start the session as well, but that sounds like > a bit of a big change, no? Just make the dbus client library ask CK and cache the values instead of relying on ENV variables. I agree that any program relying on ENV variable propagation is broken in 2008. -- Patryk Zawadzki PLD Linux Distribution _______________________________________________ xdg mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xdg
