Kontact/KMail recieved SIGSEGV while deleting message...

Bug #117363 reported by Michael D. Stemle, Jr.
6
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: kontact

I had more than 200 messages after not checking for a while. I have several filters set up for mailing lists, and I had about 60 messages in my LoCo's mailing list folder. I went through them all skimming and reading, then when I reached the end I hit Ctrl-A and the delete key. Kontact then crashed with a SIGSEGV.

This is kontact/kmail/kdepim from the KDE 3.5.7 kubuntu.org repositories.

Stack trace:
(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found) [several "no debugging symbols found" lines removed]
[Thread debugging using libthread_db enabled]
[New Thread 47362368343600 (LWP 8827)]
[New Thread 1107310912 (LWP 8944)]
[New Thread 1098918208 (LWP 8943)]
[New Thread 1090525504 (LWP 8942)]
[New Thread 1082132800 (LWP 8941)]
(no debugging symbols found) [several "no debugging symbols found" lines removed]
[KCrash handler]
#5 0x00002b136f27bf7b in FolderStorage::moveMsg ()
   from /usr/lib/libkmailprivate.so
#6 0x00002b136f31773a in KMMoveCommand::execute ()
   from /usr/lib/libkmailprivate.so
#7 0x00002b136f29b080 in KMCommand::slotPostTransfer ()
   from /usr/lib/libkmailprivate.so
#8 0x00002b136f4abd73 in KMCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#9 0x00002b136f4ac099 in KMMenuCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#10 0x00002b136f4ac11d in KMMoveCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#11 0x00002b136f4ac159 in KMDeleteMsgCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#12 0x00002b13622f4ce2 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#13 0x00002b136f29b1b0 in KMCommand::messagesTransfered ()
   from /usr/lib/libkmailprivate.so
#14 0x00002b136f36734a in KMCommand::transferSelectedMsgs ()
   from /usr/lib/libkmailprivate.so
#15 0x00002b136f4abd87 in KMCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#16 0x00002b136f4ac099 in KMMenuCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#17 0x00002b136f4ac11d in KMMoveCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#18 0x00002b136f4ac159 in KMDeleteMsgCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#19 0x00002b13622f4ce2 in QObject::activate_signal ()
   from /usr/lib/libqt-mt.so.3
#20 0x00002b1362662ec9 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#21 0x00002b1362313e37 in QSignal::activate () from /usr/lib/libqt-mt.so.3
#22 0x00002b136231ae6a in QSingleShotTimer::event ()
   from /usr/lib/libqt-mt.so.3
#23 0x00002b13622901d6 in QApplication::internalNotify ()
   from /usr/lib/libqt-mt.so.3
#24 0x00002b1362291f65 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#25 0x00002b13619b34f8 in KApplication::notify ()
   from /usr/lib/libkdecore.so.4
#26 0x00002b1362222cc2 in QApplication::sendEvent ()
   from /usr/lib/libqt-mt.so.3
#27 0x00002b1362283490 in QEventLoop::activateTimers ()
   from /usr/lib/libqt-mt.so.3
#28 0x00002b13622373ef in QEventLoop::processEvents ()
   from /usr/lib/libqt-mt.so.3
#29 0x00002b13622a970b in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#30 0x00002b13622a9513 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#31 0x00002b1362291c9c in QApplication::exec () from /usr/lib/libqt-mt.so.3
#32 0x000000000041dc12 in ?? ()
#33 0x00002b136148f8e4 in __libc_start_main () from /lib/libc.so.6
#34 0x0000000000415a19 in ?? ()
#35 0x00007fff4b345c48 in ?? ()
#36 0x0000000000000000 in ?? ()

Revision history for this message
Rich Johnson (nixternal) wrote :

Hey Michael. I have never experienced a crash when deleting a mass amount of email at a time. I get all of the wiki edit emails, so a few hundred a day, and after skimming and making sure they aren't spam, I do a ctrl-a delete. This usually deletes around 200+ emails at one time. It is a little slow, but never crashed. Has this happened more than once? Was there updates recently and if so, does it still crash after this?

Changed in kdepim:
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :
Download full text (8.3 KiB)

I'm experiencing this problem on Gutsy. Here's the stack trace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/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 -1243248960 (LWP 16763)]
[New Thread -1287484528 (LWP 16767)]
[New Thread -1279091824 (LWP 16766)]
[New Thread -1270699120 (LWP 16765)]
[New Thread -1262306416 (LWP 16764)]
(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 symb...

Read more...

Revision history for this message
Michael D. Stemle, Jr. (manchicken) wrote :

I've noticed some additional patterns here.

First, this seems to happen only when kmail is telling me that there are more messages in a folder than there are on the filesystem.

Second, if you delete the messages on the filesystem and then restart kontact/kmail, when you try to view the folder it seems to correct itself.

My guess is that the bug is actually happening before the crash when the index first gets out of whack, and then afterwards it's just crashing because it's not able to handle an index that disagrees with the filesystem.

Revision history for this message
Luka Renko (lure) wrote :

This bug should be fixed with last version in gutsy. If you still experience the problem, feel free to reopen or open new bug with stack track information.

Changed in kdepim:
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.