Bug 1117791

Summary: [abrt] gdm: gdm_display_finish(): gdm killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Stephen Gallagher <sgallagh>
Component: gdmAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: chmelarz, Hapoofesgeli, kparal, mikhail.v.gavrilov, peljasz, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/e451091377eb0a4570566c247b201761af35b4e0
Whiteboard: abrt_hash:3775818b2e24d1f3c0aeeceab0d90fe88835169e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:55:01 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Stephen Gallagher 2014-07-09 12:01:03 UTC 
Version-Release number of selected component:
gdm-3.12.2-2.fc21

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/sbin/gdm
crash_function: gdm_display_finish
executable:     /usr/sbin/gdm
kernel:         3.16.0-0.rc4.git0.1.fc21.1.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 gdm_display_finish
 #1 remove_user_session
 #6 ffi_call_unix64 at ../src/x86/unix64.S:76
 #7 ffi_call at ../src/x86/ffi64.c:525
 #8 g_cclosure_marshal_generic at /lib64/libgobject-2.0.so.0
 #11 g_signal_emitv at /lib64/libgobject-2.0.so.0
 #12 gdm_dbus_worker_proxy_g_signal
 #13 ffi_call_unix64 at ../src/x86/unix64.S:76
 #14 ffi_call at ../src/x86/ffi64.c:525
 #15 g_cclosure_marshal_generic at /lib64/libgobject-2.0.so.0
Comment 1 Stephen Gallagher 2014-07-09 12:01:05 UTC 
Created attachment 916730 [details]
File: backtrace
Comment 2 Stephen Gallagher 2014-07-09 12:01:06 UTC 
Created attachment 916731 [details]
File: cgroup
Comment 3 Stephen Gallagher 2014-07-09 12:01:07 UTC 
Created attachment 916732 [details]
File: core_backtrace
Comment 4 Stephen Gallagher 2014-07-09 12:01:07 UTC 
Created attachment 916733 [details]
File: dso_list
Comment 5 Stephen Gallagher 2014-07-09 12:01:08 UTC 
Created attachment 916734 [details]
File: environ
Comment 6 Stephen Gallagher 2014-07-09 12:01:09 UTC 
Created attachment 916735 [details]
File: exploitable
Comment 7 Stephen Gallagher 2014-07-09 12:01:10 UTC 
Created attachment 916736 [details]
File: limits
Comment 8 Stephen Gallagher 2014-07-09 12:01:10 UTC 
Created attachment 916737 [details]
File: maps
Comment 9 Stephen Gallagher 2014-07-09 12:01:11 UTC 
Created attachment 916738 [details]
File: open_fds
Comment 10 Stephen Gallagher 2014-07-09 12:01:12 UTC 
Created attachment 916739 [details]
File: proc_pid_status
Comment 11 Stephen Gallagher 2014-07-09 12:01:13 UTC 
Created attachment 916740 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 16:07:17 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Fedora End Of Life 2016-07-19 11:55:01 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.