Comment 71 for bug 576724

Just following up here, I'm sure you saw my comment #5 in bug #580408 which also applies here.

I had encountered one problem that I suspected was unrelated to these proposed updates, and I still believe it's unrelated. When performing the initial test described in comment #70 above I was asleep at the wheel and installed all 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

Following that I encountered bug #529338, but I was wide awake when I performed the test outlined in comment #5 in bug #580408 and I made certain to only apply the proposed grub-pc and grub-common updates, and the behavior described in bug #529338 was NOT duplicated in that test case!

So, I think it's safe to say that's in no way related to your proposed updates, and possibly not even due to the other proposed updates I unwisely applied in my first test case. I have in fact even painstakingly backed out all of the proposed updates, including these grub updates, and I've not been able to escape that behavior where the Login Keyring fails to unlock (it does so only if I'm using auto-login).

Anyway, even though I suspect this is totally unrelated, I thought you should know :^)