Your message dated Sun, 11 Apr 2021 17:37:38 +0100
with message-id <[email protected]>
and subject line Re: Bug#931558: seahorse: GnuPG key import fails
has caused the Debian Bug report #931558,
regarding seahorse: GnuPG key import fails
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
931558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931558
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: seahorse
Version: 3.30.1.1-1
Severity: normal
Dear Maintainer,
I installed Debian Buster today and wanted to import the keys I had exported
from Seahorse on Debian Stretch (on other hardware) yesterday. After selecting
the files to import and pressing the button "import" Seahorse I got a list of
the included keys. I couldn't select any entry using the mouse but was able to
select everything by using the shortcut "CTR-A". After pressing the Seahorse
"import" button the window with the list of the keys went away but nothing else
happened. Even after about half an hour no key was imported. After several
attempts with a whole key ring and as an alternative with just my private key I
could only import my keys using the command line.
-- System Information:
Debian Release: 10.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages seahorse depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii gcr 3.28.1-1
ii gnome-keyring 3.28.2-5
ii gnupg 2.2.12-1
ii libatk1.0-0 2.30.0-2
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libavahi-glib1 0.7-4+b1
ii libc6 2.28-10
ii libgck-1-0 3.28.1-1
ii libgcr-base-3-1 3.28.1-1
ii libgcr-ui-3-1 3.28.1-1
ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii libglib2.0-0 2.58.3-2
ii libgpgme11 1.12.0-6
ii libgtk-3-0 3.24.5-1
ii libldap-2.4-2 2.4.47+dfsg-3
ii libsecret-1-0 0.18.7-1
ii libsoup2.4-1 2.64.2-2
Versions of packages seahorse recommends:
ii openssh-client 1:7.9p1-10
seahorse suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 40~alpha-1
On Fri, 09 Apr 2021 at 02:00:33 +0200, SnipFoo wrote:
> I've backported the fix from upstream [1], and it seems to have fixed
> the problem: importing GnuPG keys now works again as expected.
>
> [1] https://gitlab.gnome.org/GNOME/seahorse/-/merge_requests/144
This seems to be included in upstream release 40.alpha, so whatever else
happens, version 40~alpha-1 in experimental should fix this.
> Since this bug prevents seahorse from importing GnuPG keys--and
> therefore makes it quite useless for managing GnuPG keyrings--,
> do you think there's any chance this fix might make it to bullseye,
> please?
I don't know whether the release team are accepting unblocks for non-RC
bugs at this point, but I'll ask.
smcv
--- End Message ---
