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.
Created attachment 1133788[details]
journalctl output of gdm with debuglevel
Description of problem:
remote xdmcp session can't unlock the screen
Version-Release number of selected component (if applicable):
gdm-3.14.2-12.el7.x86_64
gnome-session-3.14.0-4.el7.x86_64
systemd-219-19.el7_2.4.x86_64
How reproducible:
always.
Steps to Reproduce:
1. install gnome desktop (yum install gnome-desktop)
2. add tcp listener to gdm by adding DisallowTCP=false to /etc/gdm/custom.conf
3. restart gdm (systemctl restart gdm.service)
4. access machine using xdmcp (on a linux workstation: Xephyr :1 -ac -br -screen 1024x768 -reset -terminate -query server.example.com)
5. log into gdm (using the gnome classic session)
6. see gnome desktop, so far so good.
7. lock the remote screen using the system menu in the top right corner of the gnome shell, lock icon (or wait till the automatic lock kicks in)
8. the gnome curtain displays.
9. hit enter, password prompt shows
10. enter password. Password prompt shows again. no error message.
Actual results:
can't unlock a remote gnome lock screen.
Expected results:
unlock and desktop shows again.
Additional info:
Unlocking the session using loginctl works.
A locally (as in sitting in front of the servers keyboard) logged in user can lock and unlock the screen.
Running gdm with debug enabled here is a shortened version of journalctl, a longer version is attached
gdm[16832]: GdmSessionWorker: state AUTHENTICATED
gdm[16832]: GdmSessionWorker: state AUTHORIZED
gdm[16832]: GdmSessionWorker: state ACCREDITED
gdm[16832]: GdmCommon: process (pid:18514) done (status:0)
gdm[16832]: GdmSession: Emitting 'reauthenticated' signal
gdm[16832]: GLib: g_variant_new_string: assertion 'string != NULL' failed
gdm[16832]: GdmManager: logind 'ActivateSessionOnSeat' org.freedesktop.login1.NoSuchSeat raised:
gdm[16832]: GDBus.Error:org.freedesktop.login1.NoSuchSeat: No seat '[Invalid UTF-8]' known
gdm[16832]: GdmManager: unable to activate session: 26
The glib error and the invalid utf8 look suspicious.
Comment 4Ray Strode [halfline]
2016-08-01 15:47:15 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://rhn.redhat.com/errata/RHBA-2016-2451.html
Created attachment 1133788 [details] journalctl output of gdm with debuglevel Description of problem: remote xdmcp session can't unlock the screen Version-Release number of selected component (if applicable): gdm-3.14.2-12.el7.x86_64 gnome-session-3.14.0-4.el7.x86_64 systemd-219-19.el7_2.4.x86_64 How reproducible: always. Steps to Reproduce: 1. install gnome desktop (yum install gnome-desktop) 2. add tcp listener to gdm by adding DisallowTCP=false to /etc/gdm/custom.conf 3. restart gdm (systemctl restart gdm.service) 4. access machine using xdmcp (on a linux workstation: Xephyr :1 -ac -br -screen 1024x768 -reset -terminate -query server.example.com) 5. log into gdm (using the gnome classic session) 6. see gnome desktop, so far so good. 7. lock the remote screen using the system menu in the top right corner of the gnome shell, lock icon (or wait till the automatic lock kicks in) 8. the gnome curtain displays. 9. hit enter, password prompt shows 10. enter password. Password prompt shows again. no error message. Actual results: can't unlock a remote gnome lock screen. Expected results: unlock and desktop shows again. Additional info: Unlocking the session using loginctl works. A locally (as in sitting in front of the servers keyboard) logged in user can lock and unlock the screen. Running gdm with debug enabled here is a shortened version of journalctl, a longer version is attached gdm[16832]: GdmSessionWorker: state AUTHENTICATED gdm[16832]: GdmSessionWorker: state AUTHORIZED gdm[16832]: GdmSessionWorker: state ACCREDITED gdm[16832]: GdmCommon: process (pid:18514) done (status:0) gdm[16832]: GdmSession: Emitting 'reauthenticated' signal gdm[16832]: GLib: g_variant_new_string: assertion 'string != NULL' failed gdm[16832]: GdmManager: logind 'ActivateSessionOnSeat' org.freedesktop.login1.NoSuchSeat raised: gdm[16832]: GDBus.Error:org.freedesktop.login1.NoSuchSeat: No seat '[Invalid UTF-8]' known gdm[16832]: GdmManager: unable to activate session: 26 The glib error and the invalid utf8 look suspicious.