Bug 1594814
| Summary: | GDM killed by SIGABRT after login | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Tomas Hudziec <thudziec> | ||||||
| Component: | gdm | Assignee: | Ray Strode [halfline] <rstrode> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 7.6 | CC: | jkoten, thudziec | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | gdm-3.28.2-5.el7 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-10-30 10:26:43 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: | |||||||||
| Attachments: |
|
||||||||
was the machine recently upgraded from an earlier rhel release? Your symtoms sound very similar to bug 1477289 . If you had upgraded and not rebooted that would explain why you were getting hit by the bug. I have upgraded the machine from 7.5 to 7.6 beta a week ago, yesterday I did update of system packages, GDM was between them. I rebooted the machine. The bug still occurs after some longer time of inactivity and today I figured out, that it also happens after connecting laptop to docking station. I have ThinkPad X1 Carbon 4th gen with OneLink+ dock. can you post a backtrace? Created attachment 1454770 [details]
backtrace of gdm
Yes, here it is. Hope it is correct.
yup thanks.
Relevant code:
•
res = sd_session_get_class (sessions[i], &service_class);•
if (res < 0) {•
if (res == -ENOENT) {•
free (service_class);•
continue;•
}•
•
Clearly service_class is left uninitialized because sd_session_get_class is returning an error. Problem was introduced in the fix for bug 1489977. Fix is straightforward, need to drop the free call.
since this was introduced in bug 1489977 which is still ON_QA, i piggy backed off the acks for it. Not reproducible any more with gdm-3.28.2-5.el7.x86_64. (Reproducer was to lock the screen and unlock it). *** Bug 1613867 has been marked as a duplicate of this bug. *** 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://access.redhat.com/errata/RHSA-2018:3140 |
Created attachment 1454354 [details] info about gdm crash from /var/log/messages Description of problem: After half an hour of inactivity (and screen lock) logging in back caused GDM crash. Black screen blinked with some text containing two lines with 'permission denied', then desktop shown up for half a second and then GDM again appeared (it logged me off). After second attempt to log in it happened again, then I rebooted system. It have not happened since then. Version-Release number of selected component (if applicable): gdm-3.28.2-4.el7.x86_64 How reproducible: happened once Steps to Reproduce: Don't know exactly, how to reproduce. After second half an hour of inactivity it did not happen. Actual results: successful logging in blinks screen black, shows desktop for a while and then it returns to locked screen Expected results: successful logging in should show desktop Additional info: /var/log/messages show "gdm: *** Error in `/usr/sbin/gdm': double free or corruption (fasttop): 0x000055dcd463a800 ***", backtrace and more consequent events. See attachment.