Bug#831536: gnome-keyring: Unencrypted login keyring remains "locked" after autologin
Daniel Gnoutcheff
daniel at gnoutcheff.name
Sun Jul 17 04:33:23 UTC 2016
Package: gnome-keyring
Version: 3.20.0-1
Severity: normal
I've enabled autologin on one of my workstations, and in a bid to get
gnome-keyring to play nice with it, I've set an empty password on the
login keyring. This worked nicely in wheezy.
Since at least jessie, however, the (unencrypted) login keyring remains
"locked" after autologin, and e.g. password autofill in Chromium doesn't
happen. To fix this, I end up starting seahorse and asking it to unlock
the keyring, which of course it does immediately with no password
prompt.
This seems silly. I would expect that an unencrypted keyring would
always be "unlocked", as far as client apps are concerned.
This has also been noted by Maciej Mensfeld on his blog, along with his
workaround:
http://dev.mensfeld.pl/2014/09/ubuntu-14-04-gnome-keyring-seahorse-auto-unlock-when-auto-login/
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.6.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-keyring depends on:
ii dbus-x11 1.10.8-1
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-1
ii gcr 3.20.0-2
ii libc6 2.23-1
ii libcap-ng0 0.7.7-3
ii libcap2-bin 1:2.25-1
ii libgck-1-0 3.20.0-2
ii libgcr-base-3-1 3.20.0-2
ii libgcrypt20 1.7.1-2
ii libglib2.0-0 2.48.1-1
ii p11-kit 0.23.2-3
ii pinentry-gnome3 0.9.7-5
Versions of packages gnome-keyring recommends:
ii libpam-gnome-keyring 3.20.0-1
gnome-keyring suggests no packages.
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list