I'm not using a fingerprint reader. On this machine I am the only user
so there is only one password.

I posted a screenshot here:

http://ubuntuforums.org/showpost.php?p=9551450&postcount=1

I only get that if I'm using auto-login. If I log in using my password
all is fine.

I first encountered this behavior in Lucid after applying the following
proposed updates:

app-install-data-partner (12.10.04) to 12.10.04.3
dpkg (1.15.5.6ubuntu4) to 1.15.5.6ubuntu4.1
empathy (2.30.1.1-0ubuntu1) to 2.30.2-0ubuntu1
empathy-common (2.30.1.1-0ubuntu1) to 2.30.2-0ubuntu1
grub-common (1.98-1ubuntu6) to 1.98-1ubuntu7
grub-pc (1.98-1ubuntu6) to 1.98-1ubuntu7
libatk1.0-0 (1.30.0-0ubuntu2) to 1.30.0-0ubuntu2.1
libatk1.0-data (1.30.0-0ubuntu2) to 1.30.0-0ubuntu2.1
libdbusmenu-glib1 (0.2.9-0ubuntu3) to 0.2.9-0ubuntu3.1
libdbusmenu-gtk1 (0.2.9-0ubuntu3) to 0.2.9-0ubuntu3.1
nautilus-sendto-empathy (2.30.1.1-0ubuntu1) to 2.30.2-0ubuntu1
update-manager (1:0.134.9) to 1:0.134.10
update-manager-core (1:0.134.9) to 1:0.134.10

That was somewhat of an error on my part as I'd intended to only upgrade
'grub-pc' and 'grub-common', but I ended up with the same behavior in
Maverick after upgrading the 'grub' packages. I'm unsure that was the
actual trigger but it may be???? However even purging/reverting these
packages does not revert to the "unbroken" state.

Strangely I was not able to duplicate this behavior with test installs
of Lucid and Maverick on my secondary drive and ATM it appears that I
can duplicate this behavior if either Lucid or Maverick are installed
using ext3, but NOT if I use ext4.

I do however need to perform a few more test installs to be certain and,
due to totally unrelated time constraints, that may take a few days.

That's why I wonder if others effected by this are all using ext3?

Or has anyone seen this if using ext4?

Something else I've found while testing for this behavior is that
opening any password protected gui (eg: synaptic, gufw, gparted, etc)
will always produce this behavior if the problem is present. That is
I'll first have to enter my password "to unlock keyring" and then also
on the expected screen to "perform administrative tasks". Of course it
appears only once after each reboot.

-- 
[regression-release] Keyring not unlocked on login anymore in Lucid
https://bugs.launchpad.net/bugs/529338
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to