Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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:
When we setup VNC based on xinetd with XDMCP for GDM on RHEL7.2 follow the kcs as below:
https://access.redhat.com/solutions/2516
At last step:
[root@R72 ~]# vncviewer localhost:5950
TigerVNC Viewer 64-bit v1.3.1 (20150902)
Built on Sep 2 2015 at 11:19:20
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Fri Jan 20 09:45:27 2017
CConn: connected to host localhost port 5950
CConn: End of stream
[root@R72 ~]#
and log message as below:
Jan 20 09:45:27 R72 xinetd[12233]: START: vnc01-640x480x16 pid=14726 from=::1
Jan 20 09:45:27 R72 kernel: Xvnc[14726]: segfault at 0 ip 0000000000527267 sp 00007ffdac64c4b0 error 4 in Xvnc[400000+238000]
Jan 20 09:45:27 R72 xinetd[12233]: EXIT: vnc01-640x480x16 signal=11 pid=14726 duration=0(sec)
Version-Release number of selected component (if applicable):
[root@R72 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.2 (Maipo)
[root@R72 ~]# yum list tigervnc*
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Installed Packages
tigervnc.x86_64 1.3.1-3.el7 @LocalISO
tigervnc-icons.noarch 1.3.1-3.el7 @LocalISO
tigervnc-license.noarch 1.3.1-3.el7 @anaconda/7.2
tigervnc-server.x86_64 1.3.1-3.el7 @LocalISO
tigervnc-server-minimal.x86_64 1.3.1-3.el7 @anaconda/7.2
[root@R72 ~]#
How reproducible:
Steps to Reproduce:
1. yum install gdm tigervnc tigervnc-server xinetd
2. systemctl enable xinetd.service
3. vim /etc/gdm/custom.conf
[xdmcp]
Enable=true
4. vim /etc/xinetd.d/xvncserver
5. vim /etc/services
6. init 3
7. init 5
8. vncviewer localhost:5950
Actual results:
[root@R72 ~]# vncviewer localhost:5950
TigerVNC Viewer 64-bit v1.3.1 (20150902)
Built on Sep 2 2015 at 11:19:20
Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt)
See http://www.tigervnc.org for information on TigerVNC.
Fri Jan 20 09:45:27 2017
CConn: connected to host localhost port 5950
CConn: End of stream
[root@R72 ~]#
Expected results:
It should be a pop-up window for user to login.
Additional info:
Only on RHEL7.3 can success.
and on RHEL7.2 i can see the abrt message as below:
[root@R72 ~]# cat /var/spool/abrt/ccpp-2017-01-19-17\:05\:58-14875/package
tigervnc-server-minimal-1.3.1-3.el7
so i # yum update tigervnc-server-minimal -y and that issue is disappeared