Version: Unbekannt (using 3.5.9, Debian Package 4:3.5.9.dfsg.1-2+b1 (lenny/sid)) Compiler: Target: x86_64-linux-gnu OS: Linux (x86_64) release 2.6.24-1-amd64 symptom 1: Every time when I click on Contacts, the application crashes. When kadressbook was started before, contact will not crash. Same effect with kalender! symptom 2: Every time when I exit Kontact, the application crashes. Both effects did not appear before the last update of kontact (4:3.5.8-1) to 4:3.5.9-2 plus kmail, etc.
Created attachment 24365 [details] Backtrace when clicking kaddressbook
Created attachment 24366 [details] Backtrace when exiting contact
Backtraces look quite similar!
Please paste backtraces in the description, this makes finding duplicates in the future easier for us. [KCrash handler] #5 0x0000000000000000 in ?? () #6 0x00002ac5c7a53fe4 in KXMLGUI::ActionList::unplug () from /usr/lib/libkdeui.so.4 #7 0x00002ac5c7ae1da6 in KXMLGUI::ContainerNode::unplugClient () from /usr/lib/libkdeui.so.4 #8 0x00002ac5c7ae200f in KXMLGUI::ContainerNode::unplugActions () from /usr/lib/libkdeui.so.4 #9 0x00002ac5c7ae2060 in KXMLGUI::ContainerNode::destruct () from /usr/lib/libkdeui.so.4 #10 0x00002ac5c7ae2230 in KXMLGUI::ContainerNode::destructChildren () from /usr/lib/libkdeui.so.4 #11 0x00002ac5c7ae2055 in KXMLGUI::ContainerNode::destruct () from /usr/lib/libkdeui.so.4 #12 0x00002ac5c7aed53a in KXMLGUIFactory::removeClient () from /usr/lib/libkdeui.so.4 #13 0x00002ac5c4b04113 in KParts::MainWindow::createGUI () from /usr/lib/libkparts.so.2 #14 0x000000000041f519 in ?? () #15 0x000000000041f319 in ?? () #16 0x00002ac5c6b8536c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #17 0x0000000000421671 in ?? () #18 0x0000000000421861 in ?? () #19 0x0000000000421a79 in ?? () #20 0x00002ac5c6b853aa in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0x0000000000421ca1 in ?? () #22 0x00002ac5c6c43e29 in QListBox::mousePressEventEx () from /usr/lib/libqt-mt.so.3 #23 0x00002ac5c6bb6466 in QWidget::event () from /usr/lib/libqt-mt.so.3 #24 0x00002ac5c6b2f953 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #25 0x00002ac5c6b30886 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #26 0x00002ac5c6311ead in KApplication::notify () from /usr/lib/libkdecore.so.4 #27 0x00002ac5c6ad7a83 in QETWidget::translateMouseEvent () from /usr/lib/libqt-mt.so.3 #28 0x00002ac5c6ad6b63 in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3 #29 0x00002ac5c6ae5a59 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #30 0x00002ac5c6b44001 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #31 0x00002ac5c6b43eb2 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #32 0x0000000000418fba in ?? () #33 0x00002ac5c5df81c4 in __libc_start_main () from /lib/libc.so.6 #34 0x00000000004187a9 in ?? () #35 0x00007fffe69e3418 in ?? () #36 0x0000000000000000 in ?? ()
*** This bug has been marked as a duplicate of 102470 ***
Hello, I can't see this as a duplicate of 160920 http://bugs.kde.org/show_bug.cgi?id=102470 1. I have been working with kontact for over a year without any problem. the problem occured directly after the last update. Must have been: kontact (4:3.5.8-1) to 4:3.5.9-2 2. The application only crashes, when the included application is NOT running. When I start Kontact plus Kmail, then I can switch! By the way, I did not get any message when this bug was created nor when it was set to confirmed - why that? Regards, Martin
Created attachment 24942 [details] New backtrace, now on startup Hi folks, thank you that you show readiness to work on this bug! Now kontact even crashes on startup. What is the difference? Changes on the toolbar. Not even one change can be done without direct chrash when applying the change. Can you tell me how I can delete my changes to kontact toolbars by editing config files directly? By the way, just to try to get you back on this bug: I have been working with kmail an later on kontact since 1999! This is the software I use day by day and I really do need it working. As I use a lot of accounts, filters, folders, etc. I cannot simply delete the config file! Regards, Martin
Please read this page and post a full backtrace : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Hey Christophe, this comment is great, this really helps! I wondered about the meaningless entries in the backtrace, now I do understand. A bit earlier and I would have sent the correct information before! ;-) Martin
New backtrace, this time when starting the application: Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x2b4a8671e870 (LWP 11545)] [New Thread 0x42003950 (LWP 11558)] [New Thread 0x41802950 (LWP 11557)] [New Thread 0x41001950 (LWP 11556)] [New Thread 0x40800950 (LWP 11555)] [KCrash handler] #5 0x0000000000000021 in ?? () #6 0x00002b4a80ab6fe4 in KXMLGUI::ActionList::unplug ( this=<value optimized out>, container=0x837c00) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory_p.cpp:44 #7 0x00002b4a80b44da6 in KXMLGUI::ContainerNode::unplugClient ( this=0x85c9c0, client=0x1c65bd0) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory_p.cpp:426 #8 0x00002b4a80b4500f in KXMLGUI::ContainerNode::unplugActions ( this=0x85c9c0, state=@0x831e60) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory_p.cpp:406 #9 0x00002b4a80b45060 in KXMLGUI::ContainerNode::destruct (this=0x85c9c0, element=@0x7fff2d980840, state=@0x831e60) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory_p.cpp:313 #10 0x00002b4a80b45230 in KXMLGUI::ContainerNode::destructChildren ( this=0x8320f0, element=@0x7fff2d9809c0, state=@0x831e60) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory_p.cpp:358 #11 0x00002b4a80b45055 in KXMLGUI::ContainerNode::destruct (this=0x1c97570, element=@0x837c00, state=@0x1d1cd30) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory_p.cpp:311 #12 0x00002b4a80b5053a in KXMLGUIFactory::removeClient (this=0x831e00, client=0x9b5f40) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdeui/kxmlguifactory.cpp:364 #13 0x00002b4a7db67113 in KParts::MainWindow::createGUI (this=0x6a36c0, part=0x9b5e30) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kparts/mainwindow.cpp:108 #14 0x000000000041f519 in Kontact::MainWindow::selectPlugin (this=0x6a36c0, plugin=0x88eeb0) at /build/buildd/kdepim-3.5.9/./kontact/src/mainwindow.cpp:740 #15 0x000000000041d9f7 in Kontact::MainWindow::initObject (this=0x6a36c0) at /build/buildd/kdepim-3.5.9/./kontact/src/mainwindow.cpp:186 #16 0x000000000041dbb8 in MainWindow (this=0x6a36c0) at /build/buildd/kdepim-3.5.9/./kontact/src/mainwindow.cpp:113 #17 0x0000000000418a80 in KontactApp::newInstance (this=0x7fff2d9816e0) at /build/buildd/kdepim-3.5.9/./kontact/src/main.cpp:100 #18 0x00002b4a7f340da4 in KUniqueApplication::processDelayed ( this=0x7fff2d9816e0) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdecore/kuniqueapplication.cpp:444 #19 0x00002b4a7f35bd41 in KUniqueApplication::qt_invoke (this=0x7fff2d9816e0, _id=19, _o=0x7fff2d9810e0) at ./kuniqueapplication.moc:86 #20 0x00002b4a7fbe836c in QObject::activate_signal (this=0x6b6a60, clist=<value optimized out>, o=0x7fff2d9810e0) at kernel/qobject.cpp:2359 #21 0x00002b4a7fec07e2 in QSignal::signal (this=0x1c97570, t0=@0x6b6ab0) at .moc/release-shared-mt/moc_qsignal.cpp:100 #22 0x00002b4a7fc005fd in QSignal::activate (this=0x6b6a60) at kernel/qsignal.cpp:215 #23 0x00002b4a7fc068c8 in QSingleShotTimer::event (this=0x6b6a10) at kernel/qtimer.cpp:289 #24 0x00002b4a7fb92953 in QApplication::internalNotify ( this=<value optimized out>, receiver=0x6b6a10, e=0x7fff2d981470) at kernel/qapplication.cpp:2638 #25 0x00002b4a7fb93668 in QApplication::notify (this=0x7fff2d9816e0, receiver=0x837c00, e=0x7fff2d981470) at kernel/qapplication.cpp:2361 #26 0x00002b4a7f374ead in KApplication::notify (this=0x7fff2d9816e0, receiver=0x6b6a10, event=0x7fff2d981470) at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdecore/kapplication.cpp:550 #27 0x00002b4a7fb8922b in QEventLoop::activateTimers ( this=<value optimized out>) at kernel/qapplication.h:523 #28 0x00002b4a7fb48c4d in QEventLoop::processEvents (this=0x692e70, flags=2) at kernel/qeventloop_x11.cpp:392 #29 0x00002b4a7fba7001 in QEventLoop::enterLoop (this=0x1c97570) at kernel/qeventloop.cpp:201 #30 0x00002b4a7fba6eb2 in QEventLoop::exec (this=0x1c97570) at kernel/qeventloop.cpp:148 #31 0x0000000000418fba in main (argc=<value optimized out>, argv=<value optimized out>) at /build/buildd/kdepim-3.5.9/./kontact/src/main.cpp:163 #32 0x00002b4a7ee5b1c4 in __libc_start_main () from /lib/libc.so.6 #33 0x00000000004187a9 in _start ()
*** Bug 162953 has been marked as a duplicate of this bug. ***
do you still have this crash under kde 4.3 ?
Am Montag, 14. Dezember 2009 schrieb Nicolas Lécureuil: > https://bugs.kde.org/show_bug.cgi?id=160920 > > > Nicolas Lécureuil <nlecureuil@mandriva.com> changed: > > What |Removed |Added > --------------------------------------------------------------------------- > - CC| |nlecureuil@mandriva.com > > > > > --- Comment #12 from Nicolas Lécureuil <nlecureuil mandriva com> > 2009-12-14 16:15:24 --- do you still have this crash under kde 4.3 ? > No thanks, it seems that it is gone! :-)
thanks for your feedback, i am closing this bugreport