Package: gpa Version: 0.9.0-1 Severity: normal Starting gpa for the first time, I see a bunch of strange keys (many expired) in the key manager. It is not possible to delete these keys. Should they really be there? Are these some system-wide installed keys? In any case, the expired ones are of no use, no?
Trying to delete one using the right-click context menu leads to the error message: "The GPGME library returned an unexpected error. The error was: No public key This is probably a bug in GPA. GPA will now try to recoved from this error". Best regards Torquil Sørensen -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38.4 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpa depends on: ii gnupg2 2.0.17-2 GNU privacy guard - a free PGP rep ii gpgsm 2.0.17-2 GNU privacy guard - S/MIME version ii libc6 2.13-2 Embedded GNU C Library: Shared lib ii libglib2.0-0 2.28.6-1 The GLib library of C routines ii libgpg-error0 1.10-0.3 library for common error values an ii libgpgme11 1.2.0-1.3 GPGME - GnuPG Made Easy ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime gpa recommends no packages. gpa suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
