betterlockscreen --off timeout seems to not work with the last update

Hi, I have noticed that the command betterlockscreen --off 5 -l, that until commit 9a8294 worked just fine (switching off the screen after 5 seconds of inactivity) now (ee1a64) just locks, without altering screen timeouts.

I have tried to figure out which recent commit introduces this bug, with no luck. Do you have any clue?

May 19 '21 14:05 Maik93

Thanks for you feedback, even I activated all notifications for this Repo I got none for this :-/ Will check the code later, test and let you know...

(Edit: As there is more ToDo currently, I will try to look at it through the weekend)

May 22 '21 16:05 SebTM

Seems to be working again for me on multi-monitor which is the next step, could you maybe checkout the multi-monitor branch and check if this is also the case for you? :)

Jun 05 '21 12:06 SebTM

Seems to work there! However, it seems that the current master branch is many commits ahead of multi-monitor, it could still introduce a bug during its merge that will cause --off to stop working.

Jun 05 '21 15:06 Maik93

Will have an eye on it :)

Jun 05 '21 19:06 SebTM

Tested with latest multi-monitor which is going to be in beta, so I close it for now if you still experience issues please let me know :)

Jun 30 '21 19:06 SebTM

@SebTM still doesn't work with multihead setup

Mar 15 '22 11:03 ez-pzz

What do you mean with multihead? Did you use the latest next-branch as the fix is not released yet?

Mar 17 '22 04:03 SebTM

I mean multi-monitor. I've built package from the next branch, commit 1d2b1e4

Mar 17 '22 10:03 ez-pzz

Hi I realized that betterlockscreen --off 5 -l works for me but betterlockscreen -l --off 5 does not. Maybe that helps on investigating the problem.

Aug 06 '22 13:08 patriciagschossmann

Neither --off first or -l first work for me. xhost + does nothing to help this issue for me. It does not work with either one monitor or two. Updating from 4.1.0 to 4.2.0 fixed a separate issue, but --off still does not work.

Let me know what other information would be helpful.

Sep 02 '23 14:09 ArchWand

Please place set -x at the top of betterlockscreen and post the full output for more information's. Please also concrete what's "not work" means - as it seems to be a different issue than the original where it worked with "-l".

Sep 03 '23 06:09 SebTM

Not sure where exactly to put the set -x, but this issue disappeared. Probably because I rebooted? Not too sure.

Sep 03 '23 14:09 ArchWand

You edit the "betterlockscreen" script and add "set -x" after the shebang.

Even better 😄 Let's wait a few days if it reoccurs and then close it?

Sep 03 '23 16:09 SebTM

Seems to be solved, closing for now :)

Sep 25 '23 01:09 SebTM