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:
I'm trying to setup remote gdm login access as described here:
https://access.redhat.com/solutions/2516
I'm able to connect to the host with vncviewer remotely but, when I click on the user or enter a username, the window disappears and I can see this crash:
reason: gdm killed by SIGTRAP
cmdline: /usr/sbin/gdm
executable: /usr/sbin/gdm
package: gdm-3.28.2-8.el7
component: gdm
pid: 12386
pwd: /
hostname: seceng-idm-1.fqdm.domain
count: 4
abrt_version: 2.1.11
analyzer: CCpp
architecture: x86_64
event_log:
global_pid: 12386
kernel: 3.10.0-947.el7.x86_64
last_occurrence: 1536845223
os_release: Red Hat Enterprise Linux Workstation release 7.6 Beta (Maipo)
pkg_arch: x86_64
pkg_epoch: 1
pkg_fingerprint: 199E 2F91 FD43 1D51
pkg_name: gdm
pkg_release: 8.el7
pkg_vendor: Red Hat, Inc.
pkg_version: 3.28.2
runlevel: 3 5
time: Thu 13 Sep 2018 09:03:28 AM EDT
type: CCpp
uid: 0
username: root
uuid: 8853ad130e68d39cb5a03a0c565eb64b8a44a8bd
Version-Release number of selected component (if applicable):
How reproducible:
always. I've re-installed the host from scratch.
Steps to Reproduce:
1. Follow installation steps from portal article:
https://access.redhat.com/solutions/2516
2. In addiotion, to get a prompt I had to install the following:
yum -y install xorg-x11-server-Xorg
3. Install and configure abrt to capture the crash
Actual results:
See crash report above.
Expected results:
no crash and login should prompt for password and allow expected remote access.
Additional info:
If I do a groupinstall for the "GNOME Desktop" package group, it doesn't seem to crash and kill the window. Now though, it does seem to hang when entering username. I'm able to cancel though and go back and login successfully.
If I attempt a smartcard login, it appears to hang though:
1. remove smartcard
2. connect with vncviewer
3. select user
4. when password prompt appears, insert smart card into reader
5. Password screen never changes to PIN prompt
6. If I click cancel nothing appears to change
7. after a while it dumped core:
Sep 13 12:32:07 seceng-idm-1.fqdn.domain kernel: traps: gnome-shell[14475] general prote
ction ip:7f6e3b32f039 sp:7fff2fc40290 error:0 in libglib-2.0.so.0.5600.1[7f6e3b2e5000+114000]
Sep 13 12:32:07 seceng-idm-1.fqdn.domain abrt-hook-ccpp[14969]: Process 14475 (gnome-shell) of user 42 killed by SIGSEGV - dumping core
I'm not sure if this warrants a different bug, or if it's just another symptom of the same issue.
Let me know if I need to open a different bug.
Comment 7RHEL Program Management
2021-02-15 07:42:38 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.