You are not logged in.
Pages: 1
I recently installed BunsenLabs on my PC. In the past when I've installed it I've been able to lock my screen but on this recent install I'm unable to to. When I right-click and select Lock Screen nothing happens at all. Anyone else getting this issue?
Offline
The Lock Screen menu item runs `bl-lock`, which is a wrapper script for light-locker. Others have reported issues in the past with light-locker, so you may want to search for those threads.
What is the output if you run the script in a terminal?
bl-lock
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline
@usuallymatt: You could also try using xscreensaver. Edit the bl-lock file as superuser, /usr/bin/bl-lock, and substitute xscreensaver-command -lock for all instances of light-locker-command -l. The final results should look something like this:
#!/bin/bash
# bl-lock
# -------
# This is a wrapper for the 'xscreensaver-command -lock' command.
# If running in live mode, offer up a prompt detailing the live session password.
# Else, run xscreensaver-command -lock.
LOCK_COMMAND=(xscreensaver-command -lock)
which ${LOCK_COMMAND[0]} >/dev/null 2>&1 || {
echo "$0: ${LOCK_COMMAND[0]} no such command." >&2
exit 1
}
if [ -d /lib/live ] && [ ! -f /home/$USER/.config/bunsen/bl-lock ]; then
yad --image='bunsenlabs' --window-icon='distributor-logo-bunsenlabs' --center --borders=20 --button=gtk-ok --fixed --on-top --title='Lock screen info:' --text='Lock screen has detected you are running a live session.\nThe username needed to unlock the screen is "user" and the password is "live".\nThis notice will only be displayed once per live session.'
mkdir -p /home/$USER/.config/bunsen
touch /home/$USER/.config/bunsen/bl-lock
fi
"${LOCK_COMMAND[@]}"
exit 0
However, note that every update of bunsen-utilities will overwrite what you've done. To remedy that, checkout johnraff's suggestion. I haven't tried his suggestion yet, so I can't vouch for whether it will work or not.
Last edited by KrunchTime (2016-02-07 03:14:48)
Offline
Aha. Looks like light-locker wasn't running. I've since added it to my autostart and everything works just fine.
With regards to xscreensaver I've never been able to load the Screen Saver screen even on Crunchbang. When I load the screensaver menu item it says "Failed to execute child process "xscreensaver-demo" (no such file or directory). It doesn't matter too much to me because I just use the power management menu to set a blank out time.
Offline
Looks like light-locker wasn't running. I've since added it to my autostart and everything works just fine.
That shouldn't be necessary in fact. Do you have a file 'light-locker.desktop' in /etc/xdg/autostart? How about in $HOME/.config/autostart? The second may not exist, but if it does, it might be preventing light-locker from starting.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
Pages: 1