Ubuntu
gnome-keyring package

gnupg error message: WARNING: The GNOME keyring manager hijacked the GnuPG agent

Bug #1397614 reported by Simon Lyall
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-keyring (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Running gnupg will generate the error message:

gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system!

Cause:

The gnupg maintainer doesn't like GNOME keyring

http://bugs.gnupg.org/gnupg/issue1656

fix:

Editing or deleting /etc/xdg/autostart/gnome-keyring-gpg.desktop will probably fix the problem according to advice, but this is a little hard for an end user.

Needed: Simple solution for end user

Really Needed: GNOME keyring and Gnupg maintainers need to sort out their differences in a way that doesn't screw users.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-keyring (Ubuntu):
status: New → Confirmed
Revision history for this message
seba (5-admin-starepro-info) wrote :

Hello,
Any updates?

I have openPGP card and can't use with enigmail

:

2015-06-30 10:41:11.648 [DEBUG] enigmailCommon.jsm: encryptMessageEnd: uiFlags=1, sendFlags=00000061, outputLen=58
2015-06-30 10:41:11.648 [DEBUG] enigmailCommon.jsm: parseErrorOutput: status message:
[GNUPG:] BEGIN_SIGNING H8
gpg: WARNING: The GNOME keyring manager hijacked the GnuPG agent.
gpg: WARNING: GnuPG will not work properly - please configure that tool to not interfere with the GnuPG system!
[GNUPG:] ERROR check_hijacking 33554509
[GNUPG:] CARDCTRL 4
gpg: selecting openpgp failed: Unsupported certificate
gpg: signing failed: Unsupported certificate
gpg: [stdin]: clearsign failed: Unsupported certificate

2015-06-30 10:41:11.649 [DEBUG] enigmailCommon.jsm: parseErrorOutput: statusFlags = 08400000
2015-06-30 10:41:11.649 [DEBUG] enigmailCommon.jsm: parseErrorOutput(): return with errorMsg = No SmartCard could not be found in your reader
Please insert your SmartCard and repeat the operation.

Feel little bit sad :(

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.