Version: (using KDE 4.1.3) OS: Linux Installed from: SuSE RPMs Kontact crash (SIGSEV) 11 when I work in my contacts (edit, move, rename, etc) more specifically I was assigning contacts to categories. here's the sigsev crash report: Application: Kontact (kontact), signal SIGSEGV [?1034h(no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb4e686d0 (LWP 28300)] [KCrash handler] #6 0xb77059e8 in Q3ListViewItem::depth () from /usr/lib/libQt3Support.so.4 #7 0xb77122c3 in Q3ListView::contentsMousePressEventEx () from /usr/lib/libQt3Support.so.4 #8 0xb7712894 in Q3ListView::contentsMousePressEvent () from /usr/lib/libQt3Support.so.4 #9 0xb612632d in K3ListView::contentsMousePressEvent () from /usr/lib/libkde3support.so.4 #10 0xb0d89165 in ?? () from /usr/lib/kde4/kaddrbk_tableview.so #11 0xb776fe31 in Q3ScrollView::viewportMousePressEvent () from /usr/lib/libQt3Support.so.4 #12 0xb7771a10 in Q3ScrollView::eventFilter () from /usr/lib/libQt3Support.so.4 #13 0xb770d276 in Q3ListView::eventFilter () from /usr/lib/libQt3Support.so.4 #14 0xb6b29c4a in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib/libQtCore.so.4 #15 0xb585880a in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #16 0xb5861081 in QApplication::notify () from /usr/lib/libQtGui.so.4 #17 0xb71c931d in KApplication::notify () from /usr/lib/libkdeui.so.5 #18 0xb6b2aa71 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #19 0xb586030e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4 #20 0xb58ca736 in ?? () from /usr/lib/libQtGui.so.4 #21 0xb58c9add in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #22 0xb58f21bc in ?? () from /usr/lib/libQtGui.so.4 #23 0xb52392d9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb523c85b in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb523c9d8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb6b55208 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #27 0xb58f1885 in ?? () from /usr/lib/libQtGui.so.4 #28 0xb6b2914a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #29 0xb6b2930a in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #30 0xb6b2b9a5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #31 0xb58586a7 in QApplication::exec () from /usr/lib/libQtGui.so.4 #32 0x0804c17f in _start () #0 0xffffe430 in __kernel_vsyscall () I would appreciate to know what's happening! :) please tell me if I can help. thanks!
Did you tried to use kaddressbook as a standalone application? Does it crash too? If you can reproduce the crash, you could install the debug enabled packages and provide a new backtrace. Read this page for the instructions: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports Thanks!
FiNeX, thanks for you support. I tried to recreate the crash with the standalone application and it does it too. I however noticed that if I remove the GUI-integrated contact editor, the application do not crash anymore. I edited at least 50 contacts and no crash at all. I assume the bug if related to the contact editor. I f I double click the contact and open then open the contact editor window, it does not crash either. I will install the debug enabled packs and provide a new backtrace probably tomorrow. Thanks!! Louis
Many thanks! Your feedback is very useful!!!
This may be related/duplicate of bug 170906 (bug 158179)
*** This bug has been marked as a duplicate of bug 170906 ***
Bad dup. *** This bug has been marked as a duplicate of bug 158179 ***
The development of the old KAddressBook will be discontinued for KDE 4.4. Since the new application has the same name, but a completly new code base we close all bug reports against the old version and ask the submitters to resend there reports against the new product.