Ubuntu
kdepimlibs package

kontact crashes on exit

Bug #327228 reported by linex83
2
Affects Status Importance Assigned to Milestone
kdepimlibs
Unknown
High
kdepimlibs (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: kontact

Kontact just crashed when I tried to close it. The same thing happened when I restarted kontact and tried to close it again. However, it did not happen the third time.

Please find the kcrash report attached to this bug report.

My system is Ubuntu 8.10 32bit (latest update 8. February 2009), running GNOME.

Revision history for this message
In , seespatz (seespatz) wrote :
Download full text (7.2 KiB)

Version: 1.3 (using KDE 4.1.3)
OS: Linux
Installed from: Ubuntu Packages

When logging out of KDE, Kontact crashes with Signal SIGSEGV.

It happened for three times in arow now.

System: Kubuntu 8.10 (AMD64)
KDE Version 4.1.3 from Kubuntu packages
Kontact Version 1.3

Kontact crash output:

Anwendung: Kontact (kontact), Signal SIGSEGV
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f659558f6f0 (LWP 6572)]
(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)
(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)
(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)
(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)
(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)
(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)
(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 fo...

Read more...

Revision history for this message
In , seespatz (seespatz) wrote :

Created attachment 29359
Crash output

Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

Your backtrace is not very helpful. If you're able to reproduce this crash, could you please install the debug packages for kdepim and kdepimlibs and paste a better one ?

You will find informations on this page : http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Revision history for this message
In , seespatz (seespatz) wrote :

I am sorry: since I installed the debug packages I can't reproduce the error anymore.

Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

Fine, let's close the report then.

Revision history for this message
In , seespatz (seespatz) wrote :

Created attachment 29737
Crash output (with debug packages)

Revision history for this message
In , seespatz (seespatz) wrote :

Hi. Sorry to bother again, but the crash reapeared. It happend only once, but this time I got a crash report having the debug packages installed:

Anwendung: Kontact (kontact), Signal SIGSEGV
[Thread debugging using libthread_db enabled]
[New Thread 0x7f1ae5aef6f0 (LWP 6649)]
[New Thread 0x41088950 (LWP 6800)]
[KCrash handler]
#5 KCal::IncidenceBase::uid (this=0x1b9b210)
    at /usr/include/qt4/QtCore/qstring.h:670
#6 0x00007f1add9e9983 in removeIncidenceFromMultiHashByUID<KCal::Event*> (
    container=@0x1ab38e8, key=@0x7fffedb2d1b0, uid=@0x7fffedb2d1a0)
    at /build/buildd/kdepimlibs-4.1.3/kcal/calendarlocal.cpp:93
#7 0x00007f1add9ecdf1 in KCal::CalendarLocal::incidenceUpdated (
    this=0x1ab4260, incidence=0x7176e0)
    at /build/buildd/kdepimlibs-4.1.3/kcal/calendarlocal.cpp:394
#8 0x00007f1add9b8f23 in KCal::IncidenceBase::updated (this=0x7176e0)
    at /build/buildd/kdepimlibs-4.1.3/kcal/incidencebase.cpp:474
#9 0x00007f1add9bdf2c in KCal::Incidence::setRelatedTo (this=0x7176e0,
    incidence=0x0) at /build/buildd/kdepimlibs-4.1.3/kcal/incidence.cpp:494
#10 0x00007f1add9c06fa in ~Incidence (this=0x31d62b0)
    at /build/buildd/kdepimlibs-4.1.3/kcal/incidence.cpp:187
#11 0x00007f1add9c408b in ~Event (this=0x31d62b0)
    at /build/buildd/kdepimlibs-4.1.3/kcal/event.cpp:78
#12 0x00007f1add9e957e in KCal::CalendarLocal::close (this=0x1ab4260)
    at /usr/include/qt4/QtCore/qalgorithms.h:346
#13 0x00007f1ade187756 in KRES::Resource::close (this=0x17b3f60)
    at /build/buildd/kdepimlibs-4.1.3/kresources/resource.cpp:141
#14 0x00007f1adda3c889 in KCal::CalendarResources::close (this=0x138e830)
    at /build/buildd/kdepimlibs-4.1.3/kcal/calendarresources.cpp:315
#15 0x00007f1adda3cbfd in ~CalendarResources (this=0x7fffedb2d020)
    at /build/buildd/kdepimlibs-4.1.3/kcal/calendarresources.cpp:225
#16 0x00007f1ad12d7dd6 in ~StdCalendar (this=0x7fffedb2d020)
    at /build/buildd/kdepim-4.1.3/korganizer/stdcalendar.cpp:109
#17 0x00007f1ad12d9477 in K3StaticDeleter<KOrg::StdCalendar>::destructObject (
    this=0x7f1ad14db1e0) at /usr/include/k3staticdeleter.h:174
#18 0x00007f1ade92a559 in K3StaticDeleterPrivate::deleteStaticDeleters ()
    at /build/buildd/kde4libs-4.1.3/kde3support/kdecore/k3staticdeleter.cpp:56
#19 0x00007f1ae5627315 in qt_call_post_routines ()
   from /usr/lib/libQtCore.so.4
#20 0x00007f1ae3966388 in QApplication::~QApplication ()
   from /usr/lib/libQtGui.so.4
#21 0x0000000000404971 in main (argc=3, argv=0x7fffedb2ddd8)
    at /build/buildd/kdepim-4.1.3/kontact/src/main.cpp:67
#0 0x00007f1ae31bb621 in nanosleep () from /lib/libc.so.6

Best regards,
seespatz

Revision history for this message
In , Cgiboudeaux (cgiboudeaux) wrote :

The backtrace looks close to the one in bug 171271 (but the issue on this bug should be fixed)

Revision history for this message
In , Davide Rondini (davide-rondini) wrote :

It seems my crask is similar: I experienced it when exiting from Kontact.

OS: Fedora 10 x86_64
KDE version: 4.1.4
Kontact version: 1.3

Here's my backtrace.

Applicazione: Kontact (kontact), segnale SIGSEGV
0x0000003cd70a7f81 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7ff218833800 (LWP 3891))]

Thread 2 (Thread 0x7ff20a2fb950 (LWP 3925)):
#0 0x0000003cd70deaa2 in select () from /lib64/libc.so.6
#1 0x0000003002d22626 in ?? () from /usr/lib64/libQtCore.so.4
#2 0x0000003002c59852 in ?? () from /usr/lib64/libQtCore.so.4
#3 0x0000003cd7c073da in start_thread (arg=<value optimized out>) at pthread_create.c:297
#4 0x0000003cd70e62bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112

Thread 1 (Thread 0x7ff218833800 (LWP 3891)):
[KCrash Handler]
#5 0x0000003009e4e399 in KCal::Incidence::removeRelation () from /usr/lib64/libkcal.so.4
#6 0x0000003009e50b17 in KCal::Incidence::~Incidence () from /usr/lib64/libkcal.so.4
#7 0x0000003009e540b5 in KCal::Todo::~Todo () from /usr/lib64/libkcal.so.4
#8 0x0000003009e74b5e in KCal::CalendarLocal::close () from /usr/lib64/libkcal.so.4
#9 0x0000003006e0cc99 in KRES::Resource::close () from /usr/lib64/libkresources.so.4
#10 0x0000003009ebad39 in KCal::CalendarResources::close () from /usr/lib64/libkcal.so.4
#11 0x0000003009ebb0ad in KCal::CalendarResources::~CalendarResources () from /usr/lib64/libkcal.so.4
#12 0x000000300be038f6 in KOrg::StdCalendar::~StdCalendar () from /usr/lib64/libkorganizer_calendar.so.4
#13 0x000000300be04877 in ?? () from /usr/lib64/libkorganizer_calendar.so.4
#14 0x0000003007869a8c in ?? () from /usr/lib64/libkde3support.so.4
#15 0x0000003002d42945 in qt_call_post_routines () from /usr/lib64/libQtCore.so.4
#16 0x000000300638c058 in QApplication::~QApplication () from /usr/lib64/libQtGui.so.4
#17 0x00000000004047b1 in _start ()

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

*** Bug 183266 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

The reporter of bug 183266 is experiencing this crash on 4.2

Revision history for this message
In , seespatz (seespatz) wrote :

Bug 183266 is with KDE 4.2. Bug 177862 (this one) is with KDE 4.1.
Bug 183266 is with Kontact 1.4. Bug 177862 (this one) is with KDE 1.3.
Bug 183266 is with Signal Abort. Bug 177862 (this one) is with SIGSEGV.

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

@SeeSpatz: the backtrace is *the same* (even the functions order and line numbers):

""
#12 KCal::IncidenceBase::uid (this=0x131cf50) at /usr/include/qt4/QtCore/qstring.h:670
#13 0x00007fffd816db13 in removeIncidenceFromMultiHashByUID<KCal::Event*> (container=@0x1272528, key=@0x7fffe21f2ec0, uid=@0x7fffe21f2eb0) at /build/buildd/kdepimlibs-4.2.0/kcal/calendarlocal.cpp:93
#14 0x00007fffd8170fd1 in KCal::CalendarLocal::incidenceUpdated (this=0x1271580, incidence=0x1306bd0) at /build/buildd/kdepimlibs-4.2.0/kcal/calendarlocal.cpp:394
#15 0x00007fffd813cec3 in KCal::IncidenceBase::updated (this=0x1306bd0) at /build/buildd/kdepimlibs-4.2.0/kcal/incidencebase.cpp:474
""

The version of KDE/Kontact doesn't really matter in this case. If you posted a crash report for KDE4.1.x and it wasn't properly fixed for KDE4.2 it will be there in 4.2 (that doesn't mean that it's a *different* bug).
The same for the Kontact version (as it's related to the KDE version (KDE4.1->Kontact1.3 , KDE4.2->Kontact1.4)

Not really sure about the relation between the different signals

Thanks

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

*** Bug 183318 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Gabberkes69 (gabberkes69) wrote :

my crash disappeared today after a couple of reboots (no package upgrade). I'll report if it reappears. (see Duplicate Bug 183318)

Revision history for this message
linex83 (linex83) wrote :
Jonathan Thomas (echidnaman)
Changed in kdepim:
importance: Undecided → Low
status: New → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in kdepimlibs:
status: Unknown → New
Revision history for this message
In , Kde-org-x (kde-org-x) wrote :

Created attachment 31991
Crash file

I'm experiencing a similar crash, though the signal is SIGABRT. Happens intermittently on shutdown.

System: Kubuntu 8.10 (Linux kubuntu 2.6.27-11-generic #1 SMP Thu Jan 29 19:24:39 UTC 2009 i686 GNU/Linux)
Qt: 4.4.3
KDE: 4.2.1 (KDE 4.2.1)
Kontact Version 1.4.1

Revision history for this message
In , JJ Luza (jjluza) wrote :

Hi, I have this bug too.
It seems related to the bug 196215 (where I posted some trace)

Revision history for this message
In , JJ Luza (jjluza) wrote :

*** This bug has been confirmed by popular vote. ***

Revision history for this message
In , JJ Luza (jjluza) wrote :

Sorry I'm wrong, I think it's not related since you didn't use Akonadi here.

Bug Watch Updater (bug-watch-updater)
Changed in kdepimlibs:
status: New → Confirmed
Jonathan Thomas (echidnaman)
Changed in kdepimlibs (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

*** Bug 203537 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

Bug 177862 has an updated backtrace (4.3.2). Thanks

Revision history for this message
In , Dario Andres (andresbajotierra) wrote :

*** Bug 213179 has been marked as a duplicate of this bug. ***

Bug Watch Updater (bug-watch-updater)
Changed in kdepimlibs:
importance: Unknown → High
Revision history for this message
In , iamsergio (iamsergio) wrote :

KCal is deprecated in favor of KCalCore

Bug Watch Updater (bug-watch-updater)
Changed in kdepimlibs:
status: Confirmed → Unknown
Revision history for this message
Harald Sitter (apachelogger) wrote :

Closing in favor of usptream report. Unfortuantely the affected component is unmaintained.

Changed in kdepimlibs (Ubuntu):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.