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 1449380

Summary:	gdm-session crashes when switching user
Product:	Red Hat Enterprise Linux 7	Reporter:	Roshni <rpattath>
Component:	gnome-session	Assignee:	Ray Strode [halfline] <rstrode>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	jjelen
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:	2017-06-27 17:41:24 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 Roshni 2017-05-09 20:32:03 UTC

Description of problem:
gdm-session crashes when switching user

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

How reproducible:
always

Steps to Reproduce:
1. Login using smartcard pin
2. Lock screen
3. Click "Login as another user"
4. Login using smartcard pin

Actual results:
[root@dhcp129-77 ~]# abrt-cli list --since 1494361228
id 47149a8279ab8f1b04d69eb8f845b1041cf3465a
reason:         gnome-session-failed killed by SIGSEGV
time:           Tue 18 Apr 2017 02:45:11 PM EDT
cmdline:        /usr/libexec/gnome-session-failed --debug --allow-logout
package:        gnome-session-3.22.3-3.el7
uid:            42 (gdm)
count:          63
Directory:      /var/spool/abrt/ccpp-2017-04-18-14:45:11-12707
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-04-18-14:45:11-12707' for creating a case in Red Hat Customer Portal

Expected results:


Additional info:

Comment 2 Jakub Jelen 2017-05-10 08:11:00 UTC

The actual coredump would be helpful. I don't have bare-metal RHEL7.4 machine to reproduce this scenario.

Or can we get at least the debug log and environment variables as in the bug #1449367?

Comment 3 Roshni 2017-05-10 14:13:15 UTC

This was the complete list

[root@dhcp129-77 ~]# abrt-cli ls
id 47149a8279ab8f1b04d69eb8f845b1041cf3465a
reason:         gnome-session-failed killed by SIGSEGV
time:           Tue 18 Apr 2017 02:45:11 PM EDT
cmdline:        /usr/libexec/gnome-session-failed --debug --allow-logout
package:        gnome-session-3.22.3-3.el7
uid:            42 (gdm)
count:          62
Directory:      /var/spool/abrt/ccpp-2017-04-18-14:45:11-12707
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-04-18-14:45:11-12707' for creating a case in Red Hat Customer Portal

id 663a32ce0905067c82eb8f8a52ef0c486ebcee3d
reason:         Xorg killed by SIGABRT
time:           Tue 09 May 2017 04:16:26 PM EDT
cmdline:        /usr/bin/X :0 -background none -noreset -audit 4 -verbose -logverbose 7 -core -auth /run/gdm/auth-for-gdm-zhEXXU/database -seat seat0 -nolisten tcp vt1
package:        xorg-x11-server-Xorg-1.19.3-3.el7
uid:            0 (root)
count:          1
Directory:      /var/spool/abrt/ccpp-2017-05-09-16:16:26-4613
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-05-09-16:16:26-4613' for creating a case in Red Hat Customer Portal

id 19457307ec382739b446ea08133a74f9bc14453d
reason:         gnome-settings-daemon killed by SIGSEGV
time:           Thu 04 May 2017 03:04:54 PM EDT
cmdline:        /usr/libexec/gnome-settings-daemon
package:        gnome-settings-daemon-3.22.2-1.el7
uid:            42 (gdm)
count:          2
Directory:      /var/spool/abrt/ccpp-2017-05-04-15:04:54-31639
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-05-04-15:04:54-31639' for creating a case in Red Hat Customer Portal

id 58f982d5c425a0cc2675b7cb0392492b34aade0d
reason:         gdm-session-worker killed by SIGSEGV
time:           Mon 08 May 2017 01:16:27 PM EDT
cmdline:        'gdm-session-worker [pam/gdm-smartcard]'
package:        gdm-3.22.3-9.el7
uid:            0 (root)
count:          2
Directory:      /var/spool/abrt/ccpp-2017-05-08-13:16:27-4084
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-05-08-13:16:27-4084' for creating a case in Red Hat Customer Portal

id cf26a069f30d8779774a9bcb55dda7213e177ec1
reason:         xulrunner killed by SIGSEGV
time:           Thu 04 May 2017 02:46:25 PM EDT
cmdline:        /usr/lib64/xulrunner/xulrunner ./application.ini
package:        xulrunner-31.6.0-2.el7_1
uid:            1001 (musterfraumaike)
count:          1
Directory:      /var/spool/abrt/ccpp-2017-05-04-14:46:25-29170
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-05-04-14:46:25-29170' for creating a case in Red Hat Customer Portal

id 2c87ee5fbf08e49e0b07e0bbd6c3724354c37e96
reason:         escd killed by SIGSEGV
time:           Wed 03 May 2017 10:20:50 AM EDT
cmdline:        ./escd '--key_Inserted=\"/usr/bin/esc\"' '--on_Signal=\"/usr/bin/esc\"'
package:        esc-1.1.0-37.el7
uid:            1000 (rpattath)
count:          1
Directory:      /var/spool/abrt/ccpp-2017-05-03-10:20:50-15610
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-05-03-10:20:50-15610' for creating a case in Red Hat Customer Portal

id 9f84ec9419779b1746a790a3f9d88505e07329f3
reason:         xulrunner killed by SIGSEGV
time:           Fri 21 Apr 2017 02:36:38 PM EDT
cmdline:        /usr/lib64/xulrunner/xulrunner ./application.ini
package:        xulrunner-31.6.0-2.el7_1
uid:            1000 (rpattath)
count:          1
Directory:      /var/spool/abrt/ccpp-2017-04-21-14:36:38-15766
Run 'abrt-cli report /var/spool/abrt/ccpp-2017-04-21-14:36:38-15766' for creating a case in Red Hat Customer Portal

id 7b4265a5ec50c4215f1c4343e026fca577398db5
reason:         gnome-session-failed killed by SIGSEGV
time:           Tue 18 Apr 2017 02:49:06 PM EDT
cmdline:        /usr/libexec/gnome-session-failed --debug --allow-logout
uid:            1000
count:          3
Directory:      /var/spool/abrt/ccpp-2017-04-18-14:49:06-16361
Reported:       cannot be reported

id 26c9f8ac80a084922aa13beb837ae02d23a4d4b5
reason:         nm.py:760:nm_device_setting_value:SettingsNotFoundError: SettingsNotFoundError('virbr0',)
time:           Tue 18 Apr 2017 02:03:22 PM EDT
cmdline:        python -m initial_setup
package:        initial-setup-0.3.9.30-1.el7
uid:            0 (root)
count:          1
Directory:      /var/spool/abrt/Python-2017-04-18-14:03:22-1307
Run 'abrt-cli report /var/spool/abrt/Python-2017-04-18-14:03:22-1307' for creating a case in Red Hat Customer Portal

The Autoreporting feature is disabled. Please consider enabling it by issuing
'abrt-auto-reporting enabled' as a user with root privileges

Comment 4 Jakub Jelen 2017-05-10 15:17:24 UTC

The backtrace from the coredump (id 7b4265a5ec50c4215f1c4343e026fca577398db5 above) looks like pointing directly to the gnome-session without the reference to opensc:

Program terminated with signal 11, Segmentation fault.
#0  0x00007f6f77bdfc99 in _gtk_style_provider_private_get_settings (provider=0x0) at gtkstyleproviderprivate.c:123
123	  iface = GTK_STYLE_PROVIDER_PRIVATE_GET_INTERFACE (provider);
(gdb) bt
#0  0x00007f6f77bdfc99 in _gtk_style_provider_private_get_settings (provider=0x0) at gtkstyleproviderprivate.c:123
#1  0x00007f6f77a77818 in gtk_css_value_initial_compute (value=<optimized out>, property_id=1, provider=0x0, style=0x23c6030, parent_style=0x0) at gtkcssinitialvalue.c:52
#2  0x00007f6f77a8c944 in gtk_css_static_style_compute_value (style=0x23c6030, provider=<optimized out>, parent_style=<optimized out>, id=1, specified=0x7f6f781f9320 <inherit>, section=0x0)
    at gtkcssstaticstyle.c:237
#3  0x00007f6f77a78b8c in _gtk_css_lookup_resolve (lookup=lookup@entry=0x23c3800, provider=provider@entry=0x0, style=style@entry=0x23c6030, parent_style=parent_style@entry=0x0) at gtkcsslookup.c:122
#4  0x00007f6f77a8c86c in gtk_css_static_style_new_compute (provider=provider@entry=0x0, matcher=matcher@entry=0x0, parent=parent@entry=0x0) at gtkcssstaticstyle.c:195
#5  0x00007f6f77a8c8c5 in gtk_css_static_style_get_default () at gtkcssstaticstyle.c:164
#6  0x00007f6f77a79552 in gtk_css_node_init (cssnode=0x23bc910) at gtkcssnode.c:663
#7  0x00007f6f762b3fd8 in g_type_create_instance (type=37486480) at gtype.c:1860
#8  0x00007f6f76297d8d in g_object_new_internal (class=class@entry=0x23c26c0, params=params@entry=0x0, n_params=n_params@entry=0) at gobject.c:1783
#9  0x00007f6f7629994d in g_object_newv (object_type=object_type@entry=37486480, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at gobject.c:1930
#10 0x00007f6f7629a114 in g_object_new (object_type=37486480, first_property_name=first_property_name@entry=0x0) at gobject.c:1623
#11 0x00007f6f77a94cca in gtk_css_widget_node_new (widget=widget@entry=0x23c02a0) at gtkcsswidgetnode.c:297
#12 0x00007f6f77c771f2 in gtk_widget_init (instance=0x23c02a0, g_class=0x23bfa00) at gtkwidget.c:4414
#13 0x00007f6f762b3fd8 in g_type_create_instance (type=37363152) at gtype.c:1860
#14 0x00007f6f76297d8d in g_object_new_internal (class=class@entry=0x23bfa00, params=params@entry=0x0, n_params=n_params@entry=0) at gobject.c:1783
#15 0x00007f6f7629994d in g_object_newv (object_type=object_type@entry=37363152, n_parameters=n_parameters@entry=0, parameters=parameters@entry=0x0) at gobject.c:1930
#16 0x00007f6f7629a114 in g_object_new (object_type=37363152, first_property_name=first_property_name@entry=0x0) at gobject.c:1623
#17 0x0000000000401f13 in main (argc=1, argv=0x7ffc0148e0c8) at gsm-fail-whale-dialog.c:382

There is NULL pointer to provider unhandled for some reason. I believe this should be re-assigned to gnome, since I have no idea where to look further, given that all the backtrace is in gnome code.

Comment 5 Ray Strode [halfline] 2017-05-10 21:07:38 UTC

so the crash from comment 4 is already reported as bug 1397773 but isn't likely related to a user switching crash.  It's a crash trying to show the fail whale (so crash because things have already gone sideways).  I mean you could see the notification from abrt-gui showing the crash message from earlier when you user switch so I could see how it could be confused for being related to user switching.

But there are also crashes in esc, xulrunner, gnome-settings-daemon, and gdm-session-worker.  That smells strongly of a smartcard related crash.  smartcard is about the only thing those processes have in commen.  Of course they could be crashing for independent reasons.

Jakub, do you by chance have stack trace from one or more of those?

Comment 6 Jakub Jelen 2017-05-11 07:16:35 UTC

Roshni still has the computer with the setup, coredumps and reproducers running if you need some more information to collect.
The other crashes in the list are from different times/days so I don't think they are related to this problem. Some pointers how to collect some more information from this crash would be helpful.
Ping me once you will be online.

Comment 7 Ray Strode [halfline] 2017-06-27 17:41:24 UTC


*** This bug has been marked as a duplicate of bug 1392970 ***