Version-Release number of selected component: xorg-x11-server-Xorg-1.14.4-11.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: __libc_sigaction environ: executable: /usr/bin/Xorg kernel: 3.16.1-301.mst.fc21.x86_64 open_fds: runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (1 frames) #8 __libc_sigaction at ../sysdeps/unix/sysv/linux/x86_64/sigaction.c:56 Potential duplicate: bug 706364
Created attachment 942322 [details] File: backtrace
Created attachment 942323 [details] File: cgroup
Created attachment 942324 [details] File: core_backtrace
Created attachment 942325 [details] File: dso_list
Created attachment 942326 [details] File: limits
Created attachment 942327 [details] File: maps
Created attachment 942328 [details] File: proc_pid_status
Created attachment 942329 [details] File: var_log_messages
Created attachment 942823 [details] Files from crash The attachment contains everything from the crash. If you see you would like more please let me know and I will get it. Thanks, Devon
Another user experienced a similar problem: Starting game SPACECOM, Xorg crashed. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-VsOmDE/database -seat seat0 -nolisten tcp vt1 crash_function: __libc_sigaction executable: /usr/bin/Xorg kernel: 3.16.3-200.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-11.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Thi shappens when I use three externas screens connected to my lenovo T440s and remove the laptom from the docking station. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-uV9Uke/database -seat seat0 -nolisten tcp vt1 crash_function: __libc_sigaction executable: /usr/bin/Xorg kernel: 3.17.0-0.rc5.git5.1.fc22.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-11.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Browsing with Firefox then desktop restarted. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/X :0 vt1 -background none -nolisten tcp -seat seat0 -auth /var/run/kdm/A:0-xnEhHb crash_function: __libc_sigaction executable: /usr/bin/Xorg kernel: 3.16.2-201.fc20.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.4-11.fc20 reason: Xorg killed by SIGABRT runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.