Bug 202756 - kmail crash when closing filters window
Summary: kmail crash when closing filters window
Status: RESOLVED NOT A BUG
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-06 08:39 UTC by Jan Jitse Venselaar
Modified: 2009-11-16 14:53 UTC (History)
0 users

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 Jan Jitse Venselaar 2009-08-06 08:39:33 UTC
Application that crashed: kontact
Version of the application: 4.3.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-gentoo-r4 x86_64

What I was doing when the application crashed:
When I closed the filter dialog, after some browsing, kontact (or rather it's kmail part) crashed. Kontact kept running in the background, but could not be killed, had to kill -9 it, in order to start it again and read my mail.


 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[KCrash Handler]
#5  0x00000000036f5f68 in ?? ()
#6  0x00007f606972f368 in ~KUrlRequester (this=0x2bb2e00) at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kio/kfile/kurlrequester.cpp:86
#7  0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x3065cd0) at kernel/qobject.cpp:1838
#8  0x00007f606ba642c9 in ~QWidget (this=0x3138e70) at kernel/qwidget.cpp:1367
#9  0x00007f606bdc0cb1 in ~QStackedWidget (this=0x3496c00) at widgets/qstackedwidget.cpp:152
#10 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x2eefed0) at kernel/qobject.cpp:1838
#11 0x00007f606ba642c9 in ~QWidget (this=0x3091830) at kernel/qwidget.cpp:1367
#12 0x00007f6058994279 in ~KMFilterActionWidget (this=0x3091830) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmfilterdlg.cpp:1145
#13 0x00007f606ca2487e in ~KWidgetLister (this=0x300d630) at /usr/include/qt4/QtCore/qalgorithms.h:350
#14 0x00007f6058993dce in ~KMFilterActionWidgetLister (this=0x3496c00) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmfilterdlg.cpp:1206
#15 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x3002b60) at kernel/qobject.cpp:1838
#16 0x00007f606ba642c9 in ~QWidget (this=0x2f79ad0) at kernel/qwidget.cpp:1367
#17 0x00007f606bd665e1 in ~QGroupBox (this=0x3496c00) at widgets/qgroupbox.cpp:218
#18 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x314acf0) at kernel/qobject.cpp:1838
#19 0x00007f606ba63e29 in ~QWidget (this=0x3491900) at kernel/qwidget.cpp:1367
#20 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x3091910) at kernel/qobject.cpp:1838
#21 0x00007f606ba642c9 in ~QWidget (this=0x3792b80) at kernel/qwidget.cpp:1367
#22 0x00007f606bdc0cb1 in ~QStackedWidget (this=0x3496c00) at widgets/qstackedwidget.cpp:152
#23 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x2969230) at kernel/qobject.cpp:1838
#24 0x00007f606ba642c9 in ~QWidget (this=0x32e6510) at kernel/qwidget.cpp:1367
#25 0x00007f606c631661 in ~KTabWidget (this=0x32e6510) at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kdeui/widgets/ktabwidget.cpp:261
#26 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x3078f90) at kernel/qobject.cpp:1838
#27 0x00007f606ba63e29 in ~QWidget (this=0x3722500) at kernel/qwidget.cpp:1367
#28 0x00007f606b14ebac in QObjectPrivate::deleteChildren (this=0x3049510) at kernel/qobject.cpp:1838
#29 0x00007f606ba642c9 in ~QWidget (this=0x2e795c0) at kernel/qwidget.cpp:1367
#30 0x00007f60589a3e9e in ~KMFilterDlg (this=0x3496c00) at /var/tmp/portage/kde-base/kmail-4.3.0/work/kmail-4.3.0/kmail/kmfilterdlg.h:347
#31 0x00007f606b14ff5d in QObject::event (this=0x2e795c0, e=0x0) at kernel/qobject.cpp:1085
#32 0x00007f606ba6d358 in QWidget::event (this=0x2e795c0, event=0x2f669e0) at kernel/qwidget.cpp:7946
#33 0x00007f606ba1fdcc in QApplicationPrivate::notify_helper (this=0xcf1a80, receiver=0x2e795c0, e=0x2f669e0) at kernel/qapplication.cpp:4056
#34 0x00007f606ba25678 in QApplication::notify (this=0x7fffadbd84a0, receiver=0x2e795c0, e=0x2f669e0) at kernel/qapplication.cpp:4021
#35 0x00007f606c540286 in KApplication::notify (this=0x7fffadbd84a0, receiver=0x2e795c0, event=0x2f669e0)
    at /var/tmp/portage/kde-base/kdelibs-4.3.0/work/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302
#36 0x00007f606b141ccb in QCoreApplication::notifyInternal (this=0x7fffadbd84a0, receiver=0x2e795c0, event=0x2f669e0) at kernel/qcoreapplication.cpp:606
#37 0x00007f606b14238f in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xcc7690)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#38 0x00007f606b166703 in postEventSourceDispatch (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#39 0x00007f60652f965d in IA__g_main_context_dispatch (context=0xcf2a10) at gmain.c:1824
#40 0x00007f60652fce08 in g_main_context_iterate (context=0xcf2a10, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2455
#41 0x00007f60652fcf30 in IA__g_main_context_iteration (context=0xcf2a10, may_block=1) at gmain.c:2518
#42 0x00007f606b166386 in QEventDispatcherGlib::processEvents (this=0xcc72c0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#43 0x00007f606baa4d2e in QGuiEventDispatcherGlib::processEvents (this=0x3496c00, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#44 0x00007f606b1406c2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#45 0x00007f606b14085d in QEventLoop::exec (this=0x7fffadbd83e0, flags=) at kernel/qeventloop.cpp:197
#46 0x00007f606b1426e9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#47 0x0000000000403d1d in main (argc=<value optimized out>, argv=<value optimized out>) at /var/tmp/portage/kde-base/kontact-4.3.0/work/kontact-4.3.0/kontact/src/main.cpp:218

This bug may be a duplicate of or related to bug 202152

Reported using DrKonqi
Comment 1 Christophe Marin 2009-11-16 14:53:01 UTC
Unfortunately, since Kontact was killed, there's no way to find out what really happened.

The best way to get a backtrace when an application becomes unresponsive is to attach gdb as explained here: 

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB

(the '$ gdb someKDEapp pid' part in this article)