No more count active time

Dear Sylvain,

you have your computer at home, you installed timekpr, made some configuration changes (most likely), you look at the screen and some things don’t work out as you expected. I can understand that.

But here’s me, sitting (probably) thousands of kilometers away and I don’t see your screen. In fact I know nothing about your computer or timekpr configuration, except that time does not count.

To be able to help, please reply with which Linux do you use? Which timekpr version you use? What is the configuration for the user?
You can make screenshots and post them on some free image sharing website, so I can at least know your setup a little better.

best regards
Eduards

Hello

Thank you for your reply
My OS is Linux Mint 21 on Linux kernel 5.15.0-94
TimeKpr version is 0.5.5
I attach an extract for log file.

I could see these processes :
 /usr/bin/python3 /usr/lib/python3/dist-packages/timekpr/client/timekprc.py /usr/bin/timekprc
and
/usr/bin/python3 /usr/lib/python3/dist-packages/timekpr/client/timekprd.py /usr/bin/timekprd

Thank you
Best regards,

2024-02-18 09:56:35.542722: --- initiating timekpr v. 0.5.5 ---
2024-02-18 09:56:35.542758: running on: Linux, 5.15.0-94-generic, #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024, x86_64
2024-02-18 09:56:35.922455: distribution: linuxmint, Linux Mint, 21
2024-02-18 09:56:35.922497: using python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
2024-02-18 09:56:35.922514: dbus python: 1.2.18
2024-02-18 09:56:35.922526: ---
2024-02-18 09:56:35.922540: start init dbus daemon
2024-02-18 09:56:35.923858: finish init dbus daemon
2024-02-18 09:56:35.926359: initializing configuration manager
2024-02-18 09:56:35.926838: finish configuration manager
2024-02-18 09:56:36.027904: de-initializing configuration manager
2024-02-18 09:56:36.028085: initializing configuration manager
2024-02-18 09:56:36.028295: finish configuration manager
2024-02-18 09:56:36.029082: start timekpr login1 manager
2024-02-18 09:56:36.029124: getting login1 object on DBUS
2024-02-18 09:56:36.029492: getting login1 interface on DBUS
2024-02-18 09:56:36.029522: got interface, login1 successfully set up
2024-02-18 09:56:36.029534: finish login1 manager
2024-02-18 09:56:36.029548: start init timekprUserPlayTime
2024-02-18 09:56:36.029577: finish init timekprUserPlayTime
2024-02-18 09:56:36.029602: finish init daemon data
2024-02-18 09:56:36.029619: start daemons
2024-02-18 09:56:36.029943: start up main loop thread
2024-02-18 09:56:36.030250: start up worker thread
2024-02-18 09:56:36.034329: --- start working on users ---
2024-02-18 09:56:36.034435: finish daemons, timekpr started
...
2024-02-18 09:56:57.058617: USER: user2, UID: 1001, UNAME: user2, UPATH: /org/freedesktop/login1/user/_1001
2024-02-18 09:56:57.058651: NOTE: system user "lightdm" explicitly excluded
2024-02-18 09:56:57.058685: NOTE: we have a new user "user2"
2024-02-18 09:56:57.058702: start init timekprUser
2024-02-18 09:56:57.060783: init user (user2) configuration manager
2024-02-18 09:56:57.060993: finish user configuration manager
2024-02-18 09:56:57.061015: init user (user2) control
2024-02-18 09:56:57.062383: finish init user control
2024-02-18 09:56:57.062411: start init notifications
2024-02-18 09:56:57.062472: finish init notifications
2024-02-18 09:56:57.062487: finish init timekprUser
2024-02-18 09:56:57.062557: start load user configuration
2024-02-18 09:56:57.078018: PT: found total 1 activities, valid 1
2024-02-18 09:56:57.078069: finish load user configuration
2024-02-18 09:56:57.080745: start loading user control (user2)
2024-02-18 09:56:57.139623: finish loading user control
2024-02-18 09:56:57.139717: ---=== start isUserActive for "user2" ===---
2024-02-18 09:56:57.140410: user stats, ul1st: active, ul1idlhnt: False, uscrlck: False
2024-02-18 09:56:57.140712: adding session: c2, /org/freedesktop/login1/session/c2
2024-02-18 09:56:57.143224: INFO: session locked state is available and will be used for idle state detection (if it works)
2024-02-18 09:56:57.143244: session stats, styp: x11, sVTNr: 7, sl1St: active, sl1idlst: False, sl1lckst: False
2024-02-18 09:56:57.143258: session c2 active

Ok, so far, so good.

Please get the configuration and log files, compress them and send them to me via e-mail or put them in free file sharing website, google drive or the like, so I can get them.
There is information where to find the files in the README on the project description page.

The little start of the log file is not enough and I still don’t know the configuration for the user.
Please describe which counter is not counting time too.

For those, who end up here searching for similar behaviour.

I spoke to Sylvain via e-mail and the issue was a configuration nuance which was solved by adjusting the configuration - unaccounted intervals ( ∞ ) were enabled, after disabling them, all good.