https://bugzilla.novell.com/show_bug.cgi?id=383464 User abockover@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383464#c5 Aaron Bockover <abockover@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|abockover@novell.com | --- Comment #5 from Aaron Bockover <abockover@novell.com> 2008-04-30 11:03:50 MST --- I think there's a bit of a difference between recycling apps (like Nautilus, gnome-session, the panel, etc.) when dbus goes down vs functionality being completely disabled if it goes down (like this bug). I restart DBus and HAL fairly frequently when I am working on code that uses these features to test reliability in the infrequent case when a user may experience an unintentional restart of these services. I did not explicitly restart DBus when I discovered this bug, but I did explicitly restart HAL. Does HAL have anything to do with this, or is it just DBus? As for Banshee, yes, it survives very gracefully if you yank DBus from underneath it. In fact, when DBus comes back to life, you can still use DBus features in Banshee. No crash, no app-recycle, no loss of functionality. I understand the rationale for just letting the desktop features recycle, but when they come back, they should not be limited or disabled. Furthermore, I don't see why the shutdown dialog would even be in process when I'm not using it, so it seems like any DBusing it may do would happen when I actually start that process, and certainly nothing should be disabled then since by this time, all the necessary services have restarted. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.