Session lock still counting time

First of all, thanks for providing log files and configuration files already in question, much appreciated.

Please clarify:
1. did it actually lock the screen when restriction is enforced?
2. which DE (Desktop Environment) is used (Gnome, KDE, XFCE, ...)?

My findings so far are: session lock detection is not working from manager perspective for your installation, however it seems that, if user is logged in, screensaver lock reporting from user session is detected (this was a workaround I implemented to cover as much DEs as possible).

This may mean that there might be a bug when timekpr disregards lock detection from client application for some reason or other, but to verify this, I need answers to questions above.
In addition to that, please share /tmp/timekpr*log files too, these ar client application log files, they may give me additional information to reproduce the situation and if this is a bug, solve it.

Thanks.

I left out a couple of pieces of information. The user was logged in the day before (may 31st) and used to all their allowed time (2 hrs). The user locked their screen rather than logging out. The next day (june 1st), timekpr would not allow the user to login because it has continued counting time from midnight (16hrs from midnight until 4PM), which exceeded the allowed time for the day (2 hrs).

To answer your question
1. Yes it enforces the restrictions - to be specific, it locks the screen immediately after the user authenticated
2. It's gnome3

Here are the tmp logs: https://timekpr-logs.s3.us-east-1.amazonaws.com/timekprtmplogs.tar.gz?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIATKS2E2HLMW2FI6VE%2F20220602%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20220602T094617Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=a45c95a617194a567f760696d5818b6c3b55b84d0ec4a1c4b7e8a85868dcd7d7

Thanks again for the support

ok, I see that from client the timekpr screensaver handshake does happen, it's quite weird, tho, that gnome does not work with manager interface, but I'll check that.

I'll try to reproduce the issue when I get home from work.

So this is 20.04 latest updates, i.e. standard installation, right?

And please post the version of timekpr too, because there are at least 3 possible versions (stable from ppa, beta from ppa and stable older version from debian).
Universal command: dpkg -l | grep timekpr

Yes it's ubuntu 20.04 standard install, latest updates. I don't believe I've made any mods to it in any way.

$ dpkg -l | grep timekpr
ii timekpr-next 0.5.3-1ubuntu1~ppa1~ubuntu20.04.1 amd64 Keep control of computer usage

I had a closer look at the code and log files, lock detection from client seems to work... but it looks like it worked once.

The reason why it counts time is that system reports that user session is active (logged in and is in foreground) and it's not idle.
Client app should report that it entered in screensaver mode, however it does not.

So, the question is whether your user killed or terminated client application? That midnight you mentioned, did the screen turn off when session was locked?