|
Bugzilla – Full Text Bug Listing |
| Summary: | gnome keyring integration broken since recent update | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.3 | Reporter: | Forgotten User 10buyl7JnO <forgotten_10buyl7JnO> |
| Component: | GNOME | Assignee: | E-mail List <gnome-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | vuntz |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User 10buyl7JnO
2010-01-04 07:16:37 UTC
This is probably because of the new gnome-keyring. Do you have libgnome-keyring and gnome-keyring 2.29.4? I have following packages. gnome-keyring-2.29.4-64.3.x86_64 libgnome-keyring0-2.29.4-3.1.x86_64 libgnome-keyring-devel-2.29.4-3.1.x86_64 gnome-keyring-lang-2.29.4-64.3.noarch gnome-keyring-pam-2.29.4-64.3.x86_64 Btw, is gnome-keyring-daemon running in your session before you start pidgin? It's not started before pidgin. If I start manually and then restart pidgin, I get following error dialogs. An application wants access to the keyring 'default', but it is locked. Then I have to enter the passwords again. Can you try the pidgin package from home:vuntz:11.2-testing? It should not use the keyring if it's not running. The main thing is shouldn't new gnome-keyring work as it was working before? So there are 2 things. 1) gnome-keyring is not starting and 2) applications are not able to read from gnome-keyring as it doesn't ask to unlock. Hrm. So, issue 2 is https://bugzilla.gnome.org/show_bug.cgi?id=605287 I think. It might be fixed in git, but I'm unsure. Need to think a bit about issue 1, especially in the pidgin context -- a lot of people want to use pidgin without gnome-keyring... Stanislav disabled the keyring usage in pidgin for openSUSE (since the patch is not going upstream and we don't want to maintain something that upstream won't use), so closing. I hope at least saving passwords will work and it won't ask for passwords each time pidgin starts. (In reply to comment #9) > I hope at least saving passwords will work and it won't ask for passwords each > time pidgin starts. Yes, it will be saved and so it should work again. |