Arch Linux

RaZorr

Member

Registered: 2021-12-02

Posts: 42

[SOLVED] xss-lock information not working properly

Following this section on dimming screen and locking it after, I issued the following commands :

xset s 180 240
xss-lock -n dim-screen.sh -- betterlockscreen -l --blur 0.0

But I got the following error :

** (xss-lock:75911): WARNING **: 17:10:34.866: Error spawning notifier: Failed to execute child process “dim-screen.sh” (No such file or directory)

Issuing full command didn't also help:

xss-lock -n /usr/share/doc/xss-lock/dim-screen.sh -- betterlockscreen -l --blur 0.0

Got error

** (xss-lock:78610): WARNING **: 17:18:29.000: Error spawning notifier: Failed to execute child process “/usr/share/doc/xss-lock/dim-screen.sh” (Permission denied)

The only set of commands that ran without errors were :

~$ xset s off
~$ xss-lock -n dim-screen.sh -- betterlockscreen -l --blur 0.0
[B] Betterlockscreen
[*] Running prelock...
[*] Locking screen...
[*] Running postlock...

But this is against that mentioned in the wiki as well doesn't allow to set the timing for blanking and locking.
Why isn't this properly working ?

Can anyone test this with betterlockscreen, xss-lock and xorg-xset ?

I have also raised an issue at xss-lock repo.

Last edited by RaZorr (2022-08-30 05:07:11)

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: [SOLVED] xss-lock information not working properly

The example script in /usr/share/doc is not executable (hence the permission denied error). And of course that directory is not in your $PATH (hence the no such file error). Usually you would copy the example to somewhere in your home directory, make it executable and modify it as needed.

You could use the example as-is with

-n 'bash /usr/share/doc/xss-lock/dim-screen.sh'

Last edited by Raynman (2022-01-02 15:57:40)

2ManyDogs

Forum Fellow

Registered: 2012-01-15

Posts: 4,648

Re: [SOLVED] xss-lock information not working properly

Moving to Newbie Corner.

RaZorr

Member

Registered: 2021-12-02

Posts: 42

Re: [SOLVED] xss-lock information not working properly

The example script in /usr/share/doc is not executable (hence the permission denied error). And of course that directory is not in your $PATH (hence the no such file error). Usually you would copy the example to somewhere in your home directory, make it executable and modify it as needed.

You could use the example as-is with

-n 'bash /usr/share/doc/xss-lock/dim-screen.sh'

Shouldn't this be added to the wiki then?

xss-lock -n dim-screen.sh -- i3lock -n

is given in xss-lock man but it doesn't work without some setting up.

Last edited by RaZorr (2022-01-03 09:14:51)

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: [SOLVED] xss-lock information not working properly

Most things don't magically work without some setting up and there's always some balancing between not repeating the same basic stuff everywhere and making things clear enough for relative newbies. You could certainly edit the wiki to expand on that example a tiny bit.

RaZorr

Member

Registered: 2021-12-02

Posts: 42

Re: [SOLVED] xss-lock information not working properly

Most things don't magically work without some setting up and there's always some balancing between not repeating the same basic stuff everywhere and making things clear enough for relative newbies. You could certainly edit the wiki to expand on that example a tiny bit.

Yes, I know this. But most things in the wiki have proper setup and instructions that work as such without any extra setting up from user side. Also, the commands you suggest are not working. I tried the bash one and making it executable. Maybe will do more testing. Hve you ever made it work?

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 77,170

Re: [SOLVED] xss-lock information not working properly

But most things in the wiki have proper setup and instructions that work as such without any extra setting up from user side.

No. Don't blindly copy and paste the examples from the wiki. As a matter of fact: NEVER copy and paste stuff into a console if you don't understand what you're doing.

Also, the commands you suggest are not working.

Which one?
The notify parameter must be a path to an executable file.
As Raynman pointed out, "dim-screen.sh" is neither and "/usr/share/doc/xss-lock/dim-screen.sh" isn't executable.

xss-lock -n 'bash /usr/share/doc/xss-lock/dim-screen.sh' -- i3lock -n

will work, but the dim-screen.sh script relies on xbacklight.
It is provided as an *example* script by xss-lock to illustrate a pattern for you to create a meaningful script that you would of course also make executable to avoid having to call an explicit interpreter.

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

RaZorr

Member

Registered: 2021-12-02

Posts: 42

Re: [SOLVED] xss-lock information not working properly

No. Don't blindly copy and paste the examples from the wiki. As a matter of fact: NEVER copy and paste stuff into a console if you don't understand what you're doing.

I do take some time to read the wiki because maybe I am not fast at learning things. But all the other configurations that I have ever setup from the wiki has been fairly straight forward for me once I take time to read it, reread it and follow the suggested links.  For those that are not, I do discuss it in the relevant Talk section so that it maybe made more beginner-friendly. I think this specific section may need one or two more lines for proper description.

the dim-screen.sh script relies on xbacklight.

This is probably my xbacklight issue then. Commands such :

echo 60 > /sys/class/backlight/intel_backlight/brightness

works, which is strange in itslef, since I am using intel.

Commands such as

xbacklight -get
xbacklight -set 10

  are not returning any output or changing the brightness.

Anyway for anyone looking for alternative, I would suggest

xautolock -time 10 -notify 5 -notifier '/usr/lib/xsecurelock/until_nonidle /usr/lib/xsecurelock/dimmer' -locker 'betterlockscreen -l --blur 0.0'

which works without any issue ( user your locker like i3lock instead of betterlockscreen as per your preference ). This is from Automatic locking section from xsecurelock github readme.

Last edited by RaZorr (2022-01-03 15:31:48)