Version: 4.0.0 (using 4.1.3 (KDE 4.1.3), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.24-tuxonice-r4 Sometimes, when I quit ktimetracker with all tasks stopped and then open the same file later, some tasks are running. Usually, these are other tasks that ran for some time in the session before. @Thorsten, I sent you a test file by private mail.
I can confirm this, also on Gentoo 4.1.3 amd64 (if that matters). One or more tasks previously running and stopped are restarted automatically on the next start of ktimetracker. It's quite irritating if you notice that only after some time and you can't recall the original time...
I also have this problem on Ubuntu Intrepid. Not quite sure what else you need to know, but feel free to contact me for any more info about my system. This is a real pain because six tasks start up in the background everytime I reboot.
Please vote for this bug and paste an example .ics file how I can reproduce the problem.
Created attachment 30232 [details] My ics
I've already voted for this bug, and I just sent my ics file. However, ktimetracker is not currently giving me the problem I describe above. I'm not quite sure why and when it does it, so it's difficult to reproduce.
If there is one task (like "programming") that contains several events (like "from 11:30 to 12:15") that are missing their enddate (like "from 11:30") karm did not detect this, but ktimetracker does. In this case, for the first event that does not contain and enddate, the time tracking is started. If you stop it, the end date will be added, so you have one task less that does not have an enddate. If you repeat this again and again, in the end, every task will have an enddate and the problem will not happen any longer. If you quit ktimetracker while one task is running, the task will be running again after you restart it.
Wouldn't it make more sense to end all active tasks when timetracker is exited, rather than letting them autoresume. Or, at least, if tasks do autoresume on machine startup, can ktimetracker be maximized, rather than have the tasks resume in the system tray where they are not noticed.
Steve, it was my idea to handle it the way it is, but I am now convinced it should be better differently.
(In reply to comment #8) > Steve, it was my idea to handle it the way it is, but I am now convinced it > should be better differently. I think that in principle this auto-resume feature is a good idea. (Note: I don't need it for the way I'm using ktimetracker. I start ktimetracker and my tasks manually.) So I'd vote for temporarily disabling it until all bugs have been fixed.
SVN commit 916458 by tstaerk: Finally completing the work started with KDE 3.4: ktimetracker's main window now only loads the KPart. Stop timers before quitting. BUGS:176004 M +0 -2 Mainpage.dox M +45 -75 mainwindow.cpp M +3 -11 mainwindow.h M +1 -0 timetrackerwidget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=916458
(In reply to comment #10) > Stop timers before quitting. Hmm, maybe it would be better to stop timers after startup, because stopping them before a (regular) quit does not cover crashes. (I just had to kill my X server, that's what reminded me.)
it is actually still a prblem on kde 4.2.0
(In reply to comment #12) > it is actually still a prblem on kde 4.2.0 This change will hit the user with KDE 4.3. http://websvn.kde.org/branches/KDE/4.2/kdeaccessibility/ColorSchemes/CMakeLists.txt?view=log tells me the branching of KDE 4.2 was done in revision 906699 and comment 10 says me the change has been done in revision 916458.
Please do a backport to the 4.2 branch (http://websvn.kde.org/branches/KDE/4.2/) so the bug is fixed with 4.2.3. KDE 4.3 is scheduled for July 28th, this is another 3 months of living with this bad bug which makes using ktimetracker quite impossible as old tasks get restarted from time to time on startup even without your noticing...
I wouldn't consider this bug fixed as it will hit people only in 2 months (if the 4.3 release date will be met) and only those people who are immediately switching to the new major version. Some will prefer to wait for a 4.3.1 or 4.3.2 and even others will stick with 4.2.x. So, PLEASE, make KDE 4.2.x users happy and port your changes back to the 4.2 branch. There is a KDE 4.2.4 scheduled for June 3rd and your fix is what bug fix releases are for, not major versions... There's only one file and one line changed in your commit (http://websvn.kde.org/trunk/KDE/kdepim/ktimetracker/timetrackerwidget.cpp?r1=899557&r2=916458&pathrev=916458). Thank you in advance!
I'm still getting this bug in KDE 4.3.0 :-(
I'm also still getting this bug, in KDE4.3.2, on Karmic Koala. So can someone reopen it please?
Same here, the bug still occurs in KDE 4.3.3 on Gentoo, though it seems fewer times. The weird thing is that the taskbar item now is always inactive though sometimes tasks are running automatically on startup.
Who is responsible for QA on this bug? Presumably they are the only ones who can re-open it?
Everyone is responsible for QA. Sorry I did not see this for so long.
@tstaerk: I am not sure, if you want to / can handle duplicate bugs correctly in Bugzilla. (I mean, I know Bugzilla can handle them. ;-) -> This ticket is a duplicate of bug #169660, isn't it?
*** This bug has been marked as a duplicate of bug 169660 ***