View previous topic :: View next topic |
Author |
Message |
vrghost n00b
Joined: 03 Oct 2003 Posts: 60 Location: London
|
Posted: Thu Nov 21, 2024 7:33 pm Post subject: [SOLVED] xautolock seems to do nothing |
|
|
Trying to set up xautolock to lock the screen, and before even putting it in any startup script, I seem to struggle to get it to work at all.
emergege xautolock:
Code: |
* x11-misc/xautolock
Latest version available: 2.2_p7
Latest version installed: 2.2_p7
Size of files: 43 KiB
Homepage: http://www.ibiblio.org/pub/Linux/X11/screensavers/
Description: An automatic X screen-locker/screen-saver
License: GPL-2
|
The problem is, I don't seem to be able to get it to lock my screen, but I don't get any error messages or any updated logs (that I can see)
In an X session with qtile
I started it in a terminal with
Code: |
xautolock -time 2 -locker "betterscreenlocker -l"
|
Waited for five minutes, still not locked
Started a second terminal, and ran
Code: |
xautolock -locknow -locker "betterscreenlocker -l"
|
But nothing seems to happen.
I use xorg-server 21.1.14
Any ideas?
Betterscreenlocker works by the way, have a shortcut for that using the same command, I am happy to try anything at this stage
Last edited by vrghost on Sat Nov 23, 2024 5:30 pm; edited 1 time in total |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3904
|
Posted: Thu Nov 21, 2024 8:39 pm Post subject: |
|
|
what package provides ?
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
Weezer n00b
Joined: 19 Apr 2024 Posts: 24
|
Posted: Fri Nov 22, 2024 10:53 am Post subject: Re: xautolock seems to do nothing |
|
|
vrghost wrote: |
I started it in a terminal with
Code: |
xautolock -time 2 -locker "betterscreenlocker -l"
|
Waited for five minutes, still not locked
Started a second terminal, and ran
Code: |
xautolock -locknow -locker "betterscreenlocker -l"
|
|
After the first command has been run, the second command should simply be:
xautolock -locknow
Due to the fact that xautolock is already running an instance and you are invoking it "now".
You could also add an "&" after your first command to release the terminal:
xautolock -time 2 -locker "betterscreenlocker -l" &
Then you can test without opening a second terminal (you will have to manually kill it however).
I don't use betterscreenlocker but as long as it is working properly there shouldn't be any issues. If you run lightdm you could try 'dm-tool lock', also.
Just a thought or two |
|
Back to top |
|
|
Banana Moderator
Joined: 21 May 2004 Posts: 1756 Location: Germany
|
|
Back to top |
|
|
Weezer n00b
Joined: 19 Apr 2024 Posts: 24
|
Posted: Fri Nov 22, 2024 4:28 pm Post subject: |
|
|
Disregard absolutely everything I suggested - HaHaHa! |
|
Back to top |
|
|
vrghost n00b
Joined: 03 Oct 2003 Posts: 60 Location: London
|
Posted: Sat Nov 23, 2024 5:29 pm Post subject: |
|
|
Sorry, PEBKAC, somehow I had gotten the name of the program back to front
As soon as I had fixed the spelling it started working |
|
Back to top |
|
|
|