Version: 1.13.0 (using 4.4.00 (KDE 4.4.0), Kubuntu packages) Compiler: cc OS: Linux (x86_64) release 2.6.31-19-generic I have 2 IMAP accounts, which I check regularly. Very often (once an hour) one of both accounts does not show me the Inbox mails, but hangs instead waiting. Ctrl-Q closes kontact with kmail, but kmail still is an active process: wr@[kagu]:~> pss kontact 2835 ? Sl 0:41 /usr/bin/kontact 4805 ? S 0:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactft2835.slave-socket 4807 ? S 0:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactth2835.slave-socket 5605 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactRQ2835.slave-socket 5938 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactFh2835.slave-socket 5939 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactvf2835.slave-socket 5940 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactFo2835.slave-socket 5941 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactsl2835.slave-socket 6167 pts/2 R+ 0:00 grep kontact wr@[kagu]:~> kill 2835 wr@[kagu]:~> pss kontact 4805 ? S 0:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactft2835.slave-socket 4807 ? S 0:00 kdeinit4: kio_imap4 [kdeinit] imap local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactth2835.slave-socket 5605 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactRQ2835.slave-socket 5938 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactFh2835.slave-socket 5939 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactvf2835.slave-socket 5940 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactFo2835.slave-socket 5941 ? S 0:00 kdeinit4: kio_http [kdeinit] http local:/tmp/ksocket-wr/klauncherMT2473.slave-socket local:/tmp/ksocket-wr/kontactsl2835.slave-socket 6185 pts/2 S+ 0:00 grep kontact The only chance then to start kontact again is to kill all process with -9! Kill alone does not work here. Summarizing, I see to major show stoppers: 1) kmail's imap processes hang very often 2) closing/starting kontact does not work because of the processes in the background
*** Bug 226606 has been marked as a duplicate of this bug. ***
Thank you for taking the time to file a bug report. KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2. We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.