Bug 228188 - korganizer crashes on exit every time
Summary: korganizer crashes on exit every time
Status: RESOLVED DUPLICATE of bug 222083
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-23 12:25 UTC by Martin Tlustos
Modified: 2010-02-23 13:01 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tlustos 2010-02-23 12:25:10 UTC
Application: korganizer (4.4)
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-20-generic x86_64
Distribution: Ubuntu 9.10

-- Information about the crash:
pretty much every time I exit korganizer it crashes. (Kontact crashes also if I exit it, but it seems that this happens because of korganizer crashing as well.)

The crash can be reproduced some of the time.

 -- Backtrace:
Application: KOrganizer (korganizer), signal: Segmentation fault
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7faa2ad567f0 (LWP 7446))]

Thread 2 (Thread 0x7faa13cb2910 (LWP 7453)):
#0  0x00007faa274363c3 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007faa20a0a37c in ?? () from /lib/libglib-2.0.so.0
#2  0x00007faa20a0a6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#3  0x00007faa27b794b6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#4  0x00007faa27b4e862 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#5  0x00007faa27b4ec3c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#6  0x00007faa27a58d29 in QThread::exec() () from /usr/lib/libQtCore.so.4
#7  0x00007faa27b2f098 in ?? () from /usr/lib/libQtCore.so.4
#8  0x00007faa27a5b745 in ?? () from /usr/lib/libQtCore.so.4
#9  0x00007faa2556ca04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#10 0x00007faa2744280d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7faa2ad567f0 (LWP 7446)):
[KCrash Handler]
#5  QBasicAtomicInt::deref (this=0x1830850, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133
#6  ~QList (this=0x1830850, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qlist.h:620
#7  ~QStringList (this=0x1830850, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qstringlist.h:67
#8  ~Private (this=0x1830850, __in_chrg=<value optimized out>) at ../../kcal/calfilter.cpp:48
#9  ~CalFilter (this=0x1830850, __in_chrg=<value optimized out>) at ../../kcal/calfilter.cpp:77
#10 0x00007faa2a04c9fe in ~Private (this=0x146dbb0, __in_chrg=<value optimized out>) at ../../kcal/calendar.cpp:79
#11 ~Calendar (this=0x146dbb0, __in_chrg=<value optimized out>) at ../../kcal/calendar.cpp:121
#12 0x00007faa291acf45 in ~StdCalendar (this=0x1830850, __in_chrg=<value optimized out>) at ../../korganizer/stdcalendar.cpp:109
#13 0x00007faa291ae787 in K3StaticDeleter<KOrg::StdCalendar>::destructObject (this=0x7faa293b0200) at /usr/include/KDE/../k3staticdeleter.h:174
#14 0x00007faa2402b76c in K3StaticDeleterPrivate::deleteStaticDeleters () at ../../kde3support/kdecore/k3staticdeleter.cpp:56
#15 0x00007faa27b50476 in qt_call_post_routines() () from /usr/lib/libQtCore.so.4
#16 0x00007faa284d3198 in QApplication::~QApplication() () from /usr/lib/libQtGui.so.4
#17 0x0000000000408574 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../korganizer/main.cpp:61

This bug may be a duplicate of or related to bug 222083.

Possible duplicates by query: bug 224277, bug 224126, bug 222083.

Reported using DrKonqi
Comment 1 Sergio Martins 2010-02-23 13:01:29 UTC
Fixed in rev 1088299.

*** This bug has been marked as a duplicate of bug 222083 ***