Created attachment 549824 [details] corrected file Description of problem: After login, when Gajim is launched, it asks again for a password via gnome-keyring, because Gajim' passwords are stocked into ~/.gnome2/keyrings/default.keyring instead of ~/.gnome2/keyrings/login.keyring. Don't know if this bug happens in a Gnome session by the way, only tested on other sessions, like Openbox, Wmaker, etc... but all my contacts have this bugs. I give you the fix further in this report, which is OK for me. Version-Release number of selected component (if applicable): 0.14.3-1 How reproducible: Launch Gajim after login. Steps to Reproduce: 1. login in your session (activate the normal keyring) 2. launch Gajim (with already created accounts and passwords) Actual results: It will ask a password in order to unlock the keyring created by Gajim which is not the good file (default.keyring instead of login.keyring). Expected results: Gajim should just be launched without asking anything, because the real keyring was already unlocked at login. Additional info: There is the bugfix : in /usr/share/gajim/src/common/passwords.py file, at line 66 "self.keyring = 'default'", change "default" by "login" like this : "self.keyring = 'login'" The corrected file is attached with this report.
EDIT Hmmm it seems that it doesn't work anymore after reboot... have to look deeper.
EDIT 2 It's ok, just be sure that "/usr/bin/gnome-keyring-daemon --start" is launched at startup (in Openbox autostart file for example). Sorry for the two "edit" replies.
As a workaround you can use seahorse to 'Set as default' on the 'login' keyring. I believe you that the change works as expected, but I can't tell if it is the correct fix. Could you please propose it to gajim developers upstream (http://gajim.org/)?
(In reply to comment #3) > I believe you that the change works as expected, but I can't tell if it is the > correct fix. Could you please propose it to gajim developers upstream > (http://gajim.org/)? Proposition submitted : https://trac.gajim.org/ticket/7067
Fixed and closed upstream. https://trac.gajim.org/ticket/7067#comment:6
The fix is on the gajim_0.15 branch, so it will get into Fedora with the next upstream beta or final release.
Great :) Thanks for all Michal.
gajim-0.15-0.4.beta4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/FEDORA-2011-15286/gajim-0.15-0.4.beta4.fc16
Package gajim-0.15-0.4.beta4.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gajim-0.15-0.4.beta4.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15286/gajim-0.15-0.4.beta4.fc16 then log in and leave karma (feedback).
Package gajim-0.15-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gajim-0.15-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15286/gajim-0.15-1.fc16 then log in and leave karma (feedback).
gajim-0.15-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.