| Summary: | boring accept-ssl-certicate question on every start | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Heiko Adams <bugzilla> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | lucilanga, mbarnes, mcrha |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | evolution-3.3.2 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-11-24 10:30:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Heiko Adams
2011-11-10 22:39:43 UTC
Sounds like a bad or expired certificate. Were the certificate valid it wouldn't do that. That's a possibility but as I wrote it would be enough if evolution asks one time if I accept that certicate until the cert changes again. I noticed similar behaviour with IMAP account too, but it cured on its own after some time, without anything being changed from my side. I guess there is something with the nss database, which prevents it from updating, or something with folder ~/.camel_certs ? So if you're right, deleting ~/.camel_certs should solve this problem? I wouldn't delete that folder, you can always try with renaming it to something else with closed evolution. As I said, the issue disappeared for an unknown reason to me on its own after some time. I would like to know what fixed it, but I do not. Maybe I run older evolution, which saved the cert properly, and then the newer was able to use it. I'll retest this later and let you know, though I would prefer to see this bug filled in Gnome's bugzilla, because Fedora package doesn't have any change in this area from the upstream code. I renamed my ~/.camel_certs, then run evolution and I received a prompt about bad certificate. I pressed OK, then the folder was created and the certificate was stored there. The next start evolution didn't claim on the bad certificate any more. I also noticed a warning on console of evolution: camel-WARNING **: Could not load cert /home/mcrha/.camel_certs/cert-id: Failed to open file '/home/mcrha/.camel_certs/cert-id': No such file or directory Which makes sense, the folder was renamed. To answer your question from comment #4: yes, please, rename the ~/.camel_certs and run evolution, whether it'll create and save the certificate into the folder. It would be good to run evolution from console, to see any warnings it may claim (I would try with the old ~/.camel_certs too, and fix an issue it'll claim about - I suppose it'll claim the reason there). The Problem seems to be solved after renaming ~/.camel_certs an restarting evolution. Does the previous folder or inner file have set attributes preventing write to it or an ownership is not correct after restore from backup or anything, please? It would be good to know what was wrong with the folder or its content before closing this bug report. I'm sorry but I can't tell you because i deleted the folder instead of renaming OK, no problem. I made some changes upstream, which made sure the certificate database is saved as soon as the dialog about bad certificate is finished, thus any later crash or anything will not do an issue, just the opposite. This is part of 3.3.2 of evolution/evolution-data-server. |