Bug 155026

Summary:	Crash after canceling IMAP download
Product:	[Unmaintained] kmail	Reporter:	kodefoo
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	andresbajotierra, bjoern, bruce, christophe, greg.martyn, jacob.benoit.1, jtamate, kde-bugzilla, nathanogden76
Priority:	NOR
Version:	enterprise
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description kodefoo 2008-01-03 16:02:08 UTC

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 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)
[KCrash handler]
#5  0x00002b1c242ce599 in QMetaObject::findSignal ()
   from /usr/lib/libqt-mt.so.3
#6  0x00002b1c242de6d5 in QObject::disconnect () from /usr/lib/libqt-mt.so.3
#7  0x00002b1c2e6ed2a1 in KMail::ActionScheduler::fetchTimeOut ()
   from /usr/lib/libkmailprivate.so
#8  0x00002b1c2e6f0a6d in KMail::ActionScheduler::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#9  0x00002b1c242dcd76 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#10 0x00002b1c242dd910 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#11 0x00002b1c2464c9a2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#12 0x00002b1c24303257 in QTimer::event () from /usr/lib/libqt-mt.so.3
#13 0x00002b1c242782a2 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#14 0x00002b1c2427a031 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#15 0x00002b1c22f00248 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#16 0x00002b1c2420ad12 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#17 0x00002b1c2426b55c in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#18 0x00002b1c2421f443 in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#19 0x00002b1c242917e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#20 0x00002b1c242915ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#21 0x00002b1c24279d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#22 0x0000000000419122 in ?? ()
#23 0x00002b1c27bdfb44 in __libc_start_main () from /lib/libc.so.6
#24 0x0000000000418939 in ?? ()
#25 0x00007fff8c1edcc8 in ?? ()
#26 0x0000000000000000 in ?? ()

Comment 1 Thomas McGuire 2008-01-05 22:20:10 UTC

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

Comment 2 Thomas McGuire 2008-02-05 15:04:23 UTC

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

Comment 3 Christophe Marin 2008-11-19 12:37:00 UTC

Closing due to lack of feedback (comment #1)

Comment 4 Jaime Torres 2008-11-26 13:01:02 UTC

Posibly has a dup in bug 175943

Comment 5 Thomas McGuire 2008-11-27 17:41:33 UTC

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

Comment 6 Thomas McGuire 2008-11-27 17:43:12 UTC

Reopening because of the duplicate.

Comment 7 Jaime Torres 2008-12-04 12:41:48 UTC

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

Comment 8 Dario Andres 2008-12-14 19:14:46 UTC

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

Comment 9 Dario Andres 2009-01-21 01:21:34 UTC

Isn't this related to bug 136437 ?

Comment 10 Dario Andres 2009-01-21 01:22:41 UTC

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

Comment 11 Jaime Torres 2009-03-15 10:35:33 UTC

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).

Comment 12 Dario Andres 2009-05-29 20:03:18 UTC

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

Comment 13 Björn Ruberg 2010-01-14 01:58:38 UTC

Can anybody report about the situation in KDE 4.3?

Comment 14 Bruce Cran 2010-04-25 03:28:36 UTC

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.

Comment 15 Myriam Schweingruber 2012-08-19 11:07:39 UTC

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