Bug 1226678

Summary: [abrt] xorg-x11-server-Xorg: __fdelt_chk(): Xorg killed by SIGABRT
Product: [Fedora] Fedora Reporter: Roel van de Kraats <rhbug>
Component: xorg-x11-serverAssignee: X/OpenGL Maintenance List <xgl-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ezwen-redhatbugzilla, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1bd758620223c5d1c7937d57add6f7a87a1bf020
Whiteboard: abrt_hash:7753f032caaaca56a0bb14e1a0b635031e7785d9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 14:25:19 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Roel van de Kraats 2015-05-31 17:59:15 UTC 
Description of problem:
XWayland and Xorg processes were using 100% CPU. Killed them.

Version-Release number of selected component:
xorg-x11-server-Xorg-1.17.1-12.fc22

Additional info:
reporter:       libreport-2.5.1
backtrace_rating: 4
cmdline:        /usr/libexec/Xorg vt3 -displayfd 3 -auth /run/user/578/gdm/Xauthority -nolisten tcp -background none -noreset -keeptty -verbose 3
crash_function: __fdelt_chk
executable:     /usr/libexec/Xorg
global_pid:     4587
kernel:         4.0.4-303.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            578

Truncated backtrace:
Thread no. 1 (8 frames)
 #5 __fdelt_chk at fdelt_chk.c:25
 #6 RemoveEnabledDevice at connection.c:1088
 #7 xf86libinput_off at libinput.c:362
 #8 xf86libinput_device_control at libinput.c:664
 #9 DisableDevice at devices.c:486
 #10 DisableAllDevices at devices.c:530
 #11 dix_main at main.c:308
 #13 _start
Comment 1 Roel van de Kraats 2015-05-31 17:59:17 UTC 
Created attachment 1032928 [details]
File: backtrace
Comment 2 Roel van de Kraats 2015-05-31 17:59:18 UTC 
Created attachment 1032929 [details]
File: cgroup
Comment 3 Roel van de Kraats 2015-05-31 17:59:19 UTC 
Created attachment 1032930 [details]
File: core_backtrace
Comment 4 Roel van de Kraats 2015-05-31 17:59:20 UTC 
Created attachment 1032931 [details]
File: dso_list
Comment 5 Roel van de Kraats 2015-05-31 17:59:21 UTC 
Created attachment 1032932 [details]
File: environ
Comment 6 Roel van de Kraats 2015-05-31 17:59:22 UTC 
Created attachment 1032933 [details]
File: limits
Comment 7 Roel van de Kraats 2015-05-31 17:59:24 UTC 
Created attachment 1032934 [details]
File: maps
Comment 8 Roel van de Kraats 2015-05-31 17:59:25 UTC 
Created attachment 1032935 [details]
File: mountinfo
Comment 9 Roel van de Kraats 2015-05-31 17:59:26 UTC 
Created attachment 1032936 [details]
File: namespaces
Comment 10 Roel van de Kraats 2015-05-31 17:59:27 UTC 
Created attachment 1032937 [details]
File: open_fds
Comment 11 Roel van de Kraats 2015-05-31 17:59:28 UTC 
Created attachment 1032938 [details]
File: proc_pid_status
Comment 12 Roel van de Kraats 2015-05-31 17:59:29 UTC 
Created attachment 1032939 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 14:25:19 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.