Bug 196163 - kontact crashs after close program
Summary: kontact crashs after close program
Status: RESOLVED DUPLICATE of bug 185544
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
Depends on:
Reported: 2009-06-12 12:19 UTC by sts
Modified: 2010-03-28 20:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Note You need to log in before you can comment on or make changes to this bug.
Description sts 2009-06-12 12:19:42 UTC
Application that crashed: kontact
Version of the application: 4.3.0 pre
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) "release 138"
Qt Version: 4.5.1
Operating System: Linux x86_64
Distribution: "openSUSE 11.1 (x86_64)"

What I was doing when the application crashed:
I start kde; he ask me start kontact or close kontact; I choose start kontact.. hmh ok now I have two kontact windows; I close the first and after I close the second one kontact crashs

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f7c6fe7bb05 in KMMainWidget::slotCheckMail (this=<value optimized out>) at /usr/src/debug/kdepim-4.2.90/kmail/kmmainwidget.cpp:1040
#6  0x00007f7c6fe9f64c in KMMainWidget::qt_metacall (this=0x11fd450, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff9037bef0)
    at /usr/src/debug/kdepim-4.2.90/build/kmail/kmmainwidget.moc:355
#7  0x00007f7c83a26c22 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#8  0x00007f7c826fe777 in QAction::triggered(bool) () from /usr/lib64/libQtGui.so.4
#9  0x00007f7c826ffbf0 in QAction::activate(QAction::ActionEvent) () from /usr/lib64/libQtGui.so.4
#10 0x00007f7c82a8fb3a in ?? () from /usr/lib64/libQtGui.so.4
#11 0x00007f7c82a8fdd5 in QAbstractButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007f7c82b61bba in QToolButton::mouseReleaseEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007f7c827557ed in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007f7c8270478d in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007f7c8270d18a in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f7c8484c04b in KApplication::notify (this=0x7fff9037e620, receiver=0x1f65eb0, event=0x7fff9037c6d0) at /usr/src/debug/kdelibs-4.2.90/kdeui/kernel/kapplication.cpp:302
#17 0x00007f7c83a1115c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007f7c8270c3d8 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&) () from /usr/lib64/libQtGui.so.4
#19 0x00007f7c82776149 in ?? () from /usr/lib64/libQtGui.so.4
#20 0x00007f7c827751b5 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4
#21 0x00007f7c8279c384 in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007f7c7d2bc0fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f7c7d2bf8cd in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f7c7d2bfa8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f7c83a3a89f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f7c8279bb0f in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f7c83a0f9f2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f7c83a0fdbd in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f7c83a120a4 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#30 0x0000000000404995 in main (argc=3, argv=0x7fff9037ed08) at /usr/src/debug/kdepim-4.2.90/kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Christophe Marin 2010-03-28 20:27:31 UTC

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