[Pkg-kde-extras] Bug#1022149: ktimetracker total data loss

[contact smxi]

Package: ktimetracker
Version: 4:5.0.1-3
Severity: grave

KDE Frameworks: Version 5.98.0
Qt: Version 5.15.4 (built against 5.15.4)

Running on: Xfce v: 4.16.1

ktimetracker loses all session history/times data on shutdown/quit.

Worse, when I tried to manually reload the icv file using the 'open' option from:
~/.local//share/ktimetracker/ktimetracker.ics

it failed to load the data, and promptly wiped the .ics data (about 45 KiB worth) to the default 
state, leaving no backup or temp file version at least.

This is the second major data loss I've encountered, the first was losing my entire history after 
upgrading to current Debian Testing a few days ago, and this one happened after I rebuilt my session 
times from memory, saved using the 'save' option in hopes that would help create a good backup.

Note that ktimetracker does not offer any useful option like 'save history as', only 'save', which 
saves it to the default location, which as far as I know, can't be changed.

This makes ktimetracker worse than unusable, since it doesn't lose the data until you try to restart 
ktimetracker, and it does not load the saved data on restart, even though it appears to still be 
present, nor does it appear to use the saved .ics file data when it's opened.

Your only chance of not losing data as far as I can tell is to not close ktimetracker, 
suspend/resume system, and also routinely make backup copies of 
~/.local//share/ktimetracker/ktimetracker.ics to a different location and file name manually.

This is the same bug as has been reported to kde already, 2022-10-19

https://bugs.kde.org/show_bug.cgi?id=460701

There are no warnings, errors, or anything else, all that happens is that you close ktimetracker, 
while your session data and times and history are there, and you open it, and they are gone, and 
attempts to open the saved file results in nothing changing.

Until this bug is fixed, warning also to users to disable the autosave ever x minutes feature, 
though I believe that may save on close always.

This makes ktimetracker totally unusable for its intended purpose, being a session time tracker, so 
warning to users about this until the issue is resolved or the cause located.