On Sun, 2007-02-18 at 13:57 +0100, Marco Pesenti Gritti wrote: > On Sun, 2007-02-18 at 18:12 +0530, Joshua N Pritikin wrote: > > On Sun, Feb 18, 2007 at 11:47:30AM +0100, Marco Pesenti Gritti wrote: > > > On Sun, 2007-02-18 at 15:50 +0530, Joshua N Pritikin wrote: > > > > OK, but why can't sugar-clipboard fail gracefully like everything else? > > > > > > I think sugar-clipboard is leaked because it doesn't make an X server > > > connection. The other processes are not exiting gracefully but they are > > > dieing because gtk kills them when the X connection is lost. > > > > > > We need to figure out a good session shutdown strategy at some point. > > > > I see that sugar-clipboard is daemonized when created (parent=1): > > > > joshua 7616 1 6 18:11 ? 00:00:00 python > > /home/joshua/sugar-jhbuild/build/bin/sugar-clipboard > > > > This may be a dumb question, but why doesn't dbus remain > > sugar-clipboard's parent and kill it when dbus dies? > > Yeah, that's an issue I run into a few months ago when looking in this > stuff... I'm not sure really, it might just be a dbus bug. If someone > has time to investigate this one it would be useful. > > Marco
If you have a D-Bus connection open and the exit on disconnect flag is enabled (default) then it should be killed when the connection disconnects (i.e. the bus goes away). -- John (J5) Palmieri <[EMAIL PROTECTED]> _______________________________________________ Sugar mailing list [email protected] http://mailman.laptop.org/mailman/listinfo/sugar
