https://bugs.kde.org/show_bug.cgi?id=319783

            Bug ID: 319783
           Summary: IMAP resource hangs
    Classification: Unclassified
           Product: Akonadi
           Version: 1.9.1
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: IMAP resource
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]

I have 3 IMAP accounts configured:
1) gmail
2) dovecot server
3) company exchange server

I boot up my computer and everything works fine, I can send and receive emails,
but after a while exchange connections seems to hang, it doesn't throw any
errors, but it doesn't notice any new messages (either with periodic checks or
when I click to check new messages).
If I restart exchange agent in kmail->settings->account it starts to work
again, restarting whole akonadi also fixes this issue.
Most of the time this happens without any indication, there is nothing that
tells me to restart exchange imap agent, but once in awhile my exchange account
gets marked as crashed in kmail with message that it was crashed and cannot be
restarted. It never triggered bug report window as with any other crash I've
had with KDE apps.
This is very annoying since most of the time it hits me when I have unread
emails I'm unaware of.

I've attached gdb to exchange akonadi imap resource process, after a while I've
got this crash:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f4cad0f6700 (LWP 3973)]
QSslSocketBackendPrivate::transmit (this=0x7f4ca8133df0) at
ssl/qsslsocket_openssl.cpp:1004

If there is any other way I can help to debug this issue just let me know.

Reproducible: Always

Steps to Reproduce:
1. start kmail with IMAP exchange connection
2. sit and wait
Actual Results:  
New emails are not fetched be kmail

Expected Results:  
New messages should be fetched by kmail

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Kdepim-bugs mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kdepim-bugs

Reply via email to