Kmail crashes with segfault in KMail::ActionScheduler::fetchTimeOut

[Jesse Ruffin]

Binary package hint: kdepim

Didn't change anything that I know of, but all of sudden KMail, and kontact when loading the mail pane, crash reliably shortly after finishing checking the server for mail. Backtrace attached.

lsb_release -rd:
Description: Ubuntu 8.10
Release: 8.10

apt-cache policy kmail:
kmail:
  Installed: 4:4.1.3-0ubuntu1~intrepid2
  Candidate: 4:4.1.3-0ubuntu1~intrepid2
  Version table:
 *** 4:4.1.3-0ubuntu1~intrepid2 0
        500 http://us.archive.ubuntu.com intrepid-updates/main Packages
        100 /var/lib/dpkg/status
     4:4.1.2-0ubuntu2 0
        500 http://us.archive.ubuntu.com intrepid/main Packages

[Kodefoo (kodefoo)]

Version: 1.9.6 (using KDE KDE 3.5.8)
Installed from: Ubuntu Packages
OS: Linux

I had set up some new filters to move mail around within Kontact/Kmail. I selected several larger emails from my inbox and ran the filters manually. One of the emails was taking a long time to download so I cancelled the job. Nothing seemed to happen for ten or fifteen seconds. I was able to click on other folders and bring up messages. Then the entire app crashed. I have been able to repeat this multiple times.

Backtrace:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47399937843856 (LWP 14137)]
[New Thread 1107310928 (LWP 14141)]
[New Thread 1098918224 (LWP 14140)]
[New Thread 1090525520 (LWP 14139)]
[New Thread 1082132816 (LWP 14138)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbo...

[Mcguire-c (mcguire-c)]

Please provide a backtrace, see
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

[Mcguire-c (mcguire-c)]

*** Bug 157091 has been marked as a duplicate of this bug. ***

[Cgiboudeaux (cgiboudeaux)]

Closing due to lack of feedback (comment #1)

[Jtamate (jtamate)]

Posibly has a dup in bug 175943

[Mcguire-c (mcguire-c)]

*** Bug 175943 has been marked as a duplicate of this bug. ***

[Mcguire-c (mcguire-c)]

Reopening because of the duplicate.

[Jtamate (jtamate)]

*** Bug 176839 has been marked as a duplicate of this bug. ***

[Dario Andres (andresbajotierra)]

*** Bug 177727 has been marked as a duplicate of this bug. ***

[Dario Andres (andresbajotierra)]

Isn't this related to bug 136437 ?

[Dario Andres (andresbajotierra)]

*** Bug 181432 has been marked as a duplicate of this bug. ***

[Jtamate (jtamate)]

It does not crash for me in kde 4.2.65 >= 20090226 (opensuse factory builds) filtering >140 spam messages manually (first using a dimap account and then an imap account).

[Dario Andres (andresbajotierra)]

*** Bug 136437 has been marked as a duplicate of this bug. ***

[Björn Ruberg (bjoern-ruberg-wegener)]

Can anybody report about the situation in KDE 4.3?

[Bruce Cran (bruce-cran-org)]

I've seen regular crashes when closing KMail as an IMAP operation is going on with KDE 4.4.1. gdb ends up crashing though so I've not got a backtrace yet.

[Jonathan Thomas (echidnaman)]

Closing in favor of tracking this at the upstream bug task: http://bugs.kde.org/show_bug.cgi?id=155026

[Myriam Schweingruber (myriam)]

Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding