After update to gcr-3.6.2-3.fc18, together with gnome-keyring-3.6.3-1, I'm no longer asked for a keyring unlock and other password prompts (like from evolution 3.8 testing repo) under KDE. I tested this with seahorse, which seems to be the easiest way of testing this. Steps: a) update to gcr-3.6.2-3.fc18 b) kill running gnome-keyring-daemon, if any c) run seahorse d) View->By Keyring e) if your Password keyring (most likely Default) is unlocked, then Lock it f) right-click the Password->Default and choose Unlock See nothing happens, while one should get a prompt to unlock his/her keyring. g) close seahorse h) yum downgrade gcr (you should get 3.6.2-1.fc18) i) kill running gnome-keyring-daemon j) run seahorse k) right-click the Password->Default and choose Unlock This time the keyring password prompt is shown.
I can verify this bug as well. Downgrading gcr allowed evolution to prompt for a new SMTP password after the old one was changed, which it would not do under gcr-3.6.2-3.fc18. I examined keyring in seahorse and noted that evolution updated the keyring with the new password under gcr-3.6.2-1.fc18.
*** Bug 952483 has been marked as a duplicate of this bug. ***
I just found out that this is kind of known within bug #907156.
gcr-3.6.2-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/gcr-3.6.2-4.fc18
The update fixes the password prompt, I'm asked for a password, but the keyring is not unlocked, thus the password I entered is not saved. This is still better than no password prompt at all.
hm. I can lock and unlock. I am not prompted for a password. Maybe I have none set up. But the keyring apparently locks and unlocks properly.
(In reply to comment #6) > hm. I can lock and unlock. I am not prompted for a password. Maybe I have > none set up. But the keyring apparently locks and unlocks properly. What is your gcr version?
3.6.2-3.fc18
(In reply to Tobias Mueller from comment #8) > 3.6.2-3.fc18 My comment #5 was for version from comment #4, thus gcr-3.6.2-4.fc18
gcr-3.6.2-4.fc18.x86_64 fixed the problem for me (after rebooting).
gcr-3.6.2-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
(In reply to Fedora Update System from comment #11) > gcr-3.6.2-4.fc18 has been pushed to the Fedora 18 stable repository. If > problems still persist, please make note of it in this bug report. the bug should have been automatically closed