Bug 463727 - KTimeTracker opened 600+ questions about idle desktop while session was locked
Summary: KTimeTracker opened 600+ questions about idle desktop while session was locked
Status: REPORTED
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (show other bugs)
Version: 5.0.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Alexander Potashev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-02 13:48 UTC by Ingo Klöcker
Modified: 2023-02-17 14:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ingo Klöcker 2023-01-02 13:48:56 UTC 
I have enabled automatic tracking. Worked for some hours. Then I locked the screen and went for lunch. When I came back the screen locker was unresponsive and didn't show the password prompt.

After unlocking the session via the command line, I could see that KTimeTracker had opened about 620 message boxes telling me that the desktop session was idle since whatever and whether I wanted to continue. The system reacted extremely slow, so that quickly closing the 600+ message boxes wasn't an option.

Even terminating the session via the command line and logging in again didn't recover the session, so that I resorted to a reboot. I have uninstalled KTimeTracker again. I anyway need time tracking by virtual desktop and not by application window which KTimeTracker doesn't provide.
Comment 1 Jiri Palecek 2023-02-17 14:07:23 UTC 
Same thing here. The freeze is caused by kwin handling the windows too slowly, which I solved by patching kwin. It is still rogue behaviour by ktimetracker.