We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Background: some users (as from https://askubuntu.com/q/1263287/66509 ) do not want to use mate-screensaver, but want to use light-locker instead.
mate-screensaver
light-locker
" Couldn't execute command: xscreensaver-command -lock Verify that this is a valid command. "
This happens because of the fact that mate-settings-daemon does not know anything about light-locker.
mate-settings-daemon
sudo apt-get purge mate-screensaver sudo apt-get autoremove --purge
sudo apt-get install light-locker
<Ctrl>+<Alt>+<L>
Use some kind of hack:
cat <<EOF | sudo tee /usr/local/bin/xscreensaver-command #!/bin/bash light-locker-command -l EOF sudo chmod a+x /usr/local/bin/xscreensaver-command
to introduce the missed xscreensaver-command command.
xscreensaver-command
1.24.0
1.24.0-1
Ubuntu MATE 20.04 LTS
https://pad.lv/1889632
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Background:
some users (as from https://askubuntu.com/q/1263287/66509 ) do not want to use
mate-screensaver
, but want to uselight-locker
instead.Expected behaviour
Actual behaviour
"
Couldn't execute command: xscreensaver-command -lock
Verify that this is a valid command.
"
This happens because of the fact that
mate-settings-daemon
does not know anything aboutlight-locker
.Steps to reproduce the behaviour
<Ctrl>+<Alt>+<L>
to test light-locker functionalityWorkaround
Use some kind of hack:
to introduce the missed
xscreensaver-command
command.MATE general version
1.24.0
Package version
1.24.0-1
Linux Distribution
Ubuntu MATE 20.04 LTS
Link to downstream report of your Distribution
https://pad.lv/1889632
The text was updated successfully, but these errors were encountered: