Bug 113841 - Severe screen flickering and tearing over VNC connections
Summary: Severe screen flickering and tearing over VNC connections
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-06 21:47 UTC by da_audiophile
Modified: 2016-03-07 08:55 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.4.4
Subsystem:
Regression: No
Bisected commit-id:

Attachments
screen grab of the vnc connection (2.76 MB, video/mp4)
2016-03-06 21:47 UTC, da_audiophile 		Details
Add an attachment (proposed patch, testcase, etc.)

Description da_audiophile 2016-03-06 21:47:01 UTC 
Created attachment 207881 [details]
screen grab of the vnc connection

Details:
Upon connecting over vnc to an Xorg server (in this case running Kodi), the resulting video flickers and tears quite severely.  An example screen grab of a vnc session attached to illustrate what I am seeing is attached.  In the past such connections have been very smooth and pleasant.  I see nothing diagnostic in the output of dmesg nor in the output from my vncserver.  I can confirm the behavior with both the x11vnc package and the x0vncserver supplied with tigervnvc.

Glad to supply any diagnostic logs upon request.


Distro:
Arch Linux x86_64

Hardware:
Intel(R) Core(TM) i3-4130T with on board video.
Motherboard: MSI H97I AC (latest BIOS)

Video drivers and xorg version:
xf86-video-intel 1:2.99.917+560+gd167280-1
libva-intel-driver 1.6.2-1
xorg-server 1.18.1-3
Comment 1 Jean Delvare 2016-03-07 08:34:42 UTC 
What is the most recent kernel version (and, if applicable, relevant package versions) with which the problem did not happen?
Comment 2 Jani Nikula 2016-03-07 08:55:46 UTC 
Please file new drm/i915 bugs at the freedesktop.org bugzilla:
https://bugs.freedesktop.org/enter_bug.cgi?product=DRI&component=DRM/Intel
Note You need to log in before you can comment on or make changes to this bug.