Bug 347365

Summary:	(v 4.14.1) ktimetracker: closing application window does NOT kill the ktimetracker-task
Product:	[Applications] ktimetracker	Reporter:	mossl
Component:	general	Assignee:	Zoltan Gyarmati <mr.zoltan.gyarmati>
Status:	REOPENED ---
Severity:	critical	CC:	aspotashev
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Debian stable
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description mossl 2015-05-07 07:32:14 UTC

Awefull bug unless you know that you've to kill the task manually!
The remainig tasks all keep updating the ktimetracker.ics file, so this file gets messed up really bad.
eg:
You will lose changes in the ics-file made by a session started at 08:00 and closed at 08:15 when a task (started 07:30 and not fully closed at 07:45) is active after 08:15!

Reproducible: Always

Steps to Reproduce:
1. start ktimetracker
2. close ktimetracker from menue
3. open a task-manager and search for the remaining task(s) called "ktimetracker"

Actual Results:  
task(s) called "ktimetracker" remained

Expected Results:  
there should be no task(s) called "ktimetracker" any more

Comment 1 mossl 2015-05-07 09:45:38 UTC

bug 321026 https://bugs.kde.org/show_bug.cgi?id=321026 and 
bug 284936 https://bugs.kde.org/show_bug.cgi?id=284936
might be caused by this bug!

In Comment #2 of bug 312949 ( https://bugs.kde.org/show_bug.cgi?id=312949#c2 ) the "shading of windows" is suspected to be the reason for a "similar" bug. Unfortunately there are more then one effects in KDE dealing with "shading".

... I re-tested and found:
Click on the SAVING-Button

Comment 2 mossl 2015-05-07 10:25:39 UTC

Sry - the comment was not ready for saving, AND "Steps to Reproduce" from ABOVE is INCORRECT!

Steps to Reproduce:
1. start ktimetracker
2. close ktimetracker-Window (by clicking the "X"-button in the window)
3. open a task-manager and search for the remaining task(s) called "ktimetracker"

The bug does NOT happen when ktimetracker is closed by "Strg+Q" or by closing with the menu-entry!!! Nevertheless it could be an issue for the other bugs mentioned above (321026, 284936 and 3142949). I think KDE-Effects are no reason for this bug, as deactivating all effects (Alt+Upper+F12) does not show any effect ( :lol: this is not an intended wordplay).

Comment 3 Andrew Crouthamel 2018-09-04 18:55:02 UTC

Hello! Sorry to be the bearer of bad news, but this project has been unmaintained for many years so I will be closing this bug.