Bug 967370
| Summary: | Couldn't change keyring password | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Per Nystrom <centaur> | ||||
| Component: | mate-keyring | Assignee: | Dan Mashal <dan.mashal> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | dan.mashal, debarshir, fedora, mclasen, rdieter, stefw | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-09-28 15:51:43 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
Mate went and forked gnome-keyring *completely* needlessly. You probably have mate-keyring installed instead of gnome-keyring. This is completely up to the mate guys to fix, if they want seahorse to work with their fork. Which desktop manager you use? Is there a any login keyring file in ~.config/mate/keyrings ? I switched to lightdm after finding out that the default gdm was not reacting to things like shutting the laptop lid under MATE. Since then, the prompts for the keyring password after login have stopped -- though I'm not sure if the two are related. However, I do still get the same error message in seahorse if I try to change the keyring password. There is a login keyring file in this directory: $ ls ~/.config/mate/keyrings login.keyring user.keystore Using lightdm is a good choice in this case, because lightdm did the the pam mate-keyring authorization for MATE, without them no login key is writen to ~/.config/mate/keyrings. @seahorse Maybe there is a conflict with the old login keyrings stored in a directory from gnome. But i don't know the directory. I suggest to delete all login.keyring user.keystore in user directory. After a logout/login you will find new keys in ~/.config/mate/keyrings. Maybe this helps. In general seahorse is working in my MATE session and i can change the password from my keys. @Stef Walter Is 'org.gnome.keyring.InternalUnsupportedGuiltRiddenInterface' a gsetting key or dbus stuff? @Per Nystrom Did you uninstalled gnome-keyring? gnome-keyring is also needed in MATE, some applications need them, ie. network-manager for storing the wifi password. @Wolfgang Ulbrich I did not uninstall gnome-keyring. Regarding your suggestion to remove the old keyrings, I will try that and let you know. (In reply to Wolfgang Ulbrich from comment #5) > @Stef Walter > > Is 'org.gnome.keyring.InternalUnsupportedGuiltRiddenInterface' a gsetting > key or dbus stuff? It's an internal gnome-keyring dbus interface. @ Stef Walter There is a plan from MATE to switch to gnome-keyring 'IF IT WORKS FOR OTHER DESKTOPS' First tests shows me we run in probs with ssh. Is there a way to communicate with you about this per irc chanel or email? Sounds good. I'm stefw or stefw on IRC at gimpnet. Talk to you soon. Does this issue still exits? no user action since 5 month! |
Created attachment 753399 [details] Screenshot of seahorse error Description of problem: I recently upgraded to Fedora 18 and the MATE desktop, and now when I log in I have to manually enter the keyring password. I understand this can be fixed if I change the keyring password to match my user login password, but when I attempt to do this using Seahorse I get "Couldn't change keyring password" -- see attached screen shot. Version-Release number of selected component (if applicable): $ rpm -q seahorse seahorse-3.6.3-1.fc18.x86_64 How reproducible: 100% Steps to Reproduce: 1. Start seahorse 2. Right click on the login keyring, select change password 3. Error message appears Actual results: Expected results: Additional info: