Bug 1121356

Created attachment 919296 [details]
File: backtrace

Created attachment 919297 [details]
File: cgroup

Created attachment 919298 [details]
File: core_backtrace

Created attachment 919299 [details]
File: dso_list

Created attachment 919300 [details]
File: limits

Created attachment 919301 [details]
File: maps

Created attachment 919302 [details]
File: proc_pid_status

Created attachment 919303 [details]
File: var_log_messages

Another user experienced a similar problem:

I have updated all things.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-sShciv/database -seat seat0 -nolisten tcp vt1
dso_list:       
executable:     /usr/bin/Xorg
kernel:         3.15.6-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:

I had two displays connected. The crash happened, when I opened the GNOME 'Displays' settings and set the second monitor to 'Turn off'.

Other points of interest may be that this is a hybrid GPU laptop (Radeon HD 8730M plus Haswell graphics) sitting in a docking station. The monitor that was removed was connected to the displayport on the docking station. The primary one is connected to the Displayport on the laptop itself. The monitor connected to the docking station shows visual artefacts (a triangle spanning from the center of the screen to 3 o'clock and the lower-left corner is not refreshed correctly).

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-nP5VFK/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
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:

I was updating my display settings via KDEs "Settings Manager" but had made no changes yet.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/X :0 vt1 -nolisten tcp -auth /root/.serverauth.2459
executable:     /usr/bin/Xorg
kernel:         3.17.4-200.fc20.x86_64
open_fds:       
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 3
type:           CCpp
uid:            0

Created attachment 1001547 [details]
tar.gz file

Hans,

Just had another crash of X11. Sigh... Here are 3 logs that I have gathered. Hopefully the tar.gz file will upload.

George...

Created attachment 1001549 [details]
tar.gz file

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.