On Sun, Feb 11, 2018 at 8:35 PM, ToddAndMargo <ToddAndMargo@zoho.com mailto:ToddAndMargo@zoho.com> wrote:
Dear Fedora Xfce, Any work around to this bug? https://bugzilla.redhat.com/show_bug.cgi?id=1544297 <https://bugzilla.redhat.com/show_bug.cgi?id=1544297> HOW CAN I LIVE WITHOUT MY BOUNCING COWS !!??? Fedora 27, x64 installed from Fedora-Xfce-Live-x86_64-27-1.6.iso Xfce 4.12 xscreensaver-gl-base-5.38-1.fc27.x86_64 xscreensaver-5.38-1.fc27.x86_64 xscreensaver-extras-base-5.38-1.fc27.x86_64 xscreensaver-gl-extras-5.38-1.fc27.x86_64 xfce4-screenshooter-plugin-1.8.2-9.fc27.x86_64 xscreensaver-base-5.38-1.fc27.x86_64 xscreensaver-extras-5.38-1.fc27.x86_64 xfce4-screenshooter-1.8.2-9.fc27.x86_64 $ ps aux | grep [s]creen todd 5249 0.0 0.0 184156 5696 ? S 16:20 0:00 xscreensaver -no-splash I can fire up Screen Saver preference, I can preview my screen saver, I set it for five minutes, no screen saver. Restarting the daemon has no effect. How do I get my screen saver to work. It does work on other machines running Xfce and Fedora 26. Reproduces on three machines. Many thanks, -T
On 02/11/2018 06:24 PM, Bruce Hohl wrote:
This is not an answer to bug report but rather a comment and alternate suggestion: Since I do not need a screen saver (graphics) but do want a screen locker I did the following for my Fedora 27 install.
Remove xscreensaver then set power settings in xfce tool: # dnf autoremove xscreensaver xfce4-power-manager-settings
Add simple screen locker & check settings: # dnf install slock (read man page to finish config) Applications > Settings > Session & Startup > Advanced tab: Y = Lock screen before sleep Applications > Settings > Power Manager > System tab: Y = Lock screen when system is going to sleep +++ Press Ctrl+Alt+l which is mapped to the xflock4 script which looks for and runs slock. After using slock to lock the screen, type your password the [Enter] to unlock. There is no password dialogue box. While typing your password the screen will be blue. If an incorrect password is typed the screen turn red ... so try again.
Turning off xfce4-power-manager's "presentation mode" fixed the issue