Application that crashed: kontact Version of the application: 4.3.3 KDE Version: 4.3.3 (KDE 4.3.3) "release 2" Qt Version: 4.5.3 Operating System: Linux 2.6.27.37-0.1-pae i686 Distribution: "openSUSE 11.1 (i586)" What I was doing when the application crashed: What I did: I closed Kontact. Then I tried to run it again. What I expected to happen: I assumed that Kontact would start again. What I got instead: It did not start up again. So I took a look with "ps aux" and saw it was still running. I sent kontact a SIGTERM, at which place it generated a SIGSEGV and crashed. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #12 0xffffe430 in __kernel_vsyscall () #13 0xb50e8697 in poll () from /lib/libc.so.6 #14 0xb4626f12 in ?? () from /usr/lib/libglib-2.0.so.0 #15 0xb4627241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #16 0xb5f1e071 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #17 0xb546acc5 in ?? () from /usr/lib/libQtGui.so.4 #18 0xb5ef0f1a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #19 0xb5ef1362 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #20 0xb5ef3809 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #21 0xb53ca5e7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #22 0x0804c04f in main (argc=3, argv=0xbfc241b4) at /usr/src/debug/kdepim-4.3.3/kontact/src/main.cpp:218 This bug may be a duplicate of or related to bug 215326 Reported using DrKonqi
The backtrace is not useful (as expected) as it was a forced crash/exit. If you can reproduce the original situation (Kontact not being closed properly) please open a normal bug report. Thanks
Why is this INVALID? I sent a SIGTERM, and Kontact reacts with a SIGSEGV? That is not proper behaviour in my book.
It's invalid because we can't get any useful information from this backtrace. (except that it may be related to Qt-Glib) If you encounter this issue again, attach gdb to the kontact process to see what's really happening.