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.

Bug 2221816

Summary:	"DisallowTCP=false" option is not being used by /etc/gdm/custom.conf file
Product:	Red Hat Enterprise Linux 8	Reporter:	Larissa <larissa.ford>
Component:	gdm	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED MIGRATED	QA Contact:	Michal Odehnal <modehnal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.6	CC:	ayadav, desktop-qa-list, hdegoede, rstrode, sbarcomb, tpelka, tpopela, vrajput
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 17:43:58 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 Larissa 2023-07-10 21:37:32 UTC

Description of problem:

Was supposed to be fixed in https://bugzilla.redhat.com/show_bug.cgi?id=2029202 but the issue is still occurring.

This is after upgrading gdm:

==>yum install gdm
Last metadata expiration check: 1:20:15 ago on Mon 10 Jul 2023 08:00:48 PM UTC.
Package gdm-1:40.0-23.el8_6.1.x86_64 is already installed.
Dependencies resolved.
===============================================================================================================
 Package             Architecture           Version                        Repository                     Size
===============================================================================================================
Upgrading:
 gdm                 x86_64                 1:40.0-27.el8                 INFORMAL                 881 k

Transaction Summary
===============================================================================================================
Upgrade  1 Package

Total size: 881 k
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                       1/1 
  Running scriptlet: gdm-1:40.0-27.el8.x86_64                                                              1/1 
  Running scriptlet: gdm-1:40.0-27.el8.x86_64                                                              1/2 
  Upgrading        : gdm-1:40.0-27.el8.x86_64                                                              1/2 
  Running scriptlet: gdm-1:40.0-27.el8.x86_64                                                              1/2 
  Running scriptlet: gdm-1:40.0-23.el8_6.1.x86_64                                                          2/2 
  Cleanup          : gdm-1:40.0-23.el8_6.1.x86_64                                                          2/2 
  Running scriptlet: gdm-1:40.0-23.el8_6.1.x86_64                                                          2/2 
  Verifying        : gdm-1:40.0-27.el8.x86_64                                                              1/2 
  Verifying        : gdm-1:40.0-23.el8_6.1.x86_64                                                          2/2 

Upgraded:
  gdm-1:40.0-27.el8.x86_64                                                                                     

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


How reproducible:

run "ps lf -C Xorg" 
"-nolisten tcp" should not be there

Actual results:

==>ps lf -C Xorg
***
/usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3

Expected results:

==>ps lf -C Xorg
***
/usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -background none -noreset -keeptty -novtswitch -verbose 3


Additional info: N/A

Comment 1 Michal Odehnal 2023-07-11 07:19:58 UTC

Hello, did you make sure to restart the gdm or rebooting after the gdm update? Can you please post the contents of your /etc/gdm/custom.conf file? I am currently unable to reproduce on my local machine. But I will test it on a new installation of 8.6 to double check.

Comment 2 Michal Odehnal 2023-07-11 08:08:35 UTC

So the new installation of rhel-8.6 is also without any issue. The gdm version on install was gdm-40.0-23.el8_6.1.x86_64 I tested the issue with this version. I also updated like you to the gdm-1:40.0-27.el8.x86_64 and tested the issue again and it works as expected for me.

Comment 3 Larissa 2023-07-12 20:37:23 UTC

I did reboot my machine after upgrading gdm. Here are the contents of /etc/gdm/custom.conf:

# GDM configuration

[daemon]
# force gdm login screen to use Xorg
WaylandEnable=false

[security]
# enable Xserver listening on TCP ports
DisallowTCP=false

[xdmcp]

[chooser]

[debug]

Comment 4 Ray Strode [halfline] 2023-07-13 12:42:10 UTC

Thank you for your report. The issue is not immediately reproducible in-house, so there's some aspect of the bug that's somehow related to your specific configuration or package set.

Do you have an open support ticket on https://access.redhat.com/ ? If so, can you post a link to it here? If not, can you open one and post a link to this bug report there?

As part of going through Red Hat support, you'll be asked for collect things (like a sosreport, GDM debug logs, etc) that will be helpful in diagnosing your problem.

I notice your repository is called INFORMAL and not one of the Red Hat Enterprise Linux base channels. To be clear, the gdm package installed isn't a local rebuild, right? This is a red hat provided build ? I ask, because the behavior you describe could happen if the package was built without, or with an old version of xorg-x11-server-devel, I think.

Thank you for your continued cooperation. Hopefully we can get to the bottom of the problem you are seeing!

Comment 5 Larissa 2023-07-14 20:12:49 UTC

Hello, I can get the case and sos report to you by next Wednesday. When I install the version that came with the red hat provided build, it installs gdm-40.0-23.el8_6.1.x86_64. After rebooting, I still get the same result:

==>ps lf -C Xorg
***
/usr/libexec/Xorg vt1 -displayfd 3 -auth /run/user/42/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -novtswitch -verbose 3

Comment 7 RHEL Program Management 2023-09-15 17:42:26 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 8 RHEL Program Management 2023-09-15 17:43:58 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.