Application that crashed: kontact Version of the application: 4.3.4 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.3 Operating System: Linux 2.6.32-2-amd64 x86_64 Distribution: Debian GNU/Linux testing (squeeze) What I was doing when the application crashed: I am just press the check mail button, and after that kontact crash in to segfault. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 0x00007f495226b295 in KMMainWidget::slotCheckMail() () from /usr/lib/libkmailprivate.so.4 #6 0x00007f495228e0ed in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 #7 0x00007f496e100df2 in QMetaObject::activate (sender=0x23aa280, from_signal_index=<value optimized out>, to_signal_index=6, argv=0x7fff0a76bc70) at kernel/qobject.cpp:3112 #8 0x00007f496d55f147 in QAction::triggered (this=0x234efe0, _t1=false) at .moc/release-shared/moc_qaction.cpp:236 #9 0x00007f496d5605c0 in QAction::activate (this=0x23aa280, event=<value optimized out>) at kernel/qaction.cpp:1167 #10 0x00007f496d8d7eda in QAbstractButtonPrivate::click (this=0x2883750) at widgets/qabstractbutton.cpp:525 #11 0x00007f496d8d8175 in QAbstractButton::mouseReleaseEvent (this=0x2881ad0, e=0x7fff0a76c5d0) at widgets/qabstractbutton.cpp:1115 #12 0x00007f496d9a6c2a in QToolButton::mouseReleaseEvent (this=0x234efe0, e=0x0) at widgets/qtoolbutton.cpp:709 #13 0x00007f496d5b537f in QWidget::event (this=0x2881ad0, event=0x7fff0a76c5d0) at kernel/qwidget.cpp:7554 #14 0x00007f496d56501d in QApplicationPrivate::notify_helper (this=0x1be2820, receiver=0x2881ad0, e=0x7fff0a76c5d0) at kernel/qapplication.cpp:4065 #15 0x00007f496d56d7ca in QApplication::notify (this=<value optimized out>, receiver=0x2881ad0, e=0x7fff0a76c5d0) at kernel/qapplication.cpp:3767 #16 0x00007f496ea91e06 in KApplication::notify (this=0x7fff0a76e390, receiver=0x2881ad0, event=0x7fff0a76c5d0) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x00007f496e0ebc9c in QCoreApplication::notifyInternal (this=0x7fff0a76e390, receiver=0x2881ad0, event=0x7fff0a76c5d0) at kernel/qcoreapplication.cpp:610 #18 0x00007f496d56ca78 in QCoreApplication::sendSpontaneousEvent (receiver=0x2881ad0, event=0x7fff0a76c5d0, alienWidget=0x2881ad0, nativeWidget=0x1cf2d90, buttonDown=<value optimized out>, lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #19 QApplicationPrivate::sendMouseEvent (receiver=0x2881ad0, event=0x7fff0a76c5d0, alienWidget=0x2881ad0, nativeWidget=0x1cf2d90, buttonDown=<value optimized out>, lastMouseReceiver=...) at kernel/qapplication.cpp:2924 #20 0x00007f496d5d5659 in QETWidget::translateMouseEvent (this=0x1cf2d90, event=<value optimized out>) at kernel/qapplication_x11.cpp:4411 #21 0x00007f496d5d440f in QApplication::x11ProcessEvent (this=0x7fff0a76e390, event=0x7fff0a76dfa0) at kernel/qapplication_x11.cpp:3552 #22 0x00007f496d5fc76c in x11EventSourceDispatch (s=0x1be6230, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #23 0x00007f4966df590e in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #24 0x00007f4966df92c8 in ?? () from /lib/libglib-2.0.so.0 #25 0x00007f4966df93f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #26 0x00007f496e11439c in QEventDispatcherGlib::processEvents (this=0x1bb98c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407 #27 0x00007f496d5fbf1f in QGuiEventDispatcherGlib::processEvents (this=0x234efe0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #28 0x00007f496e0ea562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #29 0x00007f496e0ea934 in QEventLoop::exec (this=0x7fff0a76e2d0, flags=...) at kernel/qeventloop.cpp:201 #30 0x00007f496e0ecba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #31 0x0000000000403f17 in _start () Reported using DrKonqi
Are you able to reproduce this crash with KDE > 4.4 ?
Created attachment 56805 [details] New crash information added by DrKonqi kontact (4.4.6) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0 Same problem here. Openned kmail through kontact right after login, pressed check mail shortcut, and crash -- Backtrace (Reduced): #6 0x00007fc3c28ba725 in KMMainWidget::slotCheckMail() () from /usr/lib/libkmailprivate.so.4 #7 0x00007fc3c28dc0fd in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkmailprivate.so.4 [...] #9 0x00007fc3de7cd852 in QAction::triggered(bool) () from /usr/lib/libQtGui.so.4 #10 0x00007fc3de7cef5b in QAction::activate(QAction::ActionEvent) () from /usr/lib/libQtGui.so.4 #11 0x00007fc3de7d1257 in QAction::event(QEvent*) () from /usr/lib/libQtGui.so.4
*** Bug 271789 has been marked as a duplicate of this bug. ***
Created attachment 63673 [details] New crash information added by DrKonqi kontact (4.4.10) on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1 - What I was doing when the application crashed: If I restart my opensuse 11.4 and don't close Kontact then after reboot sometimes Kontact warns me that there is anoterh instance of Kopete is already running. I allow him to start the second instance and click "Check mail", then it crashes. Probably information about the second instance is important. -- Backtrace (Reduced): #6 0x00007fb293033d25 in KMMainWidget::slotCheckMail() () from /usr/lib64/libkmailprivate.so.4 #7 0x00007fb293053e97 in KMMainWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkmailprivate.so.4 [...] #9 0x00007fb2ad880982 in QAction::triggered (this=<value optimized out>, _t1=false) at .moc/release-shared/moc_qaction.cpp:263 #10 0x00007fb2ad880b7a in QAction::activate (this=0xf9c5b0, event=<value optimized out>) at kernel/qaction.cpp:1257 #11 0x00007fb2adc3b31a in QAbstractButtonPrivate::click (this=0x10ddf90) at widgets/qabstractbutton.cpp:528
Thank you for your report. Kmail1 is currently unmaintained and the code has changed sufficiently in Kmail2 so the backtraces are not really useful anymore. Should you experience the same crash in Kmail 4.8.5 or later, please open a new report for Kmail2. Thank you for your understanding