RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 983089 - tigervnc server module for X11 not working with ATI ES1000 515E
Summary: tigervnc server module for X11 not working with ATI ES1000 515E
Keywords:
Status: CLOSED DUPLICATE of bug 1004093
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: tigervnc
Version: 6.4
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Tim Waugh
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-10 13:20 UTC by andreas.merkel
Modified: 2014-05-23 10:32 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-23 10:32:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Xorg configuration (1.31 KB, text/plain)
2013-07-10 13:20 UTC, andreas.merkel
no flags Details
X server log (45.34 KB, text/plain)
2013-07-10 13:21 UTC, andreas.merkel
no flags Details
lspci output (4.87 KB, text/plain)
2013-07-10 13:22 UTC, andreas.merkel
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.