Bug 1500788 - gdm crashes with vnc based on xinetd with xdmcp setup
Summary: gdm crashes with vnc based on xinetd with xdmcp setup
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gdm
Version: 7.4
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Ray Strode [halfline]
QA Contact: Desktop QE
: 1485388 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2017-10-11 13:21 UTC by Ajinkya Patil
Modified: 2018-05-17 14:39 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-10 13:04:05 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3213021 None None None 2017-10-11 13:59:20 UTC
Red Hat Product Errata RHBA-2018:0770 None None None 2018-04-10 13:05:33 UTC

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:

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.


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