time tracking intermittently way off

Asked by little

Greetings. Thanks for creating/maintaining/supporting this utility.
Linux Mint 19.3 Tricia
I'm running the version of timekpra from this ppa. Frequently, it works perfectly, only allowing logins to two of the four users only for the amount of time set on the days specified.
However, sometimes it shows a much higher time allotted (5+ hour discrepancy) or too little time.
I could use some assistance troubleshooting this as I have no idea where to start.
My only guess at this point is wtmp possibly acting problematically. This is a sample output from "last". (the computer has not actually crashed)

ph tty7 :0 Wed Feb 5 17:15 gone - no logout
syn tty7 :0 Wed Feb 5 16:06 - 17:15 (01:09)
syn tty7 :0 Wed Feb 5 15:29 - 16:05 (00:35)
ph tty7 :0 Wed Feb 5 15:23 - 15:27 (00:04)
reboot system boot 5.3.0-28-generic Wed Feb 5 15:05 still running
ph tty7 :0 Wed Feb 5 14:54 - crash (00:11)
ph tty7 :0 Tue Feb 4 15:09 - 12:53 (21:44)
ph tty7 :0 Mon Feb 3 21:28 - 22:02 (00:33)
reboot system boot 5.3.0-28-generic Mon Feb 3 21:26 still running
ph tty7 :0 Mon Feb 3 21:21 - crash (00:04)
syn tty7 :0 Sun Feb 2 21:32 - 21:21 (23:49)
ph tty7 :0 Sun Feb 2 18:32 - 21:31 (02:59)
syn tty7 :0 Sun Feb 2 17:39 - 18:32 (00:52)
ph tty7 :0 Sun Feb 2 16:39 - 17:10 (00:31)
ph tty7 :0 Sun Feb 2 11:00 - 12:28 (01:28)
syn tty7 :0 Sun Feb 2 09:58 - 11:00 (01:02)
reboot system boot 5.3.0-28-generic Sun Feb 2 09:00 still running
syn tty7 :0 Sat Feb 1 22:09 - crash (10:50)
ph pts/1 <IP> Sat Feb 1 20:46 - 20:46 (00:00)
ph tty7 :0 Sat Feb 1 19:38 - 22:09 (02:30)
reboot system boot 5.3.0-28-generic Sat Feb 1 19:35 still running

I've tried purging the timekpr-next install and reinstalling. This has (intermittently) persisted since Mint 19.2
Thanks and gday.

Question information

Language:
English Edit question
Status:
Answered
For:
Timekpr-nExT Edit question
Assignee:
Eduards Bezverhijs Edit question
Last query:
Last reply:
Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#1

Did You use intervals where starting minutes of those were not 0? Like 17:30 - 22:00 or the like?

Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#2

Please send me /var/log/timekpr.log file for investigation.

Revision history for this message
little (chewy2) said :
#3

I'm not sure I understand your first question. Here are (I think?) the relevant lines from the /var/lib/timekpr/config/*.conf

ALLOWED_HOURS_1 = 0;1;2;3;4;5;6;7;8;9;10;11;12;13;14;15;16;17;18;19;20;21;22;23 (same for 1 through 7)
LIMITS_PER_WEEKDAYS = 12600;12600;12600;12600;12600;16200;16200

I'll PM you the logs since I'm not sure how much confidential information they contain.

Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#5

Did it went better with bugfix releases so far?
Some time soon, I'll be releasing a new feature for timekpr (screen lock time will not be counted as actual time spent) and can try to add more fixes, but I don't know if this is solved.

Revision history for this message
Eduards Bezverhijs (mjasnik) said :
#6

.

Can you help with this problem?

Provide an answer of your own, or ask little for more information if necessary.

To post a message you must log in.