Version-Release number of selected component: xorg-x11-server-Xorg-1.16.0-3.fc22 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/Xorg.bin :0 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-wD9p7Y/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/libexec/Xorg.bin kernel: 3.17.0-0.rc1.git0.1.fc22.x86_64 open_fds: runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #2 OsAbort #3 ddxGiveUp #4 AbortServer #5 FatalError #6 OsSigHandler #8 __memcpy_sse2_unaligned at /lib64/libc.so.6 #9 exaMemcpyBox.isra.2 at /usr/lib64/xorg/modules/libexa.so #10 exaCopyDirty at /usr/lib64/xorg/modules/libexa.so #11 exaPrepareAccessReg_mixed at /usr/lib64/xorg/modules/libexa.so #12 ExaCheckComposite at /usr/lib64/xorg/modules/libexa.so Potential duplicate: bug 883090
Created attachment 929516 [details] File: backtrace
Created attachment 929517 [details] File: cgroup
Created attachment 929518 [details] File: core_backtrace
Created attachment 929519 [details] File: dso_list
Created attachment 929520 [details] File: environ
Created attachment 929521 [details] File: limits
Created attachment 929522 [details] File: maps
Created attachment 929523 [details] File: proc_pid_status
Created attachment 929524 [details] File: var_log_messages
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
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.