Bug#842223: seahorse: can't unlock Gnome keyring
Toni Mueller
toni at debian.org
Thu Oct 27 05:05:04 UTC 2016
Package: seahorse
Version: 3.20.0-2
Severity: important
Dear Maintainer,
I want to use seahorse to unlock my Gnome keyring, which I need for
some other app (Evolution) that depends on it.
Since my latest upgrade, I am no longer being asked for a password to
unlock it with this pop-up (which app produces that?), so I thought I'd
use seahorse instead. In seahorse, I can see the keyring, then
right-click and select 'Unlock', and then nothing happens. As a result
of this, the keyring does not get unlocked.
I would expect a password dialogue to appear to let me unlock the
keyring.
FWIW, I use awesome as a "desktop", but need to use Evolution to access
my email on an Exchange server. However, switching to Gnome entirely is
not an option.
Cheers,
Toni
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages seahorse depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2
ii gcr 3.20.0-3
ii gnome-keyring 3.20.0-3
ii gnupg 2.1.15-4
ii libatk1.0-0 2.22.0-1
ii libavahi-client3 0.6.32-1
ii libavahi-common3 0.6.32-1
ii libavahi-glib1 0.6.32-1
ii libc6 2.24-5
ii libgck-1-0 3.20.0-3
ii libgcr-base-3-1 3.20.0-3
ii libgcr-ui-3-1 3.20.0-3
ii libgdk-pixbuf2.0-0 2.36.0-1
ii libglib2.0-0 2.50.1-1
ii libgpgme11 1.7.0-1
ii libgtk-3-0 3.22.1-1
ii libldap-2.4-2 2.4.42+dfsg-2+b3
ii libsecret-1-0 0.18.5-2
ii libsoup2.4-1 2.56.0-1
Versions of packages seahorse recommends:
ii openssh-client 1:7.3p1-1
seahorse suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list