Bug 226815 - kontact crashes when restarting after mail fetching via IMAP got stuck
Summary: kontact crashes when restarting after mail fetching via IMAP got stuck
Status: RESOLVED DUPLICATE of bug 193514
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: 2010-02-14 14:59 UTC by Mat Lechner
Modified: 2010-03-26 01:01 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.34 KB, text/plain)
2010-03-21 16:58 UTC, Tobias Stegmann
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mat Lechner 2010-02-14 14:59:40 UTC
Application: kontact (4.4)
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-19-generic i686
Distribution: Ubuntu 9.10

-- Information about the crash:
The crash occured after I restarted Kontact. Before closing, the progress bar in the lower right corner of Kontact was stuck at 80%, the detailed view of this progress bar showed that it got stuck during the check of an IMAP account. Rechecking by hitting the "fetch mail"-button had no effect.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0xb76fd760 (LWP 11227))]

Thread 2 (Thread 0xb366cb70 (LWP 20593)):
#0  QListData::isEmpty (src=0x8809950) at ../../include/QtCore/../../src/corelib/tools/qlist.h:91
#1  QList<QTimerInfo*>::isEmpty (src=0x8809950) at ../../include/QtCore/../../src/corelib/tools/qlist.h:134
#2  timerSourceCheckHelper (src=0x8809950) at kernel/qeventdispatcher_glib.cpp:146
#3  0x04347cd1 in g_main_context_check () from /lib/libglib-2.0.so.0
#4  0x0434847c in ?? () from /lib/libglib-2.0.so.0
#5  0x04348863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#6  0x010f291f in QEventDispatcherGlib::processEvents (this=0x87de308, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#7  0x010c5319 in QEventLoop::processEvents (this=0xb366c240, flags=) at kernel/qeventloop.cpp:149
#8  0x010c576a in QEventLoop::exec (this=0xb366c240, flags=...) at kernel/qeventloop.cpp:201
#9  0x00fc15a8 in QThread::exec (this=0x86b0f38) at thread/qthread.cpp:487
#10 0x010a4fbb in QInotifyFileSystemWatcherEngine::run (this=0x86b0f38) at io/qfilesystemwatcher_inotify.cpp:248
#11 0x00fc432e in QThreadPrivate::start (arg=0x86b0f38) at thread/qthread_unix.cpp:248
#12 0x0063380e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#13 0x00de98de in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb76fd760 (LWP 11227)):
[KCrash Handler]
#6  0x010128ac in bm_find (haystack=0x2c30352c, haystackLen=892088621, haystackOffset=<value optimized out>, needle=0x87d2dca, needleLen=19, cs=Qt::CaseSensitive) at tools/qstringmatcher.cpp:77
#7  qFindStringBoyerMoore (haystack=0x2c30352c, haystackLen=892088621, haystackOffset=<value optimized out>, needle=0x87d2dca, needleLen=19, cs=Qt::CaseSensitive) at tools/qstringmatcher.cpp:320
#8  0x01012c9e in QString::indexOf (this=0xbffb8cc8, str=..., from=0, cs=Qt::CaseSensitive) at tools/qstring.cpp:2377
#9  0x00f43e70 in QString::contains (this=0x80bbc90) at /usr/include/qt4/QtCore/qstring.h:899
#10 Kontact::MainWindow::activateInitialPluginModule (this=0x80bbc90) at ../../../kontact/src/mainwindow.cpp:289
#11 0x00f43f04 in Kontact::MainWindow::setInitialActivePluginModule (this=0x80bbc90, module=...) at ../../../kontact/src/mainwindow.cpp:266
#12 0x0804bcef in KontactApp::newInstance (this=0xbffb9a24) at ../../../kontact/src/main.cpp:149
#13 0x00b4cdb0 in KUniqueApplicationAdaptor::newInstance (this=0x815aba0, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:459
#14 0x00b4d512 in KUniqueApplicationAdaptor::qt_metacall (this=0x815aba0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbffb8f7c) at ./kuniqueapplication_p.moc:81
#15 0x00ec1034 in QDBusConnectionPrivate::deliverCall (this=0x80ae4c8, object=0x815aba0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:904
#16 0x00ec2395 in QDBusConnectionPrivate::activateCall (this=0x80ae4c8, object=0x815aba0, flags=337, msg=...) at qdbusintegrator.cpp:816
#17 0x00ec2dd0 in QDBusConnectionPrivate::activateObject (this=0x80ae4c8, node=..., msg=..., pathStartPos=16) at qdbusintegrator.cpp:1364
#18 0x00ec306a in QDBusActivateObjectEvent::placeMetaCall (this=0x85495d0) at qdbusintegrator.cpp:1477
#19 0x010d774e in QObject::event (this=0xbffb9a24, e=0x85495d0) at kernel/qobject.cpp:1248
#20 0x010c67cb in QCoreApplication::event (this=0xbffb9a24, e=0x85495d0) at kernel/qcoreapplication.cpp:1533
#21 0x04a98a06 in QApplication::event (this=0xbffb9a24, e=0x85495d0) at kernel/qapplication.cpp:2351
#22 0x04a9427c in QApplicationPrivate::notify_helper (this=0x80bb8c0, receiver=0xbffb9a24, e=0x85495d0) at kernel/qapplication.cpp:4298
#23 0x04a9aede in QApplication::notify (this=0xbffb9a24, receiver=0xbffb9a24, e=0x85495d0) at kernel/qapplication.cpp:3702
#24 0x00b451fa in KApplication::notify (this=0xbffb9a24, receiver=0xbffb9a24, event=0x85495d0) at ../../kdeui/kernel/kapplication.cpp:302
#25 0x010c6cfb in QCoreApplication::notifyInternal (this=0xbffb9a24, receiver=0xbffb9a24, event=0x85495d0) at kernel/qcoreapplication.cpp:704
#26 0x010c9733 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8096b68) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#27 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8096b68) at kernel/qcoreapplication.cpp:1345
#28 0x010c989d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238
#29 0x010f2def in QCoreApplication::sendPostedEvents (s=0x80ba510) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#30 postEventSourceDispatch (s=0x80ba510) at kernel/qeventdispatcher_glib.cpp:276
#31 0x04344e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0x04348730 in ?? () from /lib/libglib-2.0.so.0
#33 0x04348863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0x010f28e5 in QEventDispatcherGlib::processEvents (this=0x8096700, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#35 0x04b53485 in QGuiEventDispatcherGlib::processEvents (this=0x8096700, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0x010c5319 in QEventLoop::processEvents (this=0xbffb9984, flags=) at kernel/qeventloop.cpp:149
#37 0x010c576a in QEventLoop::exec (this=0xbffb9984, flags=...) at kernel/qeventloop.cpp:201
#38 0x010c995f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#39 0x04a94317 in QApplication::exec () at kernel/qapplication.cpp:3577
#40 0x0804b4c2 in main (argc=3, argv=0xbffb9c44) at ../../../kontact/src/main.cpp:224

Reported using DrKonqi
Comment 1 Mat Lechner 2010-02-15 14:20:14 UTC
This bug seems to be related to bug 223705, because IMAP is stuck after resuming from suspend.
Comment 2 Dario Andres 2010-03-19 14:09:36 UTC
The backtrace looks related to bug 193514. Regards
Comment 3 Tobias Stegmann 2010-03-21 16:58:55 UTC
Created attachment 41805 [details]
New crash information added by DrKonqi

Same issue over here. The IMAP request for new mails was hanging at 0%.
Comment 4 Christophe Marin 2010-03-26 01:01:52 UTC

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