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 139" Qt Version: 4.5.1 Operating System: Linux 2.6.27.23-0.1-default x86_64 Distribution: "openSUSE 11.1 (x86_64)" What I was doing when the application crashed: Kontact just crashed on me, for the first time in ages...apart from the system-information provided the only thing I can think of what I had been doing during that session is using the kmail and knode components. Contacts, summary, notes, and kjots were enabled but had not been in use. Akgregator was not active within Kontact but running as stand-alone. When Kontact was actively running I didn't encounter any problems. It only crashed when I shut it down. I briefly saw some clean-up and compacting dialogues but they vanished too quickly for me to see what they said (that is, I don't know if there were any problems reported in them). The crash does not seem to have caused any data-loss and I have been unable to recreate the problem. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #5 KCal::Incidence::removeRelation (this=0x21cdc90, incidence=0x21c8c00) at /usr/include/QtCore/qlist.h:664 #6 0x00007ff023c69197 in ~Incidence (this=0x21c8c00) at /usr/src/debug/kdepimlibs-4.2.90/kcal/incidence.cpp:205 #7 0x00007ff023c6ba55 in ~Todo (this=0x21c8c00) at /usr/src/debug/kdepimlibs-4.2.90/kcal/todo.cpp:103 #8 0x00007ff023c90bbe in KCal::CalendarLocal::close (this=0x20e53f0) at /usr/include/QtCore/qalgorithms.h:350 #9 0x00007ff0237683a6 in KRES::Resource::close (this=0x20eeeb0) at /usr/src/debug/kdepimlibs-4.2.90/kresources/resource.cpp:141 #10 0x00007ff023ce7689 in KCal::CalendarResources::close (this=0x20f0810) at /usr/src/debug/kdepimlibs-4.2.90/kcal/calendarresources.cpp:352 #11 0x00007ff023ce7a0d in ~CalendarResources (this=0x21cdc90) at /usr/src/debug/kdepimlibs-4.2.90/kcal/calendarresources.cpp:249 #12 0x00007ff00fdaff26 in ~StdCalendar (this=0x21cdc90) at /usr/src/debug/kdepim-4.2.90/korganizer/stdcalendar.cpp:112 #13 0x00007ff00fdb15c7 in K3StaticDeleter<KOrg::StdCalendar>::destructObject (this=0x7ff00ffb31e0) at /usr/include/k3staticdeleter.h:174 #14 0x00007ff024ef979c in K3StaticDeleterPrivate::deleteStaticDeleters () at /usr/src/debug/kdelibs-4.2.90/kde3support/kdecore/k3staticdeleter.cpp:56 #15 0x00007ff02138c6e5 in qt_call_post_routines () at kernel/qcoreapplication.cpp:163 #16 0x00007ff020089cf8 in ~QApplication (this=0x7fff2dcfa540) at kernel/qapplication.cpp:970 #17 0x0000000000404a21 in main (argc=1, argv=0x7fff2dcfac28) at /usr/src/debug/kdepim-4.2.90/kontact/src/main.cpp:67 Reported using DrKonqi
Thanks *** This bug has been marked as a duplicate of bug 174244 ***
(In reply to comment #1) > Thanks > > *** This bug has been marked as a duplicate of bug 174244 *** Are you sure it's a duplicate? The reasons why I wonder is: 1. #174244 is for KDE 4.1.x series, and not what will become 4.3.x. That is, the bug is at least one major release-number away. 2. #174244, from what it looks to me at least (considering it's the 4.1.x series), potentially involves Qt 4.3.x rather than 4.5.x. 3. #174244 states it's a regular occurence. My report is not. 4. #196115 also states that even when it doesn't crashes, it consumes 100% of one core. That also doesn't happen here. By #1-4, I would find it likely that the crashes are related but not necessarily duplicates (although they can still be that, of course, assuming the same problem persists between Qt 4.3.x through 4.5.1 and/or KDE 4.1.x and 4.3 beta2).
The backtrace is the same as bug 196115 (even line numbers). Bug 190578 looks also related. May be they are really "new" cases and not related to bug 174244 Unfortunately, some bugs can persist from older versions. Er... I will reopen this until we get more information, or until some dev can look at the report. Thanks
I still believe it is a duplicate. I fixed bug 174244 for KDE 4.3.2, please retest with that version. If your crash still occurs with KDE 4.3.2, please reopen the report. Thanks. *** This bug has been marked as a duplicate of bug 174244 ***