Skip to main content

I made a GIF!

Post a Comment

Xfce4 lock screen not working

Xfce4 would not start a screensaver on my Linux system.  Researching it, it ran xflock4 from the command line ad received an error:

 Property "/general/LockCommand" does not exist on channel "xfce4-session".

To fix this, additional configuration needed, but no hacks.

First, verify xflock4 and xfconf-query are available.

$ which xflock4 xfconf-query
/bin/xflock4
/bin/xfconf-query

Next  install a lock screen package that provides 'xlock', 'slock', 'i3lock' or similar. 

$ sudo yum install -y xlockmore-gtk i3lock

Last, add an executable (with options) as /general/LockCommand in the xfce4-session settings.

$ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "xlock -mode matrix" --type string
$ xfconf-query -c xfce4-session --create -p /general/LockCommand --set "i3lock -c 000000" --type string

Test by running xflock4 from the command line or through the GUI.


Labels:

Comments

Anonymous said…
I am actually glad to glance at this website posts which consists
of lots of useful facts, thanks for providing such statistics.
6/26/2017 09:35:00 PM
Anonymous said…
hi, thanks so much, just i have a question, your instructions worked perfectly, but when i press the lock screen command the screen turns black and the ask for the password is horrible, but it's gain, thanks!
8/02/2017 01:57:00 AM
Anonymous said…
Finally something that works for my Fedora 25 VM over spice://
9/21/2018 04:17:00 AM
LopanRS said…
Thank you. Ok in Arch Linux.
4/24/2019 10:57:00 AM
Anonymous said…
Thanks for this, helped me out as slock freezes my system for some reason, i3lock works fine.
5/13/2019 06:09:00 PM
westjgames said…
try light-locker
5/17/2019 09:49:00 AM
westjgames said…
The command to add is
xfconf-query -c xfce4-session --create -p /general/LockCommand --set "light-locker-command -l" --type string
5/17/2019 09:50:00 AM
Post a Comment

Popular posts from this blog

Cisco ASA ICMP packet-tracer

Occasionally devices fail to respond to a ping.  This can result from devices being off-line, having a local firewall enabled or the perimeter firewall configuration.  The Cisco ASA ICMP packet-tracer options differ from the TCP or UDP command options.  An example is below: packet-tracer input outside icmp A.B.C.D 8 0 E.F.G.H The ICMP type is "8" (echo request) with code"0" (none).  There are no options on destination IPv4 address E.F.G.H. Complete ICMP documentation at URL http://www.iana.org/assignments/icmp-parameters/ Complete Cisco ASA packet-tracer documentation at URL http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/p.html#wp1878788
Post a Comment
Read more

X11 Forwarding issue solved

TL;DR Disabling IPv6 necessitates SSHd AddressFamily is "inet" for X11 Forwarding to work. Issue OpenSSH assumes both IPv6 and IPv4 protocols are enabled, and default SSHd AddressFamily value "any" is valid. Quickly skimming the OpenSSH source code, it was not obvious why SSHd does not fail gracefully, selecting only an available IP address family. Therefore, for X11 Forwarding to work correctly, in /etc/ssh/sshd_config we must choose: Defaults - IPv6 enabled and SSHd AddressFamily value " any " Custom - IPv6 disabled and SSHd AddressFamily value " inet " Background PuTTY was not creating a $HOME/.Xauthority file on ssh login and no X11 applications would run, despite setting $DISPLAY.  PuTTY was correctly configured with: X11 Forwarding enabled X display location empty Remote authentication protocol MIT-Magic-Cookie-1 X authority file for local display empty On the initial ssh login there should be a .Xauthority notic
12 comments
Read more