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.

Description of problem:
By default, the Xvfb in 1.17.4-9.el6 no longer accepts connections over TCP, only over Unix domain.  The --listen-tcp flag of xvfb-run no longer works.


Version-Release number of selected component (if applicable):
xorg-x11-server-Xvfb-1.17.4-9.el6.x86_64


How reproducible:
Every time.


Steps to Reproduce:
1. Xvfb :42
2. xdpyinfo localhost:42


Actual results:
xdpyinfo:  unable to open display "localhost:42".


Expected results:
No error.


Additional info:
This might be an intentional change, but I haven't found it mentioned anywhere, so I'm not sure about it.

Obviously there is -listen flag nowadays, so it is possible to explicitly enable TCP.  But for example the script xvfb-run still assumes TCP is on by default.

Hi Göran,

Did you try latest version of Xvfb package: 

 xorg-x11-server-Xvfb-1.17.4-9.5.el6_8.x86_64.rpm 
 https://access.redhat.com/errata/RHBA-2016:1402

I hadn't, but I did right now, and the behaviour seems to be back to the original.  Please resolve this bug.  (For some reason, I don't see "CLOSED" as an option in the status field, so I guess I can't do it myself.)