Bug 178202

Summary: ktimetracker crashes when deleting top level task
Product: [Applications] ktimetracker Reporter: Ron <linuxed7>
Component: generalAssignee: Thorsten Staerk <dev>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: screenshots of how to reproduce the crash

Description Ron 2008-12-19 18:29:54 UTC
Version:           4.0.0 (using KDE 4.1.3)
OS:                Linux
Installed from:    Ubuntu Packages

Anytime I try to delete a top level task with "Track Active Applications" enabled it causes ktimetracker to crash.  I've posted the crash report below.


Application: KTimeTracker (ktimetracker), signal SIGSEGV
(no debugging symbols found)
............................
[Thread debugging using libthread_db enabled]
[New Thread 0x7f8c82f916f0 (LWP 8844)]
(no debugging symbols found)
............................
[KCrash handler]
#5  0x00007f8c8108f561 in ?? () from /usr/lib/libQtGui.so.4
#6  0x00007f8c8108f795 in QTreeWidgetItemIterator::operator++ ()
   from /usr/lib/libQtGui.so.4
#7  0x000000000043c068 in _start ()
#0  0x00007f8c7efaa5f0 in nanosleep () from /lib/libc.so.6
Comment 1 Dario Andres 2008-12-19 18:36:47 UTC
May this bug be related to bug 173543 / bug 166107 ?
Comment 2 Ron 2008-12-19 18:38:24 UTC
Created attachment 29452 [details]
screenshots of how to reproduce the crash

Steps to reproduce:

1. Open ktimetracker and click the "Create new top level task" button.
2. Enter a task name and then check the "Edit relative", "Auto Tracking" and "Desktop 1" boxes.
3. Click on the "Clock" menu and select "Track Active Applications".
4. Open a couple of applications which should cause a few new entries to be automatically added to ktimetracker.  In the screenshot I posted I was using ksnapshot and gedit.
5. Once you have a few entries listed in ktimetracker select the entry at the very bottom which should be the top level task you created.  Then click the Delete button.  In my case this causes a crash every time.
Comment 3 Thorsten Staerk 2008-12-20 11:49:10 UTC
Dario, you are right... Ron, update and try again.

*** This bug has been marked as a duplicate of bug 166107 ***
Comment 4 Ron 2008-12-20 18:26:50 UTC
I'm currently using the latest version available in the Ubuntu repository.  I just downloaded the package below and installed it.

http://mirrors.kernel.org/ubuntu/pool/main/k/kdepim/ktimetracker_4.1.3-0ubuntu1~intrepid2_amd64.deb

After it is installed it displays the following when I type ktimetracker --version.

Qt: 4.4.3
KDE: 4.1.3 (KDE 4.1.3)
KTimeTracker: 4.0.0

I am still able to reproduce the crash in the latest version.
Comment 5 Thorsten Staerk 2008-12-21 23:01:31 UTC
I cannot reproduce again, but if I know the correct backtrace, I will find my way. The backtrace you provided is useless. Please install the -debug packages and paste the full backtrace. Also please re-open this bug then.
Comment 6 Thorsten Staerk 2008-12-22 10:20:17 UTC
Hm, I am now trying to install kubuntu 8.04 on a virtual machine to reproduce your bug. VirtualBox installed beautifully, but did not allow to access the network. Now repeating with VMWare.
Comment 7 Thorsten Staerk 2008-12-22 11:49:42 UTC
I can reproduce under kubuntu 8.10 and get a useless backtrace as well. What worries me is the packaging - there is no ktimetracker-debug package and no kdepim5 package.

Regarding the version, 4.0.0 stands for about "everything". I have started using sensible version numbers now, sorry for that.

Let's contact the packager to find out what revision it is exactly.

Anyway, this is not a KDE bug, but an Ubuntu bug.
Comment 8 Thorsten Staerk 2008-12-22 17:41:52 UTC
This was neither a KDE trunk bug not an Ubuntu bug, it was a bug in KDE 4.1 branch. It is fixed now, see 
http://websvn.kde.org/?view=rev&revision=900343
bug 173543
bug 166107

For information when this fix will hit you see:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/274170
Comment 9 Ron 2008-12-22 19:11:04 UTC
Tstaerk, thanks for taking the time to research this bug.  I look forward to installing the update when it becomes available.