Bug 197241 - kontact abort on close from KMKernel::cleanup
Summary: kontact abort on close from KMKernel::cleanup
Status: RESOLVED DUPLICATE of bug 156991
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-20 10:49 UTC by Stefan Usenbinz
Modified: 2009-07-04 15:48 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Usenbinz 2009-06-20 10:49:57 UTC
Version:            (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Kontact had been open when the system was suspended. Upon resume kmail managed to retrieve new mails from a POP3 account, but apparently could not reconnect to an IMAP account. Closing and restarting kontact/kmail usually brings back the IMAP connection. This time upon close kontact ran into an assertion on Plugin unload:

Anwendung: Kontact (kontact), Signal SIGABRT
[Current thread is 0 (LWP 3517)]

Thread 2 (Thread 0xb0387b90 (LWP 3520)):
#0  0xb8050430 in __kernel_vsyscall ()
#1  0xb59a27b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb5c76380 in QProcessManager::run (this=0x8caaef0) at io/qprocess_unix.cpp:305
#3  0xb5ba496e in QThreadPrivate::start (arg=0x8caaef0) at thread/qthread_unix.cpp:189
#4  0xb519b4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb59aa49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb48b5700 (LWP 3517)):
[KCrash Handler]
#6  0xb8050430 in __kernel_vsyscall ()
#7  0xb58f16d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb58f3098 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb5b9c595 in qt_message_output (msgType=QtFatalMsg, buf=0xa4acf18 "ASSERT: \"!transferInProgress( serNum )\" in file /build/buildd/kdepim-4.2.4/kmail/messageproperty.cpp, line 180")
    at global/qglobal.cpp:2006
#10 0xb5b9c681 in qFatal (msg=0xb5ceb318 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2201
#11 0xb5b9c775 in qt_assert (assertion=0xb13a244b "!transferInProgress( serNum )", file=0xb13a23f8 "/build/buildd/kdepim-4.2.4/kmail/messageproperty.cpp", line=180) at global/qglobal.cpp:1777
#12 0xb0ed1660 in ?? () from /usr/lib/libkmailprivate.so.4
#13 0xb0f36e7a in ?? () from /usr/lib/libkmailprivate.so.4
#14 0xb0d94944 in ?? () from /usr/lib/libkmailprivate.so.4
#15 0xb0f3ffb9 in ?? () from /usr/lib/libkmailprivate.so.4
#16 0xb0f75bc0 in ?? () from /usr/lib/libkmailprivate.so.4
#17 0xb0ebe8ed in ?? () from /usr/lib/libkmailprivate.so.4
#18 0xb0f6dc00 in ?? () from /usr/lib/libkmailprivate.so.4
#19 0xb0f7b265 in ?? () from /usr/lib/libkmailprivate.so.4
#20 0xb0e90eaf in ?? () from /usr/lib/libkmailprivate.so.4
#21 0xb0eeb3c6 in ?? () from /usr/lib/libkmailprivate.so.4
#22 0xb0ee8058 in ?? () from /usr/lib/libkmailprivate.so.4
#23 0xb0eeb3c6 in ?? () from /usr/lib/libkmailprivate.so.4
#24 0xb0ee8b22 in ?? () from /usr/lib/libkmailprivate.so.4
#25 0xb0eed969 in ?? () from /usr/lib/libkmailprivate.so.4
#26 0xb0fd28bf in KMKernel::cleanup () from /usr/lib/libkmailprivate.so.4
#27 0xb153383b in ?? () from /usr/lib/kde4/kmailpart.so
#28 0xb78ed0e9 in Kontact::Plugin::~Plugin () from /usr/lib/libkontactinterfaces.so.4
#29 0xb169476c in ?? () from /usr/lib/kde4/kontact_kmailplugin.so
#30 0xb7907fce in Kontact::MainWindow::~MainWindow () from /usr/lib/libkontactprivate.so.4
#31 0xb5ca7b25 in qDeleteInEventHandler (o=0x6) at kernel/qobject.cpp:3771
#32 0xb5ca93cb in QObject::event (this=0x8cb2550, e=0x92e25d0) at kernel/qobject.cpp:1101
#33 0xb61be440 in QWidget::event (this=0x8cb2550, event=0x92e25d0) at kernel/qwidget.cpp:7913
#34 0xb65b60d7 in QMainWindow::event (this=0x8cb2550, event=0x92e25d0) at widgets/qmainwindow.cpp:1396
#35 0xb6e6faa7 in KMainWindow::event (this=0x8cb2550, ev=0x92e25d0) at /build/buildd/kde4libs-4.2.4/kdeui/widgets/kmainwindow.cpp:1094
#36 0xb6eb489c in KXmlGuiWindow::event (this=0x8cb2550, ev=0x92e25d0) at /build/buildd/kde4libs-4.2.4/kdeui/xmlgui/kxmlguiwindow.cpp:131
#37 0xb6167e9c in QApplicationPrivate::notify_helper (this=0x8cb2d10, receiver=0x8cb2550, e=0x92e25d0) at kernel/qapplication.cpp:4084
#38 0xb6170282 in QApplication::notify (this=0xbfa6c168, receiver=0x8cb2550, e=0x92e25d0) at kernel/qapplication.cpp:4049
#39 0xb6d8be0d in KApplication::notify (this=0xbfa6c168, receiver=0x8cb2550, event=0x92e25d0) at /build/buildd/kde4libs-4.2.4/kdeui/kernel/kapplication.cpp:307
#40 0xb5c98a3b in QCoreApplication::notifyInternal (this=0xbfa6c168, receiver=0x8cb2550, event=0x92e25d0) at kernel/qcoreapplication.cpp:602
#41 0xb5c99695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8c86428) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#42 0xb5c9988d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132
#43 0xb5cc47ef in postEventSourceDispatch (s=0x8ca6110) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#44 0xb4d6bb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#45 0xb4d6f0eb in ?? () from /usr/lib/libglib-2.0.so.0
#46 0xb4d6f268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#47 0xb5cc4438 in QEventDispatcherGlib::processEvents (this=0x8c8b238, flags={i = -1079590856}) at kernel/qeventdispatcher_glib.cpp:323
#48 0xb6209365 in QGuiEventDispatcherGlib::processEvents (this=0x8c8b238, flags={i = -1079590808}) at kernel/qguieventdispatcher_glib.cpp:202
#49 0xb5c9706a in QEventLoop::processEvents (this=0xbfa6c0e0, flags={i = -1079590744}) at kernel/qeventloop.cpp:149
#50 0xb5c974aa in QEventLoop::exec (this=0xbfa6c0e0, flags={i = -1079590680}) at kernel/qeventloop.cpp:200
#51 0xb5c99959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#52 0xb6167d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#53 0x0804c072 in _start ()
Comment 1 Dario Andres 2009-06-21 00:38:21 UTC
This may be related to bug 156991 / bug 176571
Could you check them to see if you find any coincidence in your situation?
Thanks
Comment 2 Stefan Usenbinz 2009-06-21 10:47:26 UTC
Hmm, the "transferInProgress" assertion surely is the same. The steps to reproduce already vary in 156991. I was neither sending or saving mail (but tried to retrieve my mails from the server; just a different type of transfer) nor am I using DIMAP, but standard IMAP. So there just to be many ways to trigger the same bug.
I am currently using Kubuntu KDE 4.2.4 packages and Qt 4.5.0, so it is certainly nothing that would have been fixed by Qt 4.5.
Comment 3 Christophe Marin 2009-07-04 15:48:13 UTC

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