Version: 1.9.1 (using KDE KDE 3.5.2) Installed from: Gentoo Packages Compiler: gcc-4.1.0 OS: Linux When trying to check new mail I get this error: "The process for the imap://imap.phys.uu.nl protocol died unexpectedly." in .xsession-errors, the relevant error is: "kioslave: ####### CRASH ###### protocol = imap pid = 22627 signal = 11" which was produced by starting kmail, clicking on check new mail, entering password, clicking ok on error message and closing kmail.
Please try to compile the imap4 kioslave with debug symbols as otherwise this doesn't help very much.
I compiled the package kde-base/kdepim-kioslaves with debug use-flag and now everything works. Recompiling again without that flag recreates the problem.
Strange, but no kmail problem ;-) Seems an installation issue.
I'm now on kde 3.5.3 and kmail 1.9.3 and the problem has returned full force. The previous workaround of compiling kde-base/kdepim-kioslaves with debug use-flag worked most of the time, but now it has stopped working. Relevant .xsession-errors output: IMAP4::kdemain kio_imap: IMAP4::dispatch - command=85 kio_imap: IMAP4::dispatch - command=48 kio_imap: IMAP4::dispatch - command=49 kio_imap: IMAP4::makeLogin - checking login kio_imap: IMAP4::makeLogin - alreadyConnected false kio_imap: myAuth: NTLM kio_imap: imapParser::parseLoop - unhandledResponse: kio_imap: * OK Microsoft Exchange IMAP4rev1 server version 5.5.2658.25 (xeon.phys.uu.nl) ready kio_imap: kio_imap: IMAP4: setHost: capability kio_imap: 'imap4' kio_imap: 'imap4rev1' kio_imap: 'idle' kio_imap: 'literal+' kio_imap: 'login-referrals' kio_imap: 'mailbox-referrals' kio_imap: 'namespace' kio_imap: 'auth=ntlm' kio_imap: IMAP4::makeLogin - attempting login kio_imap: IMAP4::makeLogin - open_PassDlg said user=mschoutn pass=xx kio_imap: aAuth: NTLM FQDN: imap.phys.uu.nl isSSL: false kio_imap: sasl_interact kio_imap: SASL_INTERACT id: 16386 kio_imap: SASL_CB_[USER|AUTHNAME]: 'mschoutn' kio_imap: SASL_INTERACT id: 16388 kio_imap: SASL_CB_PASS: [hidden] kioslave: ####### CRASH ###### protocol = imap pid = 24774 signal = 11
Any chance you can get us backtrace of kio_imap?
I've been able to produce something. If this is no good, please tell me how to get what you need. (gdb) continue Continuing. [New Thread 1082132816 (LWP 10882)] [New Thread 1090525520 (LWP 10886)] Program received signal SIGSEGV, Segmentation fault. 0x00002b81d169c8c0 in ntlm_client_mech_step () from /usr/lib64/sasl2/libntlm.so.2 Current language: auto; currently c (gdb) bt #0 0x00002b81d169c8c0 in ntlm_client_mech_step () from /usr/lib64/sasl2/libntlm.so.2 #1 0x00002b81d0870ff2 in sasl_client_step () from /usr/lib64/libsasl2.so.2 #2 0x00002b81d0745f12 in imapParser::clientAuthenticate () from /usr/kde/3.5/lib64/kde3/kio_imap4.so #3 0x00002b81d074785c in IMAP4Protocol::makeLogin () from /usr/kde/3.5/lib64/kde3/kio_imap4.so #4 0x00002b81d074bdf9 in IMAP4Protocol::openConnection () from /usr/kde/3.5/lib64/kde3/kio_imap4.so #5 0x00002b81cc7ff728 in KIO::SlaveBase::dispatch () from /usr/kde/3.5/lib64/libkio.so.4 #6 0x00002b81d073b8fd in IMAP4Protocol::dispatch () from /usr/kde/3.5/lib64/kde3/kio_imap4.so #7 0x00002b81cc817f34 in KIO::SlaveBase::dispatchLoop () from /usr/kde/3.5/lib64/libkio.so.4 #8 0x00002b81d073c6f8 in kdemain () from /usr/kde/3.5/lib64/kde3/kio_imap4.so #9 0x0000000000407ca6 in launch () #10 0x00000000004085f2 in handle_launcher_request () #11 0x00000000004089f2 in handle_requests () #12 0x0000000000409286 in main () #13 0x00002b81d023c134 in __libc_start_main () from /lib/libc.so.6 #14 0x0000000000404d29 in _start () (gdb)
I am having the same issues with smtp to when ever I want to use TLS encryption. You can watch the gentoo bug at: http://bugs.gentoo.org/show_bug.cgi?id=129014
This bug is open for over 6 months now. Any news?
Reassigning the bugs of the SMTP, IMAP and POP ioslaves to kdepim-bugs.
Undo autoconfirm.
(In reply to comment #7) > I am having the same issues with smtp to when ever I want to use TLS > encryption. You can watch the gentoo bug at: > http://bugs.gentoo.org/show_bug.cgi?id=129014 according to that bug report, this is fixed.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Unmaintained, replaced by kimap