[Bug 72194] New: Intel driver SNA causes x11vnc to display black screen when running xbmc (Haswell chip this time)

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Sun Dec 1 04:59:15 PST 2013


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

          Priority: medium
            Bug ID: 72194
          Assignee: chris at chris-wilson.co.uk
           Summary: Intel driver SNA causes x11vnc to display black screen
                    when running xbmc (Haswell chip this time)
        QA Contact: intel-gfx-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: da_audiophile at yahoo.com
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: git
         Component: Driver/intel
           Product: xorg

Background: I am experiencing the very same symptoms as I reported in
(https://bugs.freedesktop.org/show_bug.cgi?id=69730) which is now resolved
thanks to Chris.  The problem seems to be unique to my new i3-4130T (Haswell
using HD graphics 4400).

Problem: Connecting to the vncserver (x11vnc) running on the machine using the
i3-4130T (on a motherboard using the H87 chipset) causes a black screen to be
displayed on the vncclient but only when xbmc is active.  Exiting xbmc restores
the expected vnc behavior.  I see nothing relevant in my Xorg logs to indicate
there is a problem.

Linux distro: Arch linux x86_64
Xorg version: 1.14.4

Drivers packages in use (official ARCH packages):
* intel-dri 9.2.4-1
* libva-intel-driver 1.2.1-1
* xf86-video-intel-git version 2.99.906.65.g3dae8b9-1

Command used to start x11vnc on the target box:
/usr/bin/x11vnc -nap -wait 50 -passwd xxx -display :0 -forever -o
/var/log/x11vnc.log -bg

It does not matter if I use the -noxdamage switch; the result is the same.

-- 
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/20131201/296a05a6/attachment.html>


More information about the intel-gfx-bugs mailing list