GNOME Bugzilla – Bug 742386
gdbusconnection: Don't g_printerr() when exiting
Last modified: 2015-08-06 12:52:36 UTC
exit-on-close for a DBus connection is a completely normal thing. On a regular GNOME login, gdm retains the X server, but terminates the session login bus and associated helpers like gnome-settings-dameon, the a11y tools, etc. I've seen several downstream reports of confusion as to what these apparent error messages mean in the system log. It doesn't help that they're so obtuse. We're also printing them to stderr, when this is not an error. The reason this was introduced is presumably some people were confused as to why their process exited when the system bus did. But the solution for that I believe is documentation, not printing stuff to everyone's system log in normal operation.
Created attachment 293826 [details] [review] gdbusconnection: Don't g_printerr() when exiting
My understanding of the future is that exit-on-close will stop being a thing, replaced by kill-by-cgroup-membership...
I'm not sure about that. Old thread: https://lists.fedoraproject.org/pipermail/desktop/2008-January/003810.html
Even were we to switch to cgroups in some future GNOME version, I'd like to fix this bug in the existing version, since I try to pull in newer glib versions. In parallel, we could investigate using prctl(PR_SET_PDEATHSIG, SIGTERM) more. This would help for gnome-settings-daemon, if gnome-session exited first (before the session bus). The a11y bus uses it already. This is more efficient too, as we don't get scheduled only to print something and exit.
Comment on attachment 293826 [details] [review] gdbusconnection: Don't g_printerr() when exiting No real objections, so applying.
https://git.gnome.org/browse/glib/commit/?id=66bc9660c44b71c8bff47b4f7e16a801169a9f23