Description of problem: I don't know exactly. I use kmail as the e-mail client. My company has moved to using Exchange2010, and I am connecting to that by IMAP, unlike all the rest of my colleagues. In fact, they kept IMAP just for me. I have 4 types of problems: 1. Whenever I move mails from my inbox to local folders, it may work correctly or it may hang. 2. Sometimes for unknkown reason, kmail reports that it lost connectivity to server, and then goes into offline mode, then stays in that mode permanently. It is not a network problem, I have checked that repeatedly, I am a network engineer. 3. Sometimes for unknown reasons, either I navigate through mails in local folders or in the imap inbox, kmail goes into thinking about it a lot, and never shows the contents of the mail. 4. Sometimes, when i choose a mail and try to reply it, kmail just crashed alltoghether disapearing from the screen. I suspect in this case that this has to be sth to do with html, usually it happens when in the mail chain there are signatures with pics and/or html, and/or whenever the mail contains a diagram or sth in form of image that shows directly. Once one of these 4 problems manifests, killing processes won't take me out of it. I've tried that numerous times. The only thing that works is rebooting (it's a shame if you think we're talking about linux...) I am currently rebooting 4-5 times per day... One fifth thing... If before I shut down, I forget the kmail closed but with the icon active, when it starts up again, it's going to make a mess out of everything, it opens twice, makes a mess of itself, and I end up having to reboot again. I have html enabled, and I need it actually. I am withstanding the disturbance, but I can't mess up the mail-chain of numerous people everytime I need to reply a mail. If I reply a mail-chain without html, the mail looks terrible, like a bomb disaster... and I get customer complaints for this... Version-Release number of selected component: kdepim-runtime-4.10.1-1.fc17 Additional info: backtrace_rating: 4 cmdline: /usr/bin/akonadi_imap_resource --identifier akonadi_imap_resource_0 crash_function: locking_function executable: /usr/bin/akonadi_imap_resource kernel: 3.7.9-104.fc17.i686.PAE uid: 1001 ureports_counter: 1 var_log_messages: Mar 25 10:50:52 panos-pc abrt[2863]: Saved core dump of pid 1779 (/usr/bin/akonadi_imap_resource) to /var/spool/abrt/ccpp-2013-03-25-10:50:52-1779 (26730496 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 locking_function at ssl/qsslsocket_openssl.cpp:157 #1 CRYPTO_lock at cryptlib.c:600 #2 CRYPTO_add_lock at cryptlib.c:628 #3 int_thread_release at err.c:469 #4 int_thread_get_item at err.c:499 #5 ERR_get_state at err.c:1014 #6 ERR_clear_error at err.c:747 #7 ssl3_connect at s3_clnt.c:196 #8 SSL_connect at ssl_lib.c:933 #9 q_SSL_connect at ssl/qsslsocket_openssl_symbols.cpp:168
Created attachment 717195 [details] File: backtrace
Created attachment 717196 [details] File: cgroup
Created attachment 717197 [details] File: core_backtrace
Created attachment 717198 [details] File: dso_list
Created attachment 717199 [details] File: environ
Created attachment 717200 [details] File: limits
Created attachment 717201 [details] File: maps
Created attachment 717202 [details] File: open_fds
Created attachment 717203 [details] File: proc_pid_status
Created attachment 717204 [details] File: smolt_data
Created attachment 717206 [details] File: xsession_errors
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.