Same problem 1) I recreated my account 2) When logging in with username and password the keyring is unlocked, gwibber and Network Manager works are able to read password from the keyring 3) I removed the password from the keyring, and after I log in again using username and password, gwibber and Network Manager are still able to properly read the passwords from my keyring 4) I create a .thinkfinger.bir and logs in using my finger, and gwibber and Network Manager are _not_ able to read the password from the keyring
The expected result of step 4 was that gwibber and Network Manager would in fact be able to read the keyring, and until a about a week ago this worked like a charm. Is this really a bug or MUST you login with username and password to at all use the keyring? Workarounds: 1) Network Manager: apply the wireless profile to all users. This takes the local keyring out of the equation. 2) gwibber: just run "gnome-keyring-daemon -d" from a command line before starting gwibber -- [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 Desktop Bugs, which is subscribed to gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs