'Restriction type - lock screen' does not have any effect on Raspberry PI OS

[Alex]

No 'Restriction / lockout' occurs on RaspberryPI OS.

Regardless of which 'Restriction / lockout type' is selected no restriction is applied.
No session is terminated, computer does not shutdown/suspend and no lock screen is displayed.

The UI Appears to work fine, restricted time periods seem to work in that the the RED padlock icon is displayed to the correct users at the correct time.

From the attached log you can see the text 'time is up for user "test", enforcing the LOCK' but nothing apart from the RED padlock occurs.

I have tried both version 0.4.3 and version 0.5.0 but both have the same issue. (using latest Raspberry PI OS on a Raspberry PI 4)

[Eduards Bezverhijs (mjasnik)]

I have looked at the log file, the only thing you tried, seems to be the "lock sessions" option.
There's no evidence that terminate or shutdown options have been tried.

I have a bad news, I don't have a raspberry pi to try it out with that OS. I know that there are users who use this on arm machines, which most likely is raspberry and Timekpr-nExT is working for them, but I don't know about OS, I suppose they use ubuntu.

However, Timekpr-nExT uses all standard routines to enforce limits, namely systemd (login1). Timekpr-nExT asks it to lock session, suspend or terminate or shutdown. If that OS does not do what it's asked for, then there will be a problem.

Please try other options, at least terminate, which have been standard for years. Before you try, please at least log out and back in with the user you're testing it with, or better restart to get a very clean run.
Please post a new log file from that boot with terminate option selected.

[Alex (lova24)]

My Apologies, it does appear rebooting after making changes to the 'Restriction / lockout' type is required.

I have tested the 'terminate' and the 'shutdown' modes and confirm they do work after rebooting, the lock session option does nothing.

The lock session was the first option I tried before creating the previous log file, so as I had not rebooted that explains why the log only showed the lock session option.

[Eduards Bezverhijs (mjasnik)]

Good, however reboot should not be required for those options to work.

They have to be set up before conditions are met, i.e. user still has some time available or he is not logged in / does not have any sessions.

As for lock, if it does nothing, that's sad, but I'm afraid I won't be able to help as this works fine on standard KDE / Gnome for sure.
It can be that lock request from Timekpr-nExT is simply ignored.

I'll try getting amd64 version of raspberry os to check some time soon, though.

[Eduards Bezverhijs (mjasnik)]

I have checked Raspberry Pi OS, it comes with LXDE and unfortunately it completely ignores screen locking request via dbus, so does older XFCE and Cinnamon too.

This basically means that unless newer versions of those DE will support screen locking via dbus, lock option in Timekpr-nExT will not work.

The thing is that I can't even detect whether it will work or not, because method is there and it just swallows the request.