V Sun, 8 Mar 2015 15:20:15 -0600
Kevin Fenzi <kevin(a)scrye.com> napsáno:
I have been trying to wait for upstream to pick some route forward
here before we commit to having to carry a patch for a long time. ;(
All the patches I have seen have been broken for various cases...
:(
kevin
Well, xflock4 is broken by design, so I think the following patch (from
upstream bz) is still better than the current state... The only
brokenness I noticed is that switch user (from the panel plugin for
actions like lock, switch, sleep, logout, etc.) does not enable
screensaver when I'm using mate-screensaver (maybe I forgot to set
something), so I'm switching by locking first and switching from
screensaver. No other problems noticed after a couple of months of
usage.
--- old/xflock4 2013-07-05 17:30:55.123541658 +0400
+++ new/xflock4 2013-07-05 17:30:55.123541658 +0400
@@ -24,16 +24,18 @@
PATH=/bin:/usr/bin
export PATH
-# Lock by xscreensaver or gnome-screensaver, if a respective daemon is
running +# Lock by xscreensaver or mate-screensaver, if a respective
daemon is running for lock_cmd in \
"xscreensaver-command -lock" \
- "gnome-screensaver-command --lock"
+ "mate-screensaver-command --lock" \
+ "cinnamon-screensaver-command --lock"
do
$lock_cmd >/dev/null 2>&1 && exit
done
# else run another access locking utility, if installed
for lock_cmd in \
+ "i3lock" \
"xlock -mode blank" \
"slock"
do