Bug 983089

Summary: tigervnc server module for X11 not working with ATI ES1000 515E
Product: Red Hat Enterprise Linux 6 Reporter: andreas.merkel
Component: tigervncAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: high Docs Contact:
Priority: medium    
Version: 6.4   
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-23 10:32:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Xorg configuration
none
X server log
none
lspci output none

Description andreas.merkel 2013-07-10 13:20:42 UTC
Created attachment 771591 [details]
Xorg configuration

Description of problem:

X.org starts up without problems when the vnc module is enabled. When connecting to the server with a vnc client, the server asks for the credentials and then a black screen is displayed. When terminating the VNC client and trying to connect again, the server does not respond at all.

Version-Release number of selected component (if applicable):

tigervnc-server-module-1.1.0-5.el6.x86_64

How reproducible:

always

Steps to Reproduce:
1. enable the vnc module in xorg.conf
2. restart X
3. try to connect with a vnc client

Actual results:

Black screen is displayed.

Expected results:

Xorg desktop is displayed.

Additional info:

Comment 1 andreas.merkel 2013-07-10 13:21:41 UTC
Created attachment 771596 [details]
X server log

Comment 2 andreas.merkel 2013-07-10 13:22:08 UTC
Created attachment 771604 [details]
lspci output

Comment 3 andreas.merkel 2013-07-10 13:22:37 UTC
The VNC server module works without problems on different hardware.

Comment 5 Tim Waugh 2014-05-23 10:32:49 UTC
I think this is a duplicate of bug #1004093 (vnc extension could be initialized twice leading to a busy loop), a fix for which will be available in the next update.

*** This bug has been marked as a duplicate of bug 1004093 ***