Application: kontact (4.5 beta1) KDE Platform Version: 4.4.90 (KDE 4.4.90 (KDE 4.5 RC1)) Qt Version: 4.7.0 Operating System: Linux 2.6.34.1-46.2.7.rc1.fc14.x86_64 x86_64 Distribution: "Fedora release 13 (Goddard)" -- Information about the crash: - What I was doing when the application crashed: I was trying to enable a Local Folders notification, with a POP3 mail engine attached via Akonadi, into Kontact 4.5 beta 1 summary. Then Kontact went boom. Here is the backtrace. The backtrace is about Time Tracker because I was also trying to include that into the summary. - Custom settings of the application: POP3 mail engine enabled. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f98b7002860 (LWP 21344))] Thread 2 (Thread 0x7f98abae6710 (LWP 21345)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x000000300f20ca9e in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x000000300f20cbb9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x0000003d17a07761 in start_thread (arg=0x7f98abae6710) at pthread_create.c:301 #4 0x0000003d16ee14dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f98b7002860 (LWP 21344)): [KCrash Handler] #6 0x00007f9899a97970 in timetrackerstorage::saveCalendar (this=0xcf1f080) at /usr/src/debug/kdepim-4.5-beta1/ktimetracker/timetrackerstorage.cpp:1036 #7 0x00007f9899a9d083 in timetrackerstorage::save (this=0xcf1f080, taskview=0xceb05a0) at /usr/src/debug/kdepim-4.5-beta1/ktimetracker/timetrackerstorage.cpp:383 #8 0x00007f9899aab1d7 in TaskView::save (this=0xceb05a0) at /usr/src/debug/kdepim-4.5-beta1/ktimetracker/taskview.cpp:694 #9 0x00007f9899aad10f in TaskView::qt_metacall (this=0xceb05a0, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fff5aa28b70) at /usr/src/debug/kdepim-4.5-beta1/x86_64-redhat-linux-gnu/ktimetracker/taskview.moc:171 #10 0x0000003ffff6b676 in QMetaObject::activate (sender=0xce6b140, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3305 #11 0x0000003ffff6915e in QObject::event (this=0xce6b140, e=0x7fff5aa292c0) at kernel/qobject.cpp:1208 #12 0x00000030005b15fc in QApplicationPrivate::notify_helper (this=0x16fd460, receiver=0xce6b140, e=0x7fff5aa292c0) at kernel/qapplication.cpp:4345 #13 0x00000030005b749d in QApplication::notify (this=<value optimized out>, receiver=0xce6b140, e=0x7fff5aa292c0) at kernel/qapplication.cpp:4228 #14 0x000000300481b766 in KApplication::notify (this=0x7fff5aa29620, receiver=0xce6b140, event=0x7fff5aa292c0) at /usr/src/debug/kdelibs-4.4.90/kdeui/kernel/kapplication.cpp:309 #15 0x0000003ffff57e9c in QCoreApplication::notifyInternal (this=0x7fff5aa29620, receiver=0xce6b140, event=0x7fff5aa292c0) at kernel/qcoreapplication.cpp:726 #16 0x0000003ffff8263a in sendEvent (this=0x1706e30) at kernel/qcoreapplication.h:215 #17 QTimerInfoList::activateTimers (this=0x1706e30) at kernel/qeventdispatcher_unix.cpp:602 #18 0x0000003ffff7fd34 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184 #19 0x0000003d1863bd02 in g_main_dispatch (context=0x17060e0) at gmain.c:1960 #20 IA__g_main_context_dispatch (context=0x17060e0) at gmain.c:2513 #21 0x0000003d1863fae8 in g_main_context_iterate (context=0x17060e0, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2591 #22 0x0000003d1863fc9c in IA__g_main_context_iteration (context=0x17060e0, may_block=1) at gmain.c:2654 #23 0x0000003ffff7fa23 in QEventDispatcherGlib::processEvents (this=0x16d3230, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #24 0x000000300065228e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #25 0x0000003ffff56cf2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #26 0x0000003ffff56fbc in QEventLoop::exec (this=0x7fff5aa29560, flags=...) at kernel/qeventloop.cpp:201 #27 0x0000003ffff5aedb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #28 0x0000000000403c77 in main (argc=1, argv=0x7fff5aa29c08) at /usr/src/debug/kdepim-4.5-beta1/kontact/src/main.cpp:218 Reported using DrKonqi
This crash is caused by the KTimeTracker component, which was probably running in the background. It is unrelated to KMail/POP3, KTimeTracker might happened to crash while you were in the KMail component.
*** Bug 245227 has been marked as a duplicate of this bug. ***
Created attachment 50951 [details] New crash information added by DrKonqi kontact (4.6 pre) on KDE Platform 4.5.66 (KDE 4.5.66 (KDE 4.6 >= 20100825)) using Qt 4.8.0 - What I was doing when the application crashed: Fresh installation of Kontact, klick on KTimeTracker do nothing in KTimeTracker just browse your mails or something. Wait ~1minute -> Crash -- Backtrace (Reduced): #6 0x00007f742ba6dee0 in timetrackerstorage::saveCalendar (this=0x1773790) at /home/komodev/kde_trunk/src/KDE/kdepim/ktimetracker/timetrackerstorage.cpp:1036 #7 0x00007f742ba734c3 in timetrackerstorage::save (this=0x1773790, taskview=0x148d800) at /home/komodev/kde_trunk/src/KDE/kdepim/ktimetracker/timetrackerstorage.cpp:383 #8 0x00007f742ba83ce7 in TaskView::save (this=0x148d800) at /home/komodev/kde_trunk/src/KDE/kdepim/ktimetracker/taskview.cpp:694 #9 0x00007f742ba85c0f in TaskView::qt_metacall (this=0x148d800, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff8d1e6770) at /home/komodev/kde_trunk/build/KDE/kdepim/ktimetracker/taskview.moc:171 [...] [...] #12 0x00007f744ac81265 in QTimer::timeout (this=0x17bf200) at .moc/debug-shared/moc_qtimer.cpp:134
SVN commit 1170108 by aheinecke: Check if a calendar object is set before trying to lock it. BUG: 243788 M +10 -1 timetrackerstorage.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1170108
*** Bug 249013 has been marked as a duplicate of this bug. ***