Bug 257524 - Kontact closed normally after pressing "x" (close), but the error reporting assistant appeared
Summary: Kontact closed normally after pressing "x" (close), but the error reporting a...
Status: RESOLVED DUPLICATE of bug 236281
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-21 16:42 UTC by Martin Wörgötter
Modified: 2011-01-25 15:53 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 Martin Wörgötter 2010-11-21 16:42:25 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-25-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I pressed "x" (close) in the upper right corner of the Kontact window. Kontact closed, but the error reporting assistant appeared, despite the fact that I didn't notice any problems. However the application probably crashed while closing it...

The crash does not seem to be reproducible.

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

Thread 2 (Thread 0xb2b96b70 (LWP 1591)):
#0  0x00a0c422 in __kernel_vsyscall ()
#1  0x07566b86 in poll () from /lib/tls/i686/cmov/libc.so.6
#2  0x018b44eb in g_poll () from /lib/libglib-2.0.so.0
#3  0x018a70ac in ?? () from /lib/libglib-2.0.so.0
#4  0x018a74b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#5  0x0112760f in QEventDispatcherGlib::processEvents (this=0xb2200468, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#6  0x010fa059 in QEventLoop::processEvents (this=0xb2b96270, flags=) at kernel/qeventloop.cpp:149
#7  0x010fa4aa in QEventLoop::exec (this=0xb2b96270, flags=...) at kernel/qeventloop.cpp:201
#8  0x00ff65a8 in QThread::exec (this=0x9680410) at thread/qthread.cpp:487
#9  0x010d9c1b in QInotifyFileSystemWatcherEngine::run (this=0x9680410) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00ff932e in QThreadPrivate::start (arg=0x9680410) at thread/qthread_unix.cpp:248
#11 0x080f396e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#12 0x07574a4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb7787990 (LWP 1488)):
[KCrash Handler]
#6  QBasicAtomicInt::operator!= (this=0x945fdf8) at /usr/include/qt4/QtCore/qbasicatomic.h:75
#7  QList<KMAccount*>::detach (this=0x945fdf8) at /usr/include/qt4/QtCore/qlist.h:122
#8  QList<KMAccount*>::begin (this=0x945fdf8) at /usr/include/qt4/QtCore/qlist.h:248
#9  KMail::AccountManager::readPasswords (this=0x945fdf8) at ../../kmail/accountmanager.cpp:435
#10 0xb3e3385b in KMail::NetworkAccount::passwd (this=0x948d2f8) at ../../kmail/networkaccount.cpp:95
#11 0xb3ea7258 in KMail::PopAccount::processNewMail (this=0x948d2f8, _interactive=true) at ../../kmail/popaccount.cpp:147
#12 0xb3dccb41 in KMail::AccountManager::processNextCheck (this=0x945fdf8, _newMail=false) at ../../kmail/accountmanager.cpp:230
#13 0xb3dcd300 in KMail::AccountManager::singleCheckMail (this=0x945fdf8, account=0x945fdf8, interactive=true) at ../../kmail/accountmanager.cpp:157
#14 0xb3dcd5f0 in KMail::AccountManager::checkMail (this=0x945fdf8, _interactive=true) at ../../kmail/accountmanager.cpp:352
#15 0xb3f8e538 in KMMainWidget::slotCheckMail (this=0x94960b8) at ../../kmail/kmmainwidget.cpp:1038
#16 0xb3fb3028 in KMMainWidget::qt_metacall (this=0x94960b8, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xbfb4aa8c) at ./kmmainwidget.moc:363
#17 0x01100c9a in QMetaObject::metacall (object=0x94960b8, cl=155581952, idx=36, argv=0xbfb4aa8c) at kernel/qmetaobject.cpp:237
#18 0x0110f3d5 in QMetaObject::activate (sender=0x95cd9b8, m=0x120e188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#19 0x01116fe7 in QSingleShotTimer::timeout (this=0x95cd9b8) at .moc/release-shared/qtimer.moc:82
#20 0x011170fc in QSingleShotTimer::timerEvent (this=0x95cd9b8) at kernel/qtimer.cpp:308
#21 0x0110c254 in QObject::event (this=0x95cd9b8, e=0x5) at kernel/qobject.cpp:1212
#22 0x01bf34dc in QApplicationPrivate::notify_helper (this=0x8ff05f0, receiver=0x95cd9b8, e=0xbfb4afc0) at kernel/qapplication.cpp:4300
#23 0x01bfa05e in QApplication::notify (this=0xbfb4b3d4, receiver=0x95cd9b8, e=0xbfb4afc0) at kernel/qapplication.cpp:3704
#24 0x00becf2a in KApplication::notify (this=0xbfb4b3d4, receiver=0x95cd9b8, event=0xbfb4afc0) at ../../kdeui/kernel/kapplication.cpp:302
#25 0x010fba3b in QCoreApplication::notifyInternal (this=0xbfb4b3d4, receiver=0x95cd9b8, event=0xbfb4afc0) at kernel/qcoreapplication.cpp:704
#26 0x0112ad66 in QCoreApplication::sendEvent (this=0x8ff63cc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#27 QTimerInfoList::activateTimers (this=0x8ff63cc) at kernel/qeventdispatcher_unix.cpp:603
#28 0x011278e4 in timerSourceDispatch (source=0x8ff6398) at kernel/qeventdispatcher_glib.cpp:184
#29 0x018a35e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#30 0x018a72d8 in ?? () from /lib/libglib-2.0.so.0
#31 0x018a74b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#32 0x011275d5 in QEventDispatcherGlib::processEvents (this=0x8fd0070, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#33 0x01cb3135 in QGuiEventDispatcherGlib::processEvents (this=0x8fd0070, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#34 0x010fa059 in QEventLoop::processEvents (this=0x9116178, flags=) at kernel/qeventloop.cpp:149
#35 0x010fa4aa in QEventLoop::exec (this=0x9116178, flags=...) at kernel/qeventloop.cpp:201
#36 0x002efb9b in Akonadi::Control::Private::exec (this=0x9131888) at ../../akonadi/control.cpp:137
#37 0x002f011e in Akonadi::Control::start () at ../../akonadi/control.cpp:206
#38 0x002f0373 in Akonadi::Control::start (parent=0x0) at ../../akonadi/control.cpp:233
#39 0x0804b451 in main (argc=3, argv=0xbfb4b5f4) at ../../../kontact/src/main.cpp:204

Reported using DrKonqi
Comment 1 Dario Andres 2010-11-22 18:52:16 UTC
[Comment from a bug triager]
This issue could be related to bug 236281 (similar trace). Regards
Comment 2 Christophe Marin 2011-01-25 15:53:48 UTC

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