Bug 924486

Summary: Avoid spurious warnings from gnome about setting the application name
Product: [Fedora] Fedora EPEL Reporter: Todd Zullinger <tmz>
Component: python-keyringAssignee: Christopher Tubbs <ctubbsii>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: el6CC: bperkins, ctubbsii, extras-qa, p, rtnpro
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-keyring-5.0-3.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-01-09 16:18:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Work around spurious output from gnome keyring on EL6 none

Description Todd Zullinger 2013-03-21 21:07:10 UTC 
Created attachment 714116 [details]
Work around spurious output from gnome keyring on EL6

When calling get_password or set_password using the GnomeKeyring backend, spurious warnings are printed to the terminal:

** (process:29438): WARNING **: g_set_application_name not set.

This appears to be due to https://bugzilla.gnome.org/show_bug.cgi?id=460515 which seems to be fixed in Fedora releases.  I did not see this issue when using the same calls on Fedora.

The attached patch against 0.7-1.el6 corrects the problem for me.
Comment 1 Christopher Tubbs 2017-04-10 23:58:47 UTC 
The referenced GNOME bug indicates that the problem is with the application calling the keyring library, and not a problem with the library itself. It's also been 4 years since the last activity on this bug. I recommend closing it, but I defer to the el6 branch maintainer.
Comment 2 Christopher Tubbs 2017-10-11 23:02:48 UTC 
I've patched this in epel7 via bz#1498477
However, I don't have write access to the el6 branch to push the fix there.

It's a simple fast-forward merge if another maintainer wants to do it, or the POC for the el6 branch can give me write-access (I don't know how ACLs work in Pagure now that Pkgdb2 is no longer being used):
  fedpkg clone python-keyring && \
  cd python-keyring && \
  git checkout -t origin/el6 && \
  git merge --ff-only origin/epel7 && \
  git push origin refs/heads/el6:refs/heads/el6
Comment 3 Christopher Tubbs 2017-12-22 01:01:43 UTC 
Ping to the primary maintainer or a provenpackager. Please either patch, or give me access so I can patch el6. I've already fixed this in epel7. See above comment for instructions on backporting to el6.
Comment 4 Fedora Update System 2017-12-22 02:27:29 UTC 
python-keyring-5.0-3.el6 has been submitted as an update to Fedora EPEL 6. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-f190f4cfd9
Comment 5 Christopher Tubbs 2017-12-22 02:30:17 UTC 
I was able to push the changes after the repo credentials were reset, and push the fix to the el6 branch.
Comment 6 Fedora Update System 2017-12-22 15:32:30 UTC 
python-keyring-5.0-3.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-f190f4cfd9
Comment 7 Fedora Update System 2018-01-09 16:18:27 UTC 
python-keyring-5.0-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.