Bug 1114001 - [abrt] xorg-x11-server-Xorg: Xorg killed by SIGABRT
Summary: [abrt] xorg-x11-server-Xorg: Xorg killed by SIGABRT
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL: https://abrt.fedoraproject.org/faf/re...
Whiteboard: abrt_hash:ed57b6916c13784d08dff98085a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-27 12:29 UTC by Jakub Filak
Modified: 2016-12-01 00:47 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:22:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.91 KB, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: cgroup (154 bytes, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: core_backtrace (3.60 KB, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: dso_list (4.97 KB, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: environ (84 bytes, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: limits (1.29 KB, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: maps (24.37 KB, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: open_fds (48 bytes, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: proc_pid_status (907 bytes, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details
File: var_log_messages (17.21 KB, text/plain)
2014-06-27 12:29 UTC, Jakub Filak
no flags Details

Description Jakub Filak 2014-06-27 12:29:29 UTC
Description of problem:
I'm sorry, but I am not sure what I was doing before this crash happen. Perhaps I swtiched off the computer, because I saw the ABRT problem after boot.

Version-Release number of selected component:
xorg-x11-server-Xorg-1.14.4-9.fc20

Additional info:
reporter:       libreport-2.2.2.15.g25b0
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :0 -background none -verbose -auth /run/gdm/auth-for-gdm-BibOou/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.14.6-200.fc20.x86_64
runlevel:       3 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #6 _XSERVTransClose at /usr/include/X11/Xtrans/Xtrans.c:959
 #7 CloseWellKnownConnections at connection.c:520
 #10 switch_to at lnx_init.c:72
 #11 xf86CloseConsole at lnx_init.c:308

Comment 1 Jakub Filak 2014-06-27 12:29:31 UTC
Created attachment 912796 [details]
File: backtrace

Comment 2 Jakub Filak 2014-06-27 12:29:33 UTC
Created attachment 912797 [details]
File: cgroup

Comment 3 Jakub Filak 2014-06-27 12:29:35 UTC
Created attachment 912798 [details]
File: core_backtrace

Comment 4 Jakub Filak 2014-06-27 12:29:37 UTC
Created attachment 912799 [details]
File: dso_list

Comment 5 Jakub Filak 2014-06-27 12:29:39 UTC
Created attachment 912800 [details]
File: environ

Comment 6 Jakub Filak 2014-06-27 12:29:42 UTC
Created attachment 912801 [details]
File: limits

Comment 7 Jakub Filak 2014-06-27 12:29:44 UTC
Created attachment 912802 [details]
File: maps

Comment 8 Jakub Filak 2014-06-27 12:29:46 UTC
Created attachment 912803 [details]
File: open_fds

Comment 9 Jakub Filak 2014-06-27 12:29:49 UTC
Created attachment 912804 [details]
File: proc_pid_status

Comment 10 Jakub Filak 2014-06-27 12:29:52 UTC
Created attachment 912805 [details]
File: var_log_messages

Comment 11 Ankur Sinha (FranciscoD) 2014-07-17 10:22:19 UTC
Another user experienced a similar problem:

Added an external monitor and tried to change the aspect ratio. It sticks to 4:3 and cannot increase any further. The external monitor does have the capability to use a better aspect ratio, though.

reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/bin/Xorg :1 -background none -noreset -verbose 3 -logfile /dev/null -auth /run/gdm/auth-for-gdm-mXwHT6/database -seat seat0 -nolisten tcp vt1
executable:     /usr/bin/Xorg
kernel:         3.16.0-0.rc2.git4.2.fc21.x86_64
package:        xorg-x11-server-Xorg-1.14.4-11.fc20
reason:         Xorg killed by SIGABRT
runlevel:       N 5
type:           CCpp
uid:            0

Comment 12 Fedora End Of Life 2015-05-29 12:14:26 UTC
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.

Comment 13 Fedora End Of Life 2015-06-29 21:22:01 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.