GNOME Bugzilla – Bug 721324
Error message is printed to stdout
Last modified: 2014-01-02 15:09:13 UTC
On testing some things with dbus and dconf I'm sometimes seeing this message: "g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting." The message itself is not the problem as I know the cause but I'm noticing it is printed to stdout. But shouldn't this message go to stderr?
-> gdbus For some reason it's using g_print()...
Created attachment 265123 [details] [review] GDBusConnection: don't write to stdout When losing the D-Bus connection, we would write to stdout about it just before killing ourselves with SIGTERM. We're a library, so we should probably use stderr instead.
Created attachment 265124 [details] [review] GDBusConnection: don't write to stdout When losing the D-Bus connection, we would write to stdout about it just before killing ourselves with SIGTERM. We're a library, so we should probably use stderr instead. There was a testcase that verified that the message was written to stdout. Modify that to check stderr instead.
Review of attachment 265124 [details] [review]: Ok. (I quite dislike this printing code since it happens in completely normal situations like logging in via gdm, but that's a separate bug)
Attachment 265124 [details] pushed as 51b3dd7 - GDBusConnection: don't write to stdout