Bug 1484730 - [abrt] xorg-x11-server-Xorg: OsLookupColor(): Display server crashed
Summary: [abrt] xorg-x11-server-Xorg: OsLookupColor(): Display server crashed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 26
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:13ed251c27f43739b2735501ffa...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-24 08:46 UTC by Toomas Kaevand
Modified: 2018-05-29 11:33 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-29 11:33:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: Xorg.0.log (31.98 KB, text/plain)
2017-08-24 08:46 UTC, Toomas Kaevand
no flags Details
File: backtrace (116 bytes, text/plain)
2017-08-24 08:46 UTC, Toomas Kaevand
no flags Details
File: cpuinfo (1.24 KB, text/plain)
2017-08-24 08:46 UTC, Toomas Kaevand
no flags Details
File: dmesg (74.09 KB, text/plain)
2017-08-24 08:46 UTC, Toomas Kaevand
no flags Details
File: dso_list (164 bytes, text/plain)
2017-08-24 08:46 UTC, Toomas Kaevand
no flags Details
File: etc_X11_xorg_conf_d.tar.gz (521 bytes, application/octet-stream)
2017-08-24 08:46 UTC, Toomas Kaevand
no flags Details
File: usr_share_xorg_conf_d.tar.gz (1.95 KB, application/octet-stream)
2017-08-24 08:47 UTC, Toomas Kaevand
no flags Details
Better backtrace for the crash in comment 8 (9.02 KB, text/plain)
2017-09-27 18:32 UTC, Jeremy Reed
no flags Details

Description Toomas Kaevand 2017-08-24 08:46:39 UTC
Description of problem:
Browser GPU acceleration (as always).

Version-Release number of selected component:
xorg-x11-server-Xorg-1.19.3-4.fc26

Additional info:
reporter:       libreport-2.9.1
crash_function: OsLookupColor
executable:     /usr/libexec/Xorg
kernel:         4.12.5-300.fc26.x86_64
runlevel:       N 5
type:           xorg
uid:            0

Truncated backtrace:
0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59c629]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7fc2e14ad30f]

Comment 1 Toomas Kaevand 2017-08-24 08:46:49 UTC
Created attachment 1317511 [details]
File: Xorg.0.log

Comment 2 Toomas Kaevand 2017-08-24 08:46:51 UTC
Created attachment 1317512 [details]
File: backtrace

Comment 3 Toomas Kaevand 2017-08-24 08:46:53 UTC
Created attachment 1317513 [details]
File: cpuinfo

Comment 4 Toomas Kaevand 2017-08-24 08:46:55 UTC
Created attachment 1317514 [details]
File: dmesg

Comment 5 Toomas Kaevand 2017-08-24 08:46:57 UTC
Created attachment 1317515 [details]
File: dso_list

Comment 6 Toomas Kaevand 2017-08-24 08:46:59 UTC
Created attachment 1317516 [details]
File: etc_X11_xorg_conf_d.tar.gz

Comment 7 Toomas Kaevand 2017-08-24 08:47:01 UTC
Created attachment 1317517 [details]
File: usr_share_xorg_conf_d.tar.gz

Comment 8 Jeremy Reed 2017-09-26 14:56:04 UTC
Description of problem:
The X server seems to crash when waking the laptop from suspend.
My session gets shut down, all open apps get killed, and I get dropped back to a login screen.

Version-Release number of selected component:
xorg-x11-server-Xorg-1.19.3-4.fc26

Additional info:
reporter:       libreport-2.9.1
crash_function: OsLookupColor
executable:     /usr/libexec/Xorg
kernel:         4.12.13-300.fc26.x86_64
runlevel:       N 5
type:           xorg
uid:            0

Truncated backtrace:
0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59c629]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f7e376b63ff]

Comment 9 Olivier Fourdan 2017-09-27 09:13:09 UTC
Unfortunately, the backtrace in attachment 1317512 [details] or comment 8 is useless.

The crash at the end of the log in in attachment 1317511 [details] occurs in NVidia closed source driver.

Also worth noting this:

[ 16748.975] (EE) NVIDIA(0): Failed to allocate primary buffer: out of memory.
[ 16748.975] (EE) NVIDIA(0):  *** Aborting ***

Comment 10 Jeremy Reed 2017-09-27 18:32:13 UTC
Created attachment 1331524 [details]
Better backtrace for the crash in comment 8

Comment 11 Jeremy Reed 2017-09-27 18:36:52 UTC
Oliver,

   Thanks for taking a look at this.  Sorry about the backtrace, the automated tool provided that.  I went digging into my /var/log/messages log and found the full backtrace, and I've attached it as attachment 1331524 [details].

   It does look like this is another crash in the NVidia closed source driver.  Let me know if you need more details.

~Jeremy

Comment 12 Fedora End Of Life 2018-05-03 08:09:29 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. 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 '26'.

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 26 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 2018-05-29 11:33:49 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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.