Hide Forgot
Description of problem: I somehow managed to get evolution to stall/hang while fetching new mail. I.e. the mail fetching threads seems to fetch forever the new mail, but never fetches anything. Version-Release number of selected component (if applicable): Stack traces: evolution [8861] [cores: 0] Thread [13] 8862 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 read() at 0x43ed485b 0x43fb585b 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [12] 8863 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 g_poll() at 0x43fc87cc 0x43fb9c06 g_main_loop_run() at 0x43fba337 0x4444e18b 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [11] 8864 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 g_poll() at 0x43fc87cc 0x43fb9c06 g_main_loop_run() at 0x43fba337 0xf5d8f235 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [10] 8865 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 0x44ec275f 0x44ec2fa0 0x4503ab74 0x4503d715 0x4503dc8e 0x45037735 0x4503ed75 SSL_ForceHandshake() at 0x4503f248 rehandshake_ssl() at camel-tcp-stream-ssl.c:708 0x4b8c538c tcp_stream_ssl_connect() at camel-tcp-stream-ssl.c:749 0x4b8c558b camel_tcp_stream_connect() at camel-tcp-stream.c:107 0x4b8c65f4 network_service_connect_sync() at camel-network-service.c:117 0x4b8a0f26 camel_network_service_connect_sync() at camel-network-service.c:227 0x4b8a1110 connect_to_server() at camel-imap-store.c:247 0xef816ae0 connect_to_server_wrapper() at camel-imap-store.c:612 0xef816ae0 imap_store_connect_sync() at camel-imap-store.c:906 0xef817551 camel_service_connect_sync() at camel-service.c:1.018 0x4b8b1e7b camel_imap_store_connected() at camel-imap-store.c:3.185 0xef81461d replay_offline_journal() at camel-imap-folder.c:335 0xef8038e0 imap_synchronize_sync() at camel-imap-folder.c:1.654 0xef80b06e camel_folder_synchronize_sync() at camel-folder.c:3.622 0x4b8993e1 refresh_folders_exec() at mail-send-recv.c:988 0xf60d3c78 mail_msg_proxy() at mail-mt.c:416 0xf60cf2ea 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [9] 8867 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 0x44ec275f 0x44ec2fa0 0x4503ab74 0x4503d715 0x4503dc8e 0x45037735 0x4503ed75 SSL_ForceHandshake() at 0x4503f248 rehandshake_ssl() at camel-tcp-stream-ssl.c:708 0x4b8c538c tcp_stream_ssl_connect() at camel-tcp-stream-ssl.c:749 0x4b8c558b camel_tcp_stream_connect() at camel-tcp-stream.c:107 0x4b8c65f4 network_service_connect_sync() at camel-network-service.c:117 0x4b8a0f26 camel_network_service_connect_sync() at camel-network-service.c:227 0x4b8a1110 connect_to_server() at camel-imap-store.c:247 0xef816ae0 connect_to_server_wrapper() at camel-imap-store.c:612 0xef816ae0 imap_store_connect_sync() at camel-imap-store.c:906 0xef817551 camel_service_connect_sync() at camel-service.c:1.018 0x4b8b1e7b camel_imap_store_connected() at camel-imap-store.c:3.185 0xef81461d replay_offline_journal() at camel-imap-folder.c:335 0xef8038e0 imap_synchronize_sync() at camel-imap-folder.c:1.654 0xef80b06e camel_folder_synchronize_sync() at camel-folder.c:3.622 0x4b8993e1 refresh_folders_exec() at mail-send-recv.c:988 0xf60d3c78 mail_msg_proxy() at mail-mt.c:416 0xf60cf2ea 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [8] 8868 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 __lll_lock_wait() at 0x43ed44d2 _L_lock_693() at 0x43ecfe63 pthread_mutex_lock() at 0x43ecfca8 g_static_rec_mutex_lock() at 0x43fe1345 camel_service_lock() at camel-service.c:1.124 0x4b8b1976 refresh_refresh() at camel-imap-store.c:2.881 0xef815c4a session_do_job_cb() at camel-session.c:148 0x4b8b2506 0x443ed22e 0x443dd85c 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [7] 8871 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 __lll_lock_wait() at 0x43ed44d2 _L_lock_693() at 0x43ecfe63 pthread_mutex_lock() at 0x43ecfca8 g_static_rec_mutex_lock() at 0x43fe1345 camel_folder_lock() at camel-folder.c:2.978 0x4b897116 camel_folder_refresh_info_sync() at camel-folder.c:3.508 0x4b898f86 refresh_folder_exec() at mail-ops.c:1.272 0xf60d0f1f mail_msg_proxy() at mail-mt.c:416 0xf60cf2ea 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [6] 8872 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 __lll_lock_wait() at 0x43ed44d2 _L_lock_693() at 0x43ecfe63 pthread_mutex_lock() at 0x43ecfca8 g_static_rec_mutex_lock() at 0x43fe1345 camel_service_lock() at camel-service.c:1.124 0x4b8b1976 refresh_refresh() at camel-imap-store.c:2.881 0xef815c4a session_do_job_cb() at camel-session.c:148 0x4b8b2506 0x443ed22e 0x443dd85c 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [5] 8873 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 0x44ec275f 0x44ec2fa0 0x4503ab74 0x4503d715 0x4503dc8e 0x45037735 0x4503ed75 SSL_ForceHandshake() at 0x4503f248 rehandshake_ssl() at camel-tcp-stream-ssl.c:708 0x4b8c538c tcp_stream_ssl_connect() at camel-tcp-stream-ssl.c:749 0x4b8c558b camel_tcp_stream_connect() at camel-tcp-stream.c:107 0x4b8c65f4 network_service_connect_sync() at camel-network-service.c:117 0x4b8a0f26 camel_network_service_connect_sync() at camel-network-service.c:227 0x4b8a1110 connect_to_server() at camel-imap-store.c:247 0xef816ae0 connect_to_server_wrapper() at camel-imap-store.c:612 0xef816ae0 imap_store_connect_sync() at camel-imap-store.c:906 0xef817551 camel_service_connect_sync() at camel-service.c:1.018 0x4b8b1e7b camel_imap_store_connected() at camel-imap-store.c:3.185 0xef81461d refresh_refresh() at camel-imap-store.c:2.884 0xef815c56 session_do_job_cb() at camel-session.c:148 0x4b8b2506 0x443ed22e 0x443dd85c 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [4] 8875 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 0x44ec275f 0x44ec2fa0 0x4503ab74 0x4503d715 0x4503dc8e 0x45037735 0x4503ed75 SSL_ForceHandshake() at 0x4503f248 rehandshake_ssl() at camel-tcp-stream-ssl.c:708 0x4b8c538c tcp_stream_ssl_connect() at camel-tcp-stream-ssl.c:749 0x4b8c558b camel_tcp_stream_connect() at camel-tcp-stream.c:107 0x4b8c65f4 network_service_connect_sync() at camel-network-service.c:117 0x4b8a0f26 camel_network_service_connect_sync() at camel-network-service.c:227 0x4b8a1110 connect_to_server() at camel-imap-store.c:247 0xef816ae0 connect_to_server_wrapper() at camel-imap-store.c:612 0xef816ae0 imap_store_connect_sync() at camel-imap-store.c:906 0xef817551 camel_service_connect_sync() at camel-service.c:1.018 0x4b8b1e7b camel_imap_store_connected() at camel-imap-store.c:3.185 0xef81461d refresh_refresh() at camel-imap-store.c:2.884 0xef815c56 session_do_job_cb() at camel-session.c:148 0x4b8b2506 0x443ed22e 0x443dd85c 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [3] 8877 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 __lll_lock_wait() at 0x43ed44d2 _L_lock_693() at 0x43ecfe63 pthread_mutex_lock() at 0x43ecfca8 g_static_rec_mutex_lock() at 0x43fe1345 camel_folder_lock() at camel-folder.c:2.978 0x4b897116 camel_folder_get_message_sync() at camel-folder.c:3.274 0x4b897e20 folder_get_message_thread() at camel-folder.c:1.077 0x4b898479 0x443ed22e 0x443dd85c 0x43fe334f 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [2] 8878 [core: 0] (Suspended : Container) __kernel_vsyscall() at 0xf775e430 pthread_cond_timedwait@@GLIBC_2.3.2() at 0x43ed1c04 0x4422df32 0x43f8b5a0 g_async_queue_timed_pop() at 0x43f8bf3f 0x43fe3283 0x43fe0ed5 start_thread() at 0x43ecdcd3 clone() at 0x43e0483e Thread [1] 8861 [core: 0] (Suspended : User Request) __kernel_vsyscall() at 0xf775e430 poll() at 0x43df9fb0 g_poll() at 0x43fc87cc 0x43fb9c06 g_main_loop_run() at 0x43fba337 gtk_main() at 0x453060b5 main() at main.c:696 0x8049cb7 any ideas what is going on here?
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.