Bug 830470
| Summary: | Evolution keeps prompting for the password | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | mark gress <mgress> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | lucilanga, mbarnes, mcrha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-13 07:20:05 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: | |||
|
Description
mark gress
2012-06-09 22:56:08 UTC
In addition to being able to send emails outbound, I know it is communicating with both the pop and smtp servers because when I query the servers in the account settings to see what authentication is required by the email server, various options get striked out letting me know which is the proper one to use. I got the email issue solved, but I still can't get it to stop asking for the keyring. It does it every time the computer is restarted. I suspect that it probably would work correctly, if this didn't keep happening: https://bugzilla.redhat.com/show_bug.cgi?id=830468 I installed Seahorse, and that seemed to help smooth things over a bit, but not enough to make evolution seamless, as it should be. Thanks for a bug report and updates on it. If the gnome-keyring is crashing in the background, then it makes sense you are asked for your keyring password whenever evolution requires it. That's why I would mark this as a duplicate of bug #830468, but before that, could you run evolution from a terminal and see whether any keyring related runtime warnings are printed there, please? That way we can confirm that this is related to your issues with key-ring. Alright. What I did here was launch Evolution in konsole, enter the keyring password at the prompt, then close the program. This is what popped up. [user@localhost ~]$ evolution GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. ** (evolution:1025): WARNING **: Unrecognized junk filter name 'Bogofilter' in GSettings [user@localhost ~]$ Thanks for the update. There is actually no warning from keyring. The "using 'memory' GSettings backend" is shown when you do not have installed dconf. It can also happen if you compile your own glib, but do not compile dconf against it. I do not think it's related to your keyring issue. I'm marking this as a duplicate of the crash bug. *** This bug has been marked as a duplicate of bug 830468 *** Thanks for being so prompt and keeping an eye on this. So theoretically, once the other bug is fixed the keyring will stop prompting for the password? (In reply to comment #6) > So theoretically, once the other bug is fixed the keyring will stop > prompting for the password? I guess so, but I do not have any prove for it. Please, feel free to reopen this bug if a fix in keyring will not help. |