Bug 182876 - when trying to edit history, ktimetracker crashes
Summary: when trying to edit history, ktimetracker crashes
Status: RESOLVED DUPLICATE of bug 194827
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Thorsten Staerk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-02 16:21 UTC by Kuser
Modified: 2009-06-01 15:55 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 Kuser 2009-02-02 16:21:32 UTC
Version:            (using KDE 4.1.4)
OS:                Linux
Installed from:    Ubuntu Packages

I try to use ktimetracker and korganizer simultaneously. After tracking a task in ktimetracker, it appears in korganizer but with the wrong endtime (one hour is added to the tasks endtime. In order to check this in ktimetracker, I tried to go to file -> edit history as this should give me an overview of starttimes and endtimes of the tasks in ktimetracker (why can't I see them in the ktimetracker window and what's the difference between time and session time?). However, then the application crashes and gives the following message: 

A Fatal Error Occurred
The application KTimeTracker (ktimetracker) crashed and caused the signal 11 (SIGSEGV).

details:
Application: KTimeTracker (ktimetracker), signal SIGSEGV

Thread 1 (Thread 0xb52736c0 (LWP 29331)):
[KCrash Handler]
#6  0xb67a116d in KCal::Incidence::summary () from /usr/lib/libkcal.so.4
#7  0x0808ef86 in _start ()
Comment 1 Dario Andres 2009-02-03 13:33:52 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks :)
Comment 2 Kuser 2009-02-04 12:34:27 UTC
sorry, if I want to make a crash report, kde techbase tells me to install kdelibs5-dbg. I'm running kde 4.1.4 on kubuntu and the only way to install the package is to downgrade back to 4.1.3, meaning I will probably go back to a previous version of ktimetracker, which might no longer reproduce the crash. Seems a bit pointless to me. Any other way to proceed?
Comment 3 Dario Andres 2009-02-04 13:04:52 UTC
Providing packages for one version and debug info for another version is a (K)Ubuntu fault. Wait until there is dbg packages for 4.1.4
Comment 4 Kuser 2009-02-04 16:51:53 UTC
ok, my mistake; after installing kde 4.1.4 I turned off the "ubuntu intrepid proposed" repository, so I didn't get the right packages. After installing the debug packages, then crashing ktimetracker, I got the following backtrace:

Application: Kontact (kontact), signal SIGSEGV

Thread 1 (Thread 0xb4db36c0 (LWP 23261)):
[KCrash Handler]
#6  KCal::Incidence::summary (this=0x0) at /build/buildd/kdepimlibs-4.1.4/kcal/incidence.cpp:408
#7  0xb0fdae0e in EditHistoryDialog::listAllEvents (this=0xa371a40) at /build/buildd/kdepim-4.1.4/ktimetracker/edithistorydialog.cpp:121
#8  0xb0fde5c2 in EditHistoryDialog (this=0xa371a40, parent=0xa460b98) at /build/buildd/kdepim-4.1.4/ktimetracker/edithistorydialog.cpp:99
#9  0xb0fe24ba in TimetrackerWidget::editHistory (this=0xa13cf10) at /build/buildd/kdepim-4.1.4/ktimetracker/timetrackerwidget.cpp:773
#10 0xb0febe90 in TimetrackerWidget::qt_metacall (this=0xa13cf10, _c=QMetaObject::InvokeMetaMethod, _id=36, _a=0xbf88a23c)
    at /build/buildd/kdepim-4.1.4/obj-i486-linux-gnu/ktimetracker/timetrackerwidget.moc:206
#11 0xb789ca60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb789ce60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb6f725f1 in QAction::triggered () from /usr/lib/libQtGui.so.4
#14 0xb6f72f5f in QAction::activate () from /usr/lib/libQtGui.so.4
#15 0xb7350564 in ?? () from /usr/lib/libQtGui.so.4
#16 0xb7350ff2 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#17 0xb7e2bfc5 in KMenu::mouseReleaseEvent (this=0x9fb6ee8, e=0xbf88a918) at /build/buildd/kde4libs-4.1.4/kdeui/widgets/kmenu.cpp:452
#18 0xb6fd0962 in QWidget::event () from /usr/lib/libQtGui.so.4
#19 0xb73532e9 in QMenu::event () from /usr/lib/libQtGui.so.4
#20 0xb6f788ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#21 0xb6f810e1 in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0xb7d56d1d in KApplication::notify (this=0xbf88b1e8, receiver=0x9fb6ee8, event=0xbf88a918) at /build/buildd/kde4libs-4.1.4/kdeui/kernel/kapplication.cpp:311
#23 0xb7887e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#24 0xb6f8036e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#25 0xb6fea8de in ?? () from /usr/lib/libQtGui.so.4
#26 0xb6fe99e5 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#27 0xb70137aa in ?? () from /usr/lib/libQtGui.so.4
#28 0xb56a16f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#29 0xb56a4da3 in ?? () from /usr/lib/libglib-2.0.so.0
#30 0xb56a4f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#31 0xb78b2478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb7012ea5 in ?? () from /usr/lib/libQtGui.so.4
#33 0xb788652a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#34 0xb78866ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#35 0xb7888da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#36 0xb6f78767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#37 0x0804bf52 in main (argc=1, argv=0xbf88b4e4) at /build/buildd/kdepim-4.1.4/kontact/src/main.cpp:218

cheers
Comment 5 Thorsten Staerk 2009-03-28 13:29:31 UTC
Line 121 from your installation corresponds to 
    QTableWidgetItem* item = new QTableWidgetItem( (*i)->relatedTo()->summary() );
This seems like a null pointer bug...
Comment 6 Thorsten Staerk 2009-03-28 13:39:05 UTC
I have set up a kubuntu 8.04 - gives me KDE 4.0. And a kubuntu 8.10 - gives me KDE 4.2. How can I get a kubuntu with KDE 4.1.4 to reproduce?
Comment 7 Thorsten Staerk 2009-03-28 13:43:53 UTC
I get exactly this crash when I manipulate an ics file to contain a "related-to" field that points to a non-existing ical ID.
Please fix your ical file.
Comment 8 Thorsten Staerk 2009-06-01 15:55:46 UTC

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