Here is a section of xscreensaver.log. The screen had been on but
black. The activity at 17:56 was when I moved the mouse to wake it up,
but it had been on all day despite the room being vacant.
xscreensaver: 21:02:54: user is active (keyboard activity)
xscreensaver: 21:02:54: unblanking screen at Sat Nov 29 21:02:54 2014.
xscreensaver: 21:02:54: 0: ungrabbing mouse (was 0xaa).
xscreensaver: 21:02:54: 0: ungrabbing keyboard (was 0xaa).
xscreensaver: 21:02:54: starting de-race timer (10 seconds.)
xscreensaver: 21:02:54: awaiting idleness.
xscreensaver: 21:03:04: de-race completed.
xscreensaver: 21:04:15: 0: screen change event received
xscreensaver: 21:04:15: 0: screen change event received
xscreensaver: 21:04:15: new layout:
xscreensaver: 21:04:15: WARNING: RANDR and Xinerama report different
xscreensaver: 21:04:15: screen layouts! Believing RANDR.
xscreensaver: 21:04:15: screens in use: 1
xscreensaver: 21:04:15: 3/0: 2560x1440+0+0 (DP2)
xscreensaver: 21:04:15: rejected screens: 4
xscreensaver: 21:04:15: 0/0: 1920x1080+0+0 (eDP1) -- enclosed by 3
(2560x1440+0+0)
xscreensaver: 21:04:15: 1/0: 1920x1080+0+0 (DP1) -- output disabled
xscreensaver: 21:04:15: 2/0: 1920x1080+0+0 (HDMI1) -- output disabled
xscreensaver: 21:04:15: 4/0: 1920x1080+0+0 (HDMI2) -- output disabled
xscreensaver: 21:04:15: 0: resize 0x2c00001 from 1920x1080+0+0 to
2560x1440+0+0
xscreensaver: 21:04:15: 0: screen change event received
xscreensaver: 21:04:16: 0: screen change event received
xscreensaver: 21:04:17: new layout:
xscreensaver: 21:04:17: WARNING: RANDR and Xinerama report different
xscreensaver: 21:04:17: screen layouts! Believing RANDR.
xscreensaver: 21:04:17: screens in use: 1
xscreensaver: 21:04:17: 3/0: 2560x1440+0+0 (DP2)
xscreensaver: 21:04:17: rejected screens: 4
xscreensaver: 21:04:17: 0/0: 0x0+0+0 (eDP1) -- enclosed by 3
(2560x1440+0+0)
xscreensaver: 21:04:17: 1/0: 0x0+0+0 (DP1) -- output disabled
xscreensaver: 21:04:17: 2/0: 0x0+0+0 (HDMI1) -- output disabled
xscreensaver: 21:04:17: 4/0: 0x0+0+0 (HDMI2) -- output disabled
xscreensaver: 21:12:19: user is idle (timeout)
xscreensaver: 21:12:19: blanking screen at Sat Nov 29 21:12:19 2014.
xscreensaver: 21:12:19: 0: grabbing keyboard on 0xaa... GrabSuccess.
xscreensaver: 21:12:19: 0: grabbing mouse on 0xaa... GrabSuccess.
xscreensaver: 21:12:19: fading...
xscreensaver: 21:12:21: fading done.
xscreensaver: 21:13:18: disabling server builtin screensaver:
xscreensaver: 21:13:18: (xset s 0 0; xset s blank; xset s expose)
xscreensaver: 21:23:21: timed out; activating lock.
xscreensaver: 21:23:21: 0: locked mode switching.
xscreensaver: 17:56:44: user is active (keyboard activity)
xscreensaver: 17:56:45: pam_start ("xscreensaver", "jgoerzen", ...) ==>
0 (Success)
xscreensaver: 17:56:45: pam_set_item (p, PAM_TTY, ":0.0") ==> 0 (Success)
xscreensaver: 17:56:45: pam_authenticate (...) ...
xscreensaver: 17:56:45: pam_conversation (ECHO_OFF="Password: ") ...
xscreensaver: 17:56:45: 0: mouse is at 518,435.
xscreensaver: 17:56:45: 0: creating password dialog ("")
xscreensaver: 17:56:45: grabbing server...
xscreensaver: 17:56:45: 0: ungrabbing mouse (was 0xaa).
xscreensaver: 17:56:45: 0: grabbing mouse on 0x2c005b1... GrabSuccess.
xscreensaver: 17:56:45: ungrabbing server.
xscreensaver: 17:56:53: input finished.
Note - it does seen to have the correct screen to blank.
John
On 11/21/2014 02:28 PM, Jamie Zawinski wrote:
> On Nov 21, 2014, at 5:36 AM, John Goerzen <jgoer...@complete.org> wrote:
>
>> I am quite sure it's not just that the mouse is getting bumped, because
>> I have observed that the monitor will not enter power-saving mode at all
>> for days, and then after a reboot, it will work again.
> Huh. Well, run it with -log for a few days and see what shows up. You will
> see a line when xscreensaver notices that the monitor has powered down. If it
> thinks it's still powered down, it won't launch hacks. The only time
> xscreensaver explicitly powers on the monitor is when unblanking the screen
> or displaying the unlock dialog. And even in those situations, it should time
> out and power off again eventually.
>
> Possibly some other app is messing with your DPMS settings, or turning the
> monitor back on. The "notifications" thing you're seeing suggests that that
> might be happening.
>
>> Thanks for xscreensaver (and Netscape, and XEmace, while I'm at it.)
> Thanks, glad you like it!
>
> --
> Jamie Zawinski http://www.jwz.org/ http://www.dnalounge.com/
>
>
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
