Bug 1544297 - xscreensaver not working in 27
Summary: xscreensaver not working in 27
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: 27
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-02-12 01:31 UTC by Todd
Modified: 2018-02-12 06:47 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-02-12 06:47:46 UTC

Attachments (Terms of Use)
.xscreensaver (13.33 KB, text/plain)
2018-02-12 04:25 UTC, Todd
no flags Details
xscreensaver -debug -log debug.txt (66.21 KB, text/plain)
2018-02-12 04:44 UTC, Todd
no flags Details
ps auwwx (24.43 KB, text/plain)
2018-02-12 06:12 UTC, Todd
no flags Details

Description Todd 2018-02-12 01:31:02 UTC
Dear Fedora,


Fedora 27, x64 installed from Fedora-Xfce-Live-x86_64-27-1.6.iso
Xfce 4.12

$ 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.

Many thanks,

Comment 1 Todd 2018-02-12 01:31:36 UTC
Oh and this repeats on three machines.

Comment 2 Mamoru TASAKA 2018-02-12 04:16:54 UTC
Would you attach your ~/.xscreensaver ? Also would you try below?
- open a terminal
- once terminate xscreensaver with "$ xscreensaver -exit"
- launch xscreensaver with debug mode as "$ xscreensaver -debug -log debug.txt"
- wait 5 ~ 6 min
- then attach "debug.txt" on this bug?

Comment 3 Todd 2018-02-12 04:25:32 UTC
Created attachment 1394785 [details]

Comment 4 Todd 2018-02-12 04:40:34 UTC
(In reply to Mamoru TASAKA from comment #2)
> Would you attach your ~/.xscreensaver ? 


> Also would you try below?
> - open a terminal
> - once terminate xscreensaver with "$ xscreensaver -exit"

No such animal:
$ xscreensaver -exit
xscreensaver: 20:25:49: unknown option "-exit".  Try "-help".


$ ps aux | grep [s]creen
todd      5249  0.0  0.0 184456  5820 ?        S    16:20   0:02 xscreensaver -no-splash

$ kill -9 5249

And it stayed gone

> - launch xscreensaver with debug mode as "$ xscreensaver -debug -log
> debug.txt"

$ xscreensaver -debug -log debug.txt
xscreensaver: 20:28:43: logging to file debug.txt

> - wait 5 ~ 6 min

waiting start: 20:29   stop: 20:39

> - then attach "debug.txt" on this bug?

will do

Comment 5 Todd 2018-02-12 04:44:36 UTC
Created attachment 1394786 [details]
xscreensaver -debug -log debug.txt

Comment 6 Mamoru TASAKA 2018-02-12 05:03:19 UTC
Oh, it was "$ xscreensaver-command -exit", but as you killed xscreensaver with SIGKILL, it is okay.

So xscreensaver says frequently
> xscreensaver: 20:41:08: ClientMessage DEACTIVATE received while inactive: resetting idle timer.

this means xscreensaver receives frequestly DEACTIVATE message with "$ xscreensaver-command -deactivate" command. I guess some other process (like mplayer or so) are repeatedly forking this "$ xscreensaver-command -deactivate" command.

Would you check
- what other process are running ("$ ps auwwx", for example)
- if you are watching some video or so, would you first try stopping it and try again?
- I guess mplayer GUI or so may have option "stop xscreensaver from blanking screen" option. If such GUI has something like such option, try disabling that?

Comment 7 Todd 2018-02-12 05:38:01 UTC
I am turning off various programs to see who is doing it.  Is there a way to trace down the culprit?

Comment 8 Todd 2018-02-12 06:12:28 UTC
Created attachment 1394792 [details]
ps auwwx

I have turned off everything I can think of to turn off.  VLC was paused, but I was listened to music without videos.  And turning vlc off did not help.

The attached ps auwwx is with everything off, except the terminal I used to make the ps.  Any thoughts as to how to trace the offender down?

Comment 9 Mamoru TASAKA 2018-02-12 06:13:40 UTC
Or after googling, I've found that XFCE (or more specific, xfce4-power-manager) has "presentation mode" and from the code it may be doing this. Would you try disabling this mode (if you are setting this mode)?

Comment 10 Mamoru TASAKA 2018-02-12 06:24:44 UTC
If the above does not help, you can survey what has sending -deactivate command by

- Once moving /usr/bin/xscreensaver-command to some other directory (such as /usr/libexec/xscreensaver/xscreensaver-command)
- as root, do

cat > /usr/bin/xscreensaver-command <<EOF

if [ -n $HOME ] ; then 
  pstree -l -p > $HOME/xscreensaver-command-pid.txt
/usr/libexec/xscreensaver/xscreensaver-command "$@"
chmod 0755 /usr/bin/xscreensaver-command

and again wait for 5 min, then check $HOME/xscreensaver-command-pid.txt

Comment 11 Todd 2018-02-12 06:35:55 UTC
Awesome!  Thank you.  I am writing all this down.  (I also wrote you something off line.)

Comment 12 Mamoru TASAKA 2018-02-12 06:47:46 UTC
Okay, anyway thank you for reporting. I am glad that you can see cow bouncing again!

Note You need to log in before you can comment on or make changes to this bug.