| Summary: | evolution stalls while fetching new mail | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Meyer <thomas.mey> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED NOTABUG | 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: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-10 10:20:07 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
Thomas Meyer
2012-01-04 18:33:34 UTC
version is: evolution.i686 3.2.2-1.fc16 @updates evolution-data-server.i686 3.2.2-2.fc16 @updates evolution-data-server-debuginfo.i686 3.2.2-2.fc16 installed evolution-debuginfo.i686 3.2.2-1.fc16 installed evolution also warns me that I need to work online to complete the refresh of the Inbox. the funny thing is, that the online/offline icon tells me that I'm online... And in the File menu I can switch to "offline". Thanks for a bug report. The backtrace seems to try to connect to your server, while it got stuck on SSL handshake, probably. Better to get backtrace through gdb, with a command like this: $ gdb --batch --ex "t a a bt" -pid=PID &>bt.txt where PID is a process ID of a running process, evolution in this case. The massage about not being online seems odd. Maybe caused by a failure to connect to the server, where it's same as not being connected to the network. I've not much idea where to follow. Try run evolution in offline (evolution --offline) and then switch it to online, whether will anything change. Also see evolution's console, in case it'll write there anything useful. $ evolution --offline (evolution:30274): evolution-shell-CRITICAL **: shell_settings_pspec_for_key: assertion `schema_name != NULL' failed Then I select "go online" and get: (evolution:30274): GLib-GObject-WARNING **: g_object_set_property: object class `EShellSettings' has no property named `start-offline' what's going on here? okay switching to plain text connection, i.e. non-ssl-connection makes evolution fetch mail again. did something broke the ssl support, or do I need to worry about my system? (In reply to comment #4) > $ evolution --offline > > (evolution:30274): evolution-shell-CRITICAL **: shell_settings_pspec_for_key: > assertion `schema_name != NULL' failed > > Then I select "go online" and get: > > (evolution:30274): GLib-GObject-WARNING **: g_object_set_property: object class > `EShellSettings' has no property named `start-offline' > > what's going on here? It means the corresponding key is missing in schema file. That's not much issue except of non-functionality of a certain part, which is not that crucial in this case. (In reply to comment #5) > okay switching to plain text connection, i.e. non-ssl-connection makes > evolution fetch mail again. did something broke the ssl support, or do I need > to worry about my system? Evolution is using nss/nspr for SSL connections, and I do not expect any issues in these libraries, though one never knows. If you updated one of them recently, and the connection worked fine before the update, then maybe it takes its part on the issue. The other option can be just a coincidence with your server dropping SSL connections, and/or not responding on the port evolution is using for SSL connections. You can ask your server admin/support what port is used to connect to it with SSL and then change the options in evolution. Note such change requires evolution's restart. You surely know, but just in case, without SSL your email account password is sent towards the server in a clear form. Hi, I found out was the problem was. I switched from imap to imap+. What I didn't notice was that with this changed the port were automatically reset from 993 to 143. The change itself seems only to be in effect with the next start of the application. so as I very rarely reboot my machine, I did not notice the error for a week or so. with the next start of evolution I began to see the error/warning message to try again in "online mode". so this is the reason for the confusion here! sorry for the noise! a better error message would be really helpful for an failed ssl handshake! does evolution warn one when you change the settings, that you need to restart evolution to make the changes active? (In reply to comment #7) > Hi, I found out was the problem was. I switched from imap to imap+. What I > didn't notice was that with this changed the port were automatically reset from > 993 to 143. Thanks for the update. Good you have it working again. I'm not sure why it changed the port number, it may not do that just on the account type change, though it's possible it can do it silently on account information "transition" from one account type to the other. > The change itself seems only to be in effect with the next start of the > application. so as I very rarely reboot my machine, I did not notice the error > for a week or so. with the next start of evolution I began to see the > error/warning message to try again in "online mode". so this is the reason for > the confusion here! sorry for the noise! a better error message would be really > helpful for an failed ssl handshake! It doesn't know that at the moment of the freeze, it's just waiting for a response from the server, and only after it timeouts it claims to a user. The thing is that the timeout is quite long. > does evolution warn one when you change the settings, that you need to restart > evolution to make the changes active? Nope, it doesn't. For years, sadly. It's a (semi)known issue of evolution. I'm closing this, as you found the issue. |