https://bugs.kde.org/show_bug.cgi?id=508132
--- Comment #2 from Łukasz Żarnowiecki <[email protected]> --- I also experienced this bug many times. > According to KTimeTracker, the total time, total session etc. is 18:23. On first load, this value was taken from X-KDE-ktimetracker-totalSessionTime:1103 field in your file. 1103/60 = 18.38 0.38 -> 22,8 minutes -> 18:23 For one reason or another, this was sometimes not updated. Could SIGKILL for example. > However, if I export the history and manually calculate the time, it sums to > 18:04 I think you meant 18.04. It should be 18.0555 ~ 18.06. Total time of events in your file is 65000 seconds. However each individual row and column is rounded to two decimal places. Therefore we lost some precision, hence discrepancy. Exporting, calculates each individual event separately, summing up its values, not relying on X-KDE-ktimetracker-totalSessionTime. It was more or less correct. > And, curiously, if I start the clock and immediately stop the clock, then > delete the new (0-minute) entry, the total is reduced to 17:57 (still wrong!). After removing event, time is recalculated going through each event, not relying on X-KDE-ktimetracker-totalSessionTime, but on the other hand, loosing precision. Each event was rounded to full minutes (without seconds) and then sum up. Which can introduce error of abs(N/2) minutes, where N is number of events/entries. In our case it was 7 minutes, which is more or less expected. > As calculating the total time used for a task is the core feature of this > application, I have set the severity to grave. Fortunately, exported values were mostly correct. -- You are receiving this mail because: You are watching all bug changes.
