[Bug 93562] New: intel-virtual-output doesn't sync built-in X11 screensaver

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sat Jan 2 09:22:58 PST 2016


https://bugs.freedesktop.org/show_bug.cgi?id=93562

            Bug ID: 93562
           Summary: intel-virtual-output doesn't sync built-in X11
                    screensaver
           Product: xorg
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/intel
          Assignee: chris at chris-wilson.co.uk
          Reporter: herzog at raffael.ch
        QA Contact: intel-gfx-bugs at lists.freedesktop.org

On the X-server :8 started by Bumblebee, the screensaver is turned on by
default. After 10 minutes without any input, :8 turns black. If an application
running on :0 suppresses the screensaver, this doesn't get forwarded to :8, it
still blanks. I noticed this while trying to calibrate my external monitor
using dispcalGUI in a multi-monitor setup using intel-virtual-output.

Also, when :8 unblanks, there are no damage events on :0, the image on :8 stays
black and gets only partially repainted (on kwin, moving a window repaints
everything).

Current behaviour: X-server :8 uses its own settings for the options BlankTime,
StandbyTime, SuspendTime and OffTime. An application running on :8 that
suppresses the screensaver (like a video player) has no effect on :8 (actual
keyboard and mouse input works fine).

Expected behaviour: The on, blank, standby, suspend and off states of :0 get
forwarded to :8. :8 does not change these states on its own.

This goes back to the following issue/pull request on the Bumblebee project:
https://github.com/Bumblebee-Project/Bumblebee/pull/679

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160102/cdb6c88f/attachment-0001.html>


More information about the intel-gfx-bugs mailing list