Red Hat Bugzilla – Bug 1396386
glib2-fam prints an extra string and breaks gnome-ssh-askpass
Last modified: 2017-08-01 08:28:09 EDT
Created attachment 1221781 [details] A trivial patch that stops printing the string Description of problem: I think starting from RHEL7.3, gnome-ssh-askpass no longer work correctly if glib2-fam is installed and the Oxygen-gtk theme is in use. This turns out to be because /usr/lib64/gio/modules/libgiofam.so prints a debug string that is then prepended to the password, breaking it. Other software are also affected. Version-Release number of selected component (if applicable): glib2-2.46.2-4.el7.x86_64 How reproducible: Reproducible. Steps to Reproduce: 1. yum install glib2-fam openssh-askpass 2. select Oxygen-gtk as the GTK+ theme from from tweak-tool 3. run /usr/libexec/openssh/gnome-ssh-askpass Actual results: The prompt for password opens and "II 1" already gets written to stdout. Expected results: Nothing is written to stdout until something is entered into the password prompt - then only the password is, nothing else. Additional info: The same bug about a year ago with pinentry-gtk-2 in OpenSUSE: https://bugzilla.novell.com/show_bug.cgi?id=951221
This bug is actually quite a critical bug in that the output is produced in many situations. We were unable to deploy the latest OS updates (because this bug introduced output when our s/w was invoked) until we finally discovered the cause of this bug (after many man hours of trying to replicate and understand it), found this bugzilla, and recompiled glib2 with the included patch. It is a trivial fix. The patch included here fixes it according to our testing. Please ship ASAP, because recompiling glib2 each time there is an update is tedious and introduces risk.
https://bugzilla.gnome.org/show_bug.cgi?id=780144
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2100