Version: 1.9.50 (using 4.00.80 (KDE 4.0.80 >= 20080104), Gentoo) Compiler: i686-pc-linux-gnu-gcc OS: Linux (i686) release 2.6.22-gentoo-r9 Today I used Kontact in IMAP mode. When I clicked on a folder and then clicked on the inbox, Kontact crashed. Regrettably I cannot reproduce this crash. Backtrace: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb534c6d0 (LWP 6578)] [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb56f41f1 in *__GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #8 0xb56f59b8 in *__GI_abort () at abort.c:88 #9 0xb7dab265 in qt_message_output (msgType=QtFatalMsg, buf=0xbfda421c "ASSERT: \"!isEmpty()\" in file /usr/include/qt4/QtCore/qlist.h, line 242") at global/qglobal.cpp:2160 #10 0xb7dab32a in qFatal (msg=0xb7eb287c "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2392 #11 0xb7dab555 in qt_assert (assertion=0xb36fd8b6 "!isEmpty()", file=0xb36fd088 "/usr/include/qt4/QtCore/qlist.h", line=242) at global/qglobal.cpp:1917 #12 0xb34b2aea in QList<int>::first (this=0xbfda62a4) at /usr/include/qt4/QtCore/qlist.h:242 #13 0xb352b4db in KMFolderImap::addMsg (this=0x8578110, aMsg=0x881cf08, aIndex_ret=0xbfda62ec) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmfolderimap.cpp:413 #14 0xb34add7b in FolderStorage::addMessages (this=0x8578110, msgList=@0xbfda6378, index_ret=@0xbfda6338) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/folderstorage.cpp:1162 #15 0xb34afa25 in FolderStorage::moveMsg (this=0x8578110, msglist=@0xbfda6378, aIndex_ret=0xbfda6428) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/folderstorage.cpp:626 #16 0xb3493000 in KMFolder::moveMsg (this=0x855b338, q=@0xbfda644c, index_return=0xbfda6428) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmfolder.cpp:437 #17 0xb35d380b in KMMoveCommand::execute (this=0x881fa38) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmcommands.cpp:2133 #18 0xb35def7d in KMCommand::slotPostTransfer (this=0x881fa38, result=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmcommands.cpp:270 #19 0xb35df3f6 in KMCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfda69ec) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim_build/kmail/kmcommands.moc:85 #20 0xb35df89a in KMMoveCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfda69ec) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim_build/kmail/kmcommands.moc:1661 #21 0xb7e911f4 in QMetaObject::activate (sender=0x881fa38, from_signal_index=4, to_signal_index=4, argv=<value optimized out>) at kernel/qobject.cpp:3081 #22 0xb7e91d94 in QMetaObject::activate (sender=0x881fa38, m=0xb3775214, local_signal_index=0, argv=0xbfda69ec) at kernel/qobject.cpp:3140 #23 0xb35cb581 in KMCommand::messagesTransfered (this=0x881fa38, _t1=KMCommand::OK) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim_build/kmail/kmcommands.moc:99 #24 0xb35dee9b in KMCommand::transferSelectedMsgs (this=0x881fa38) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmcommands.cpp:364 #25 0xb35df266 in KMCommand::slotStart (this=0x881fa38) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kmail/kmcommands.cpp:262 #26 0xb35df3dc in KMCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfda6ff4) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim_build/kmail/kmcommands.moc:84 #27 0xb35df89a in KMMoveCommand::qt_metacall (this=0x881fa38, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfda6ff4) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim_build/kmail/kmcommands.moc:1661 #28 0xb7e911f4 in QMetaObject::activate (sender=0x869b9f0, from_signal_index=4, to_signal_index=4, argv=<value optimized out>) at kernel/qobject.cpp:3081 #29 0xb7e91d94 in QMetaObject::activate (sender=0x869b9f0, m=0xb7f2fc64, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3140 #30 0xb7e9a3c3 in QSingleShotTimer::timeout (this=0x869b9f0) at .moc/debug-shared/qtimer.moc:73 #31 0xb7e9a40c in QSingleShotTimer::timerEvent (this=0x869b9f0) at kernel/qtimer.cpp:296 #32 0xb7e8f269 in QObject::event (this=0x869b9f0, e=0x19b2) at kernel/qobject.cpp:1086 #33 0xb6d51e8a in QApplicationPrivate::notify_helper (this=0x8060068, receiver=0x869b9f0, e=0xbfda7528) at kernel/qapplication.cpp:3556 #34 0xb6d5377a in QApplication::notify (this=0xbfda77b0, receiver=0x869b9f0, e=0xbfda7528) at kernel/qapplication.cpp:3115 #35 0xb7a03fb3 in KApplication::notify (this=0xbfda77b0, receiver=0x869b9f0, event=0xbfda7528) at /var/tmp/portage/kde-base/kdelibs-9999.4/work/kdelibs-9999.4/kdeui/kernel/kapplication.cpp:314 #36 0xb7e7dd7b in QCoreApplication::notifyInternal (this=0xbfda77b0, receiver=0x869b9f0, event=0xbfda7528) at kernel/qcoreapplication.cpp:530 #37 0xb7ea6efb in QTimerInfoList::activateTimers (this=0x80607e4) at kernel/qcoreapplication.h:200 #38 0xb7ea6fd1 in QEventDispatcherUNIX::activateTimers (this=0x805f170) at kernel/qeventdispatcher_unix.cpp:828 #39 0xb7ea79ab in QEventDispatcherUNIX::processEvents (this=0x805f170, flags=@0xbfda76a8) at kernel/qeventdispatcher_unix.cpp:890 #40 0xb6ddbcce in QEventDispatcherX11::processEvents (this=0x805f170, flags=@0xbfda76d4) at kernel/qeventdispatcher_x11.cpp:145 #41 0xb7e7d191 in QEventLoop::processEvents (this=0xbfda7740, flags=@0xbfda7708) at kernel/qeventloop.cpp:140 #42 0xb7e7d29a in QEventLoop::exec (this=0xbfda7740, flags=@0xbfda7748) at kernel/qeventloop.cpp:186 #43 0xb7e7f626 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:759 #44 0xb6d51487 in QApplication::exec () at kernel/qapplication.cpp:3053 #45 0x0804b3e5 in main (argc=1, argv=0xbfda7944) at /var/tmp/portage/kde-base/kdepim-9999.4/work/kdepim-9999.4/kontact/src/main.cpp:162 #46 0xb56e0fdc in __libc_start_main (main=0x804ab50 <main>, argc=1, ubp_av=0xbfda7944, init=0x804c170 <__libc_csu_init>, fini=0x804c160 <__libc_csu_fini>, rtld_fini=0xb7f41100 <_dl_fini>, stack_end=0xbfda793c) at libc-start.c:229 #47 0x0804a781 in _start () #0 0xffffe410 in __kernel_vsyscall ()
For some reason this bug has the same backtrace as bug #156291. (Though I am pretty sure that I did *not* try to move messages around when this crash occurred...) As the backtraces are the same, and bug #156291 better fits the backtrace, I will close this bug.
Seems to be a duplicate of bug #156291