KMail crashed in KMHeaders::msgRemoved

Bug #138458 reported by Daniel Hahler on 2007-09-09
Affects Status Importance Assigned to Milestone
kdepim (Ubuntu)

Bug Description

While deleting some mails in an IMAP folder, KMail from Ubuntu Gutsy crashed:

Using host libthread_db library "/lib/tls/i686/cmov/".
[Thread debugging using libthread_db enabled]
[New Thread -1251079984 (LWP 23773)]
[New Thread -1284101232 (LWP 23779)]
[New Thread -1275708528 (LWP 23778)]
[New Thread -1267315824 (LWP 23777)]
[New Thread -1258923120 (LWP 23776)]
[KCrash handler]
#6 0xb7be6973 in KMHeaders::msgRemoved (this=0x87aaf10, id=4,
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/headeritem.h:126
#7 0xb7befa29 in KMHeaders::qt_invoke (this=0x87aaf10, _id=113,
    _o=0xbfcd0860) at ./kmheaders.moc:309
#8 0xb5f8b893 in QObject::activate_signal (this=0x8588ad0, clist=0x8e732f0,
    o=0xbfcd0860) at kernel/qobject.cpp:2356
#9 0xb7c22a20 in KMFolder::msgRemoved (this=0x8588ad0, t0=4, t1=@0xbfcd08d8)
    at ./kmfolder.moc:261
#10 0xb7c236ad in KMFolder::qt_emit (this=0x8588ad0, _id=9, _o=0xbfcd0950)
    at ./kmfolder.moc:402
#11 0xb5f8b867 in QObject::activate_signal (this=0x8589518, clist=0x858a018,
    o=0xbfcd0950) at kernel/qobject.cpp:2354
#12 0xb7c41700 in FolderStorage::msgRemoved (this=0x8589518, t0=4,
    t1=@0xbfcd09c8) at ./folderstorage.moc:322
#13 0xb7c43393 in FolderStorage::take (this=0x8589518, idx=4)
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/folderstorage.cpp:454
#14 0xb7cdac20 in KMFolderImap::take (this=0x8589518, idx=4)
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/kmfolderimap.cpp:599
#15 0xb7c4023e in FolderStorage::take (this=0x8589518, msgList=@0xbfcd0a2c)
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/folderstorage.cpp:468
#16 0xb7cda513 in KMFolderImap::take (this=0x8589518, msgList=@0xbfcd0a6c)
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/kmfolderimap.cpp:607
#17 0xb7c22e19 in KMFolder::take (this=0x8588ad0, msgList=@0xbfcd0ae4)
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/kmfolder.cpp:378
#18 0xb7cd88e1 in KMFolderImap::addMsgQuiet (this=0x85995d8,
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/kmfolderimap.cpp:379
#19 0xb7cdc423 in KMFolderImap::qt_invoke (this=0x85995d8, _id=10,
    _o=0xbfcd0c14) at ./kmfolderimap.moc:323
#20 0xb5f8b893 in QObject::activate_signal (this=0x95ce1a0, clist=0x95ce220,
    o=0xbfcd0c14) at kernel/qobject.cpp:2356
#21 0xb7dbe151 in KMail::FolderJob::messageCopied (this=0x95ce1a0,
    t0=@0xbfcd0c6c) at ./folderjob.moc:169
#22 0xb7dc7441 in KMail::ImapJob::slotCopyMessageResult (this=0x95ce1a0,
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/imapjob.cpp:659
#23 0xb7dc9c17 in KMail::ImapJob::qt_invoke (this=0x95ce1a0, _id=8,
    _o=0xbfcd0d44) at ./imapjob.moc:132
#24 0xb5f8b893 in QObject::activate_signal (this=0x8f52b80, clist=0x85972e0,
    o=0xbfcd0d44) at kernel/qobject.cpp:2356
#25 0xb6bb7c11 in KIO::Job::result (this=0x8f52b80, t0=0x8f52b80)
    at ./jobclasses.moc:162
#26 0xb6bfeb2d in KIO::Job::emitResult (this=0x8f52b80)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/job.cpp:235
#27 0xb6c0a69e in KIO::SimpleJob::slotFinished (this=0x8f52b80)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/job.cpp:601
#28 0xb6bfe6c1 in KIO::SimpleJob::qt_invoke (this=0x8f52b80, _id=7,
    _o=0xbfcd0f4c) at ./jobclasses.moc:417
#29 0xb5f8b893 in QObject::activate_signal (this=0x8a2bf00, clist=0x8e39e88,
    o=0xbfcd0f4c) at kernel/qobject.cpp:2356
#30 0xb5f8c338 in QObject::activate_signal (this=0x8a2bf00, signal=6)
    at kernel/qobject.cpp:2325
#31 0xb6bafb5c in KIO::SlaveInterface::finished (this=0x8a2bf00)
    at ./slaveinterface.moc:226
#32 0xb6c180d0 in KIO::SlaveInterface::dispatch (this=0x8a2bf00, _cmd=104,
    at /build/buildd/kdelibs-3.5.7/./kio/kio/slaveinterface.cpp:243
#33 0xb6c09cda in KIO::SlaveInterface::dispatch (this=0x8a2bf00)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/slaveinterface.cpp:173
#34 0xb6bc573c in KIO::Slave::gotInput (this=0x8a2bf00)
    at /build/buildd/kdelibs-3.5.7/./kio/kio/slave.cpp:300
#35 0xb6c01dd0 in KIO::Slave::qt_invoke (this=0x8a2bf00, _id=4, _o=0xbfcd1288)
    at ./slave.moc:113
#36 0xb5f8b893 in QObject::activate_signal (this=0x8a2ff80, clist=0x8a33818,
    o=0xbfcd1288) at kernel/qobject.cpp:2356
#37 0xb5f8c1aa in QObject::activate_signal (this=0x8a2ff80, signal=2,
    param=25) at kernel/qobject.cpp:2449
#38 0xb631867f in QSocketNotifier::activated (this=0x8a2ff80, t0=25)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#39 0xb5fae46e in QSocketNotifier::event (this=0x8a2ff80, e=0xbfcd15b8)
    at kernel/qsocketnotifier.cpp:258
#40 0xb5f22af0 in QApplication::internalNotify (this=0xbfcd1934,
    receiver=0x8a2ff80, e=0xbfcd15b8) at kernel/qapplication.cpp:2635
#41 0xb5f2491f in QApplication::notify (this=0xbfcd1934, receiver=0x8a2ff80,
    e=0xbfcd15b8) at kernel/qapplication.cpp:2358
#42 0xb66e9242 in KApplication::notify (this=0xbfcd1934, receiver=0x8a2ff80,
    at /build/buildd/kdelibs-3.5.7/./kdecore/kapplication.cpp:550
#43 0xb5eb5209 in QApplication::sendEvent (receiver=0x8a2ff80,
    event=0xbfcd15b8) at ../include/qapplication.h:520
#44 0xb5f14ee9 in QEventLoop::activateSocketNotifiers (this=0x808d620)
    at kernel/qeventloop_unix.cpp:578
#45 0xb5ec9d2b in QEventLoop::processEvents (this=0x808d620, flags=4)
    at kernel/qeventloop_x11.cpp:383
#46 0xb5f3d1ce in QEventLoop::enterLoop (this=0x808d620)
    at kernel/qeventloop.cpp:198
#47 0xb5f3cfde in QEventLoop::exec (this=0x808d620)
    at kernel/qeventloop.cpp:145
#48 0xb5f24699 in QApplication::exec (this=0xbfcd1934)
    at kernel/qapplication.cpp:2758
#49 0x0804a5fe in main (argc=)
    at /build/buildd/kdepim-3.5.7enterprise20070904/./kmail/main.cpp:110
#50 0xb5728050 in __libc_start_main () from /lib/tls/i686/cmov/
#51 0x0804a381 in _start ()

Changed in kdepim:
status: Unknown → Invalid
Changed in kdepim:
status: Unknown → Confirmed
Luka Renko (lure) wrote :

This problem should be fixed with recent version in gutsy. Can you reproduce the problem with up-to-date gutsy?

Changed in kdepim:
status: New → Incomplete
Daniel Hahler (blueyed) wrote :

I've not found a way to reproduce it, but it did not happen lately.

But I'm wondering why the upstream bug report mentions no fix, while it should be fixed in Gutsy?

Luka Renko (lure) wrote :

Thanks for confirmation. The upstream bug may be still opened as the bug may not be fixed on all branches (Gutsy uses enterprise branch).

Changed in kdepim:
importance: Undecided → High
status: Incomplete → Fix Released
Changed in kdepim:
status: Confirmed → Invalid
Changed in kdepim:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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