[Bug 64675] New: xscreensaver won't go away with latest intel driver (regression)

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 64675
          Assignee: chris at chris-wilson.co.uk
           Summary: xscreensaver won't go away with latest intel driver
                    (regression)
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: nbowler at draconx.ca
          Hardware: Other
            Status: NEW
           Version: git
         Component: Driver/intel
           Product: xorg

After updating xf86-video-intel to latest git, xscreensaver appears to be
broken.  The screensaver itself works, but the unlock dialog does not render at
all (although the mouse pointer appears).  After entering my password, the
(frozen) screensaver image remains on the screen where the unlock dialog should
have been (obscuring everything on that display).  Switching VTs corrects the
issue.  All of this is 100% reproducible.

The screen which did not try to display the xscreensaver password dialog works
properly.

This issue occurs w/ SNA on a 2-screen Zaphod configuration with a G45 chip,
running Xorg server 1.14.1.  It does not appear to happen on non-zaphod dual
head configurations.

Bisection pinpoints the following commit:

16a64649e9c440ab9457467fe04be25719a73e7c is the first bad commit
commit 16a64649e9c440ab9457467fe04be25719a73e7c
Author: Chris Wilson <chris at chris-wilson.co.uk>
Date:   Fri May 10 15:48:58 2013 +0100

    sna: Basic copy-on-write support for cloning pixmaps

    Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>

:040000 040000 2891de17b5a1271fffbf71048055604b1aa0e678
9bbb332cf563e351cbf7924933bd701fcdbb1b2b M    src

-- 
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/20130516/ed104bc0/attachment.html>