Bug 182152

Summary:	Crash when deleting messages from an IMAP account
Product:	[Unmaintained] kmail	Reporter:	Bernhard Rosenkraenzer <bero>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, christophe
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bernhard Rosenkraenzer 2009-01-28 12:26:07 UTC

Version:            (using KDE 4.2.0)
Compiler:          gcc 4.3.3 
OS:                Linux
Installed from:    Unlisted Binary Package

kmail crashes occasionally when deleting (shift-delete, not moving to trash) a message on an imap server.

As usual, this doesn't happen while you're trying to get a backtrace out of it -- I'll attach one the next time it happens. ;)

Comment 1 Christophe Marin 2009-01-28 12:30:50 UTC

-- I'll attach one the next time it happens. ;)

Please reopen this report when you will have a backtrace.

Comment 2 Bernhard Rosenkraenzer 2009-01-28 13:44:45 UTC

Backtrace (unfortunately from a version that wasn't built with full debug info, but the parts that are there are better than nothing):

#0  0x44b92ed1 in ?? () from /usr/lib/libkmailprivate.so.4
#1  0x44a2df16 in ?? () from /usr/lib/libkmailprivate.so.4
#2  0x44a435e5 in ?? () from /usr/lib/libkmailprivate.so.4
#3  0x44b487e8 in KMMoveCommand::execute () from /usr/lib/libkmailprivate.so.4
#4  0x44b35c42 in KMCommand::slotPostTransfer () from /usr/lib/libkmailprivate.so.4
#5  0x44b40705 in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#6  0x44b40c22 in KMMoveCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#7  0x41b69bf5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#8  0x41b6a8e5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#9  0x44b31375 in KMCommand::messagesTransfered () from /usr/lib/libkmailprivate.so.4
#10 0x44b4b32c in KMCommand::transferSelectedMsgs () from /usr/lib/libkmailprivate.so.4
#11 0x44b4b502 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so.4
#12 0x44b4071c in KMCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#13 0x44b40c22 in KMMoveCommand::qt_metacall () from /usr/lib/libkmailprivate.so.4
#14 0x41b69bf5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#15 0x41b6a8e5 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x41b6f2e5 in ?? () from /usr/lib/libQtCore.so.4
#17 0x41b6f42c in ?? () from /usr/lib/libQtCore.so.4
#18 0x41b63dcb in QObject::event () from /usr/lib/libQtCore.so.4
#19 0x4219b2ac in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#20 0x421a39f5 in QApplication::notify() from /usr/lib/libQtGui.so.4
#21 0x42dfbd11 in KApplication::notify() from /usr/lib/libkdeui.so.5
#22 0xbfcf5978 in ?? ()
#23 0x0a6e3c18 in ?? ()
#24 0xbfcf555c in ?? ()
#25 0x09843a28 in ?? ()
#26 0x09843c3c in ?? ()
#27 0xbfcf55b0 in ?? ()
#28 0x4c26c06d in ?? () from /lib/libc.so.6
#29 0x41a7ee22 in QListData::remove () from /usr/lib/libQtCore.so.4
#30 0x41b5325e in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#31 0x41b83a85 in ?? () from /usr/lib/libQtCore.so.4
#32 0x41b83d30 in QEventDispatcherUNIX::processEvents() from /usr/lib/libQtCore.so.4
#33 0x4223f9c4 in ?? () from /usr/lib/libQtGui.so.4
#34 0x41b51823 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#35 0x41b51c72 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#36 0x41b54116 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#37 0x4219b114 in QApplication::exec () from /usr/lib/libQtGui.so.4
#38 0x0804a5ff in _start ()

Comment 3 Dario Andres 2009-01-29 14:40:56 UTC

This is probably a duplicate of bug 163071 (description matches, similar backtrace too)

Comment 4 Bernhard Rosenkraenzer 2009-01-29 15:14:37 UTC

I haven't seen this happening when moving messages to the trash yet (as in bug 163071), only when deleting them right away...

May still be the same thing though, given moving a message also deletes it from the original folder.

Comment 5 Christophe Marin 2009-03-09 10:45:19 UTC


*** This bug has been marked as a duplicate of bug 163071 ***