GNOME Bugzilla – Bug 756879
gio fam monitor: debug output can destroy functionality
Last modified: 2017-03-19 14:59:38 UTC
Originally reported downstream: https://bugzilla.opensuse.org/show_bug.cgi?id=951221 original start point: gpg signing on my laptop works, gpg signing on my desktop fails with "gpg: signing failed: Invalid IPC response" > pinentry-gtk-2 2>/dev/null OK Pleased to meet you getpin II 1 D asdf OK The output 'II 1' is fatal, as it does not belong into the conversation to be held... and gpg parsing output falls flat on the nose. The text comes from gio/fam/gfamfilemonitor.c patch: --- gio/fam/gfamfilemonitor.c +++ gio/fam/gfamfilemonitor.c @@ -140,7 +140,7 @@ g_mutex_unlock (&fam_lock); - g_print ("II %d\n", fam_initialised); + /* g_print ("II %d\n", fam_initialised); */ return fam_initialised; } Collapse All Comments Expand All Comments Add Comment
The debugging code was added as part of https://git.gnome.org/browse/glib/commit/gio/fam/gfamfilemonitor.c?id=d682df186e9cca2b8db0e921450a4db31cf0c467 Our globalization team is reporting it's also causing problems for creating a correct xml file for ibus input method configuration file by /usr/lib/ibus/ibus-engine-m17n --xml command since unnecessary 'II 1' strings are inserted to the head of xml file, which causes all m17n engines to disappear from the selection list.
Created attachment 342103 [details] [review] Patch currently used in Solaris builds
Even though THIS bug has been around for much longer, I mark it as a duplicate of bug 780144 - the latter one had a patch that was merged into the glib 2.52.0. *** This bug has been marked as a duplicate of bug 780144 ***