Bug 1000747

Summary: [abrt] gdm-3.9.90-1.fc21: _IO_default_xsputn: Process /usr/libexec/gdm-simple-slave was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Moez Roy <moez.roy>
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: rstrode, trevor.davenport
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:eb6dd1e6e5533fe1a55ab243bdbf3261e29e022b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 10:18:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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
File: binary none

Description Moez Roy 2013-08-24 21:10:12 UTC 
Version-Release number of selected component:
gdm-3.9.90-1.fc21

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/gdm-simple-slave --display-id /org/gnome/DisplayManager/Displays/_0
crash_function: _IO_default_xsputn
executable:     /usr/libexec/gdm-simple-slave
kernel:         3.11.0-0.rc6.git4.1.fc21.x86_64
runlevel:       N 5
uid:            0

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _IO_default_xsputn at genops.c:447
 #1 _IO_vfprintf_internal at vfprintf.c:1316
 #2 buffered_vfprintf at vfprintf.c:2328
 #3 _IO_vfprintf_internal at vfprintf.c:1289
 #4 _IO_acquire_lock_clear_flags2_fct at ../libio/libioP.h:899
 #5 ___fprintf_chk at fprintf_chk.c:30
 #6 fprintf at /usr/include/bits/stdio2.h:97
 #7 gdm_log_default_handler at gdm-log.c:88
 #10 gdm_slave_stop at gdm-slave.c:859
 #11 on_greeter_environment_session_stopped at gdm-simple-slave.c:1012
Comment 1 Moez Roy 2013-08-24 21:10:18 UTC 
Created attachment 789912 [details]
File: backtrace
Comment 2 Moez Roy 2013-08-24 21:10:21 UTC 
Created attachment 789913 [details]
File: cgroup
Comment 3 Moez Roy 2013-08-24 21:10:25 UTC 
Created attachment 789914 [details]
File: core_backtrace
Comment 4 Moez Roy 2013-08-24 21:10:27 UTC 
Created attachment 789915 [details]
File: dso_list
Comment 5 Moez Roy 2013-08-24 21:10:30 UTC 
Created attachment 789916 [details]
File: environ
Comment 6 Moez Roy 2013-08-24 21:10:32 UTC 
Created attachment 789917 [details]
File: exploitable
Comment 7 Moez Roy 2013-08-24 21:10:34 UTC 
Created attachment 789918 [details]
File: limits
Comment 8 Moez Roy 2013-08-24 21:10:37 UTC 
Created attachment 789919 [details]
File: maps
Comment 9 Moez Roy 2013-08-24 21:10:39 UTC 
Created attachment 789920 [details]
File: open_fds
Comment 10 Moez Roy 2013-08-24 21:10:41 UTC 
Created attachment 789921 [details]
File: proc_pid_status
Comment 11 Moez Roy 2013-08-24 21:10:44 UTC 
Created attachment 789922 [details]
File: var_log_messages
Comment 12 Moez Roy 2013-08-24 21:10:47 UTC 
Created attachment 789923 [details]
File: binary
Comment 13 Jaroslav Reznik 2015-03-03 15:00:33 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 14 Fedora End Of Life 2016-07-19 10:18:57 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.