Bug 1500788

Summary: gdm crashes with vnc based on xinetd with xdmcp setup
Product: Red Hat Enterprise Linux 7 Reporter: Ajinkya Patil <ajipatil>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: diego.santacruz, jkoten, jwright, kwalker, lawrence.creech, lmiksik, mkolbas, tpelka
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 13:04:05 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:

Description Ajinkya Patil 2017-10-11 13:21:49 UTC
Description of problem:
Upon taking to different session with the same user, gdm crashes

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


How reproducible:
100%

Steps to Reproduce:
1.Setup a vnc based on xinetd with xdmcp. {https://access.redhat.com/node/2516}
2.Take access with any user.
3.Again take an access with same user

Actual results:
gdm crashes

Expected results:
GDM should not crash

Additional info:

Comment 2 Diego Santa Cruz 2017-10-16 15:30:56 UTC
I am having a similar problem on CentOS 7, which could be related. I have a Xvnc running with gdm and xdmcp, when the user locks the screen GDM crashes just after entering the password at the unlock screen.

I traced this back to this bug: https://bugzilla.gnome.org/show_bug.cgi?id=786656

Comment 5 Ray Strode [halfline] 2017-11-14 18:58:59 UTC
*** Bug 1485388 has been marked as a duplicate of this bug. ***

Comment 9 Tomas Pelka 2018-02-15 13:24:12 UTC
Can see exactly the same as https://bugzilla.redhat.com/show_bug.cgi?id=1545659

Comment 13 errata-xmlrpc 2018-04-10 13:04:05 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0770