Timekpr-nExT doesn't work with systemd-homed users

This is a feature timekpr-next does not support yet.

Which distro are you using? Does it have systemd-homed OOTB?

I'm using Manjaro with encrypted home directories. Recently I've converted the users to homed on a few laptop in our family. Then I've realized that it doesn't work with Timekpr. I will convert my youngest daughter's account back, and I will mount the encrypted home image as before. (https://wiki.archlinux.org/title/Dm-crypt/Mounting_at_login)

Thanks for this great program!

Happy new year for the whole family!

Thanks, happy new year to you and your family!

Can you please attach a timekpr logfile (for the period when homed was used) to this feature request?
If you mask usernames, please note what is masked in log file.

Interestingly my user seems to work. Timekpr doesn't display errors, when I log in, and shows the correct unlimited time. Of course, I'm in the wheel group. I've tried to add my daughter to the wheel group too, but nothing changed.
My user was an ordinary user when timekpr was installed, and later I've converted to a systemd-homed user with the same username and UID. (As described here: https://systemd.io/CONVERTING_TO_HOMED/)
In contrary the other user (my daughter's account) was created originally as a homed user, before timekpr installation.

And...
the log didn't show anything interesting, until I've changed the log level to 2.
Then I've found these lines:
NOTE: system user "myDaughterUsername" explicitly excluded
NOTE: system user "lightdm" explicitly excluded

I think the problem is that systemd-homed uses the ID range 60001-60513. (My daughter's UID is in this range too.)

Look at "Special systemd UID ranges" here: https://systemd.io/UIDS-GIDS/

P.S.: Checked Timekpr-nExT configuration, and the username of my daughter is not in the list of excluded users.

Since you're interested, here's the deal with the users.

timekpr-next tries to be standards compliant, so it filters users against login.defs configuration, which means, if user is out of standard UID_MIN / UID_MAX range, it IS explicitly excluded.

Now, systemd-homed users are out of that range, that's why they are excluded.

However, on the last day of this year, I have put on a Santa costume (:D) and made a fix to include systemd-homed users.

It will be available in BETA version soon, hour maybe, please try BETA version and report back whether it works for you.

P.S. Your findings are correct, it seems you were investigating the issue while I was working on a fix :)

I've just tried the new Beta version and it's working perfectly!

Thank you very much!

Be my guest for a drink! 🍹 (I've sent a small amount of donation!)

Thanks!