Application: kontact (4.4) KDE Platform Version: 4.4.00 (KDE 4.4.0) Qt Version: 4.6.2 Operating System: Linux 2.6.31.12-174.2.22.fc12.i686.PAE i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - I created a new task in a new taskset in KTimeTracker - The name of the task was "[Inti] Modelo Conceptual" - When I save the taskset as "Tareas inti", kontact crash - When I save the taskset run only KTimeTracker (not Kontact) it not crash, works fine. - When I save the taskset adding the extension .ics, it not crash, but it save nothing; the tasks dessapear and opening the archive again I get an empty taskset. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 ref (this=0x8eb698c) at /usr/include/QtCore/qatomic_i386.h:120 #7 QList (this=0x8eb698c) at /usr/include/QtCore/qlist.h:114 #8 QForeachContainer (this=0x8eb698c) at /usr/include/QtCore/qglobal.h:2227 #9 KDirWatchPrivate::Entry::propagate_dirty (this=0x8eb698c) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:416 #10 0x06637471 in KDirWatchPrivate::Entry::propagate_dirty (this=0x8e6b2d4) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:421 #11 0x066418f1 in KDirWatchPrivate::slotRescan (this=0x8b4d338) at /usr/src/debug/kdelibs-4.4.0/kio/kio/kdirwatch.cpp:1349 #12 0x066424d3 in KDirWatchPrivate::qt_metacall (this=0x8b4d338, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0xbfee0d5c) at /usr/src/debug/kdelibs-4.4.0/i686-redhat-linux-gnu/kio/kdirwatch_p.moc:81 #13 0x059105db in QMetaObject::metacall (object=0x8b4d338, cl=InvokeMetaMethod, idx=4, argv=0xbfee0d5c) at kernel/qmetaobject.cpp:237 #14 0x0591f4af in QMetaObject::activate (sender=0x8b4d380, m=0x5a1f704, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #15 0x05967298 in QTimer::timeout (this=0x8b4d380) at .moc/release-shared/moc_qtimer.cpp:134 #16 0x0592537e in QTimer::timerEvent (this=0x8b4d380, e=0xbfee1290) at kernel/qtimer.cpp:271 #17 0x0591ba94 in QObject::event (this=0x8b4d380, e=0xbfee1290) at kernel/qobject.cpp:1212 #18 0x03e44d2c in QApplicationPrivate::notify_helper (this=0x8466ee0, receiver=0x8b4d380, e=0xbfee1290) at kernel/qapplication.cpp:4300 #19 0x03e4b556 in QApplication::notify (this=0xbfee15f4, receiver=0x8b4d380, e=0xbfee1290) at kernel/qapplication.cpp:3704 #20 0x0631c58b in KApplication::notify (this=0xbfee15f4, receiver=0x8b4d380, event=0xbfee1290) at /usr/src/debug/kdelibs-4.4.0/kdeui/kernel/kapplication.cpp:302 #21 0x0590bc03 in QCoreApplication::notifyInternal (this=0xbfee15f4, receiver=0x8b4d380, event=0xbfee1290) at kernel/qcoreapplication.cpp:704 #22 0x05936afe in sendEvent (this=0x84701c4) at kernel/qcoreapplication.h:215 #23 QTimerInfoList::activateTimers (this=0x84701c4) at kernel/qeventdispatcher_unix.cpp:603 #24 0x05934188 in timerSourceDispatch (source=0x8470600) at kernel/qeventdispatcher_glib.cpp:184 #25 idleTimerSourceDispatch (source=0x8470600) at kernel/qeventdispatcher_glib.cpp:231 #26 0x00578f88 in g_main_dispatch (context=<value optimized out>) at gmain.c:1960 #27 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513 #28 0x0057c8b8 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591 #29 0x0057c9e4 in IA__g_main_context_iteration (context=0x846be90, may_block=<value optimized out>) at gmain.c:2654 #30 0x05933e46 in QEventDispatcherGlib::processEvents (this=0x8447738, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #31 0x03ef30c6 in QGuiEventDispatcherGlib::processEvents (this=0x8447738, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #32 0x0590a2da in QEventLoop::processEvents (this=0xbfee1554, flags=...) at kernel/qeventloop.cpp:149 #33 0x0590a61a in QEventLoop::exec (this=0xbfee1554, flags=...) at kernel/qeventloop.cpp:201 #34 0x0590cce7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #35 0x03e44dd8 in QApplication::exec () at kernel/qapplication.cpp:3579 #36 0x0804b32d in _start () Possible duplicates by query: bug 224229, bug 222709, bug 222547, bug 221469. Reported using DrKonqi
Is it correct that you want to say: Whenever I create a task in kontact and save it, kontact crashes ?
Yes, kontact crashes when I create a task in KTimeTracker (run into kontact) and it file has not extension .ics. (In reply to comment #1) > Is it correct that you want to say: > > Whenever I create a task in kontact and save it, kontact crashes > > ?
OK, so how do you configure kontact to use an iCal file that does not end in .ics? Please give the steps to reproduce, the earlier you give them, the earlier I can care for this bug.
I do not configure Kontact to use an iCal file that does notent in .ics; I save the file without add to name the extension .ics: - I create a new KTimeTracker file (Ctrl+N) in Kontact. - I create some tasks. - I save the file (Ctrl+S, select a name without extension .ics and save) - Kontact Crash. In the versión 4.4.1, kontact do not crash, but it do not save the file: the tasks dessapear. (In reply to comment #3) > OK, so how do you configure kontact to use an iCal file that does not end in > .ics? > Please give the steps to reproduce, the earlier you give them, the earlier I > can care for this bug.
Closing as unmaintained, since ktimetracker has been dropped in recent versions. Sorry for the noise.