Version-Release number of selected component: xorg-x11-server-Xorg-1.14.0-3.fc19 Additional info: backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-OaHLmh/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.9.0-0.rc6.git1.2.fc20.x86_64 open_fds: runlevel: N 5 uid: 0 ureports_counter: 1 Truncated backtrace: Thread no. 1 (10 frames) #2 OsAbort at utils.c:1299 #3 ddxGiveUp at xf86Init.c:1075 #4 AbortDDX at xf86Init.c:1119 #5 AbortServer at log.c:670 #6 FatalError at log.c:811 #7 OsSigHandler at osinit.c:147 #9 __memcpy_ssse3_back at ../sysdeps/x86_64/multiarch/memcpy-ssse3-back.S:97 #10 memcpy at /usr/include/bits/string3.h:51 #11 exaMemcpyBox at exa_migration_classic.c:59 #12 exaCopyDirty at exa_migration_classic.c:240 Potential duplicate: bug 703807
Created attachment 734419 [details] File: backtrace
Created attachment 734420 [details] File: cgroup
Created attachment 734421 [details] File: core_backtrace
Created attachment 734422 [details] File: dso_list
Created attachment 734423 [details] File: environ
Created attachment 734424 [details] File: limits
Created attachment 734425 [details] File: maps
Created attachment 734426 [details] File: proc_pid_status
Created attachment 734427 [details] File: var_log_messages
Created attachment 734428 [details] File: binary
Enabled compositing in my window manager reporter: libreport-2.1.4 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.9.5-301.fc19.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.1-4.fc19 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0 xsession_errors:
I rebooted my machine into windows, and then back to linux again reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/X -background none :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch crash_function: OsAbort environ: executable: /usr/bin/Xorg kernel: 3.10.6-200.fc19.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.2-9.fc19 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
When I run Google Chrome, the erro wil happen. reporter: libreport-2.1.6 backtrace_rating: 3 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-xEBddp/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.6-200.fc19.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.2-9.fc19 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) reported_to: Bugzilla: URL=https://bugzilla.redhat.com/show_bug.cgi?id=951262 runlevel: N 5 uid: 0
add comment here reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-RVn3Lh/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.9-200.fc19.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.2-9.fc19 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: N 5 uid: 0
I started a game using wine. The system logged me out. reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-lAMcep/database -seat seat0 -nolisten tcp vt1 crash_function: OsAbort executable: /usr/bin/Xorg kernel: 3.10.9-200.fc19.x86_64 open_fds: package: xorg-x11-server-Xorg-1.14.2-9.fc19 reason: Process /usr/bin/Xorg was killed by signal 6 (SIGABRT) runlevel: unknown uid: 0
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.