← Back to team overview

desktop-packages team mailing list archive

[Bug 1397614] [NEW] gnupg error message: WARNING: The GNOME keyring manager hijacked the GnuPG agent

 

Public bug reported:

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.

** Affects: gnome-keyring (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1397614

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

Status in gnome-keyring package in Ubuntu:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1397614/+subscriptions


Follow ups

References