Timekpr-nExT

Lock screen does not work in case of full screen videos

Asked by Luca Trombin

Hello,

I have a problem: my kids love to watch videos or movies and when there is a full-screen video (i.e. Youtube on Firefox), the screen is not getting locked even if the time is elapsed.

Of course my kids understood the trick on the fly even before me :(

How can I resolve this issue?

Is it possible in future to add a button to inhibit the "screen lock inhibit"?

Thanks,

Luca

Question information

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

Timekpr asks to lock the screen to systemd login manager.
In this case, it looks like the request is ignored, wchich is not exactly a good thing. I would need to check whether there is a force lock request or something similar.
You can always configure to end the session, though :)

Can you provide a download link to distro you’re using? I could check whether I can do anything about this.

Revision history for this message
Luca Trombin (lucat78) said : 		#2

I have Linux Mint 21.2 "Victoria": https://www.linuxmint.com/edition.php?id=305

to force Cinnamon screen lock I'm using this command: sudo -u {0} cinnamon-screensaver-command --lock

thank you

Revision history for this message
Eduards Bezverhijs (mjasnik) said (last edit ): 		#3

Please recheck this issue after you install the latest version as per https://answers.launchpad.net/timekpr-next/+question/708434 .
There is a high probability that it might solve this issue for you.

Revision history for this message
Luca Trombin (lucat78) said : 		#4

Hi Eduards,

unfortunately the latest version does not solve this issue in Linux Mint.

I feel that locking session is NOT supported by Cinnamon Desktop Env. since I also run the command "loginctl lock-session <active session ID>" and still nothing is happening!

Even loginctl man says "this command works if it's supported", so I believe I will have no other way that I need to terminate the user session completely!

Anyway when I was playing with timekpr, I just noticed that in case the user is locked and sessions does not end, basically timekpr sets new time only to new sessions, not to any locked ones (in case I add more time to the user) and I also noticed that in this case the cached object in the code is not refreshed, hence if something fails the session is unlocked and the code does not look into it again since it thinks that that session is already finished.

In fact when sessions are locked, I can find multiple sessions for the same user, but only 1 active.

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

Well, this would need a more precise explanation…
For example, there are 3 ways how to add time to user, which one you used?

Basically I would need a simple step-by-step reproducible test case from the start to finish in order to check this on my side.

Can you help with this problem?

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

To post a message you must log in.