Bug 1634460 - [abrt] xorg-x11-server-Xorg: OsLookupColor(): Segmentation fault at address 0x0
Summary: [abrt] xorg-x11-server-Xorg: OsLookupColor(): Segmentation fault at address 0x0
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 28
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d1f478caf4810d269e3853c19e5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-10-01 00:50 UTC by Paul Olson
Modified: 2019-05-28 22:41 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-05-28 22:41:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: Xorg.0.log (5.86 KB, text/plain)
2018-10-01 00:50 UTC, Paul Olson
no flags Details
File: backtrace (1.40 KB, text/plain)
2018-10-01 00:50 UTC, Paul Olson
no flags Details
File: cpuinfo (1.24 KB, text/plain)
2018-10-01 00:50 UTC, Paul Olson
no flags Details
File: dmesg (82.10 KB, text/plain)
2018-10-01 00:50 UTC, Paul Olson
no flags Details
File: dso_list (442 bytes, text/plain)
2018-10-01 00:50 UTC, Paul Olson
no flags Details
File: etc_X11_xorg_conf_d.tar.gz (367 bytes, application/octet-stream)
2018-10-01 00:50 UTC, Paul Olson
no flags Details
File: usr_share_xorg_conf_d.tar.gz (1.92 KB, application/octet-stream)
2018-10-01 00:50 UTC, Paul Olson
no flags Details

Description Paul Olson 2018-10-01 00:50:05 UTC
Description of problem:
Sunday 09/30/2018
This is a recurring problem. Over the past couple of weeks or so it seems to happen within a couple of hours of a reboot. 
When it does occur, it jumps to the login screen. So I have executed the login process and my setup process and then
continued with my work.
I should say at this point that I am using the version of Fedora Core, FC-28, that I installed two or three months ago as I 
remember.
Some of the time, I was using LibreOffice Write to write and edit documents. At other times I was doing other normal 
such as simple browsing and research using Firefox, and I believe on one occasion I was reading my email which I use 
Thunderbird as my email client.
On none of the occasions of a fault to login was I doing anything that required major resources such as building a large 
amount of source code to create a heavy application. In the past few months most of my development work has been 
writing Python 2.7 code for various applications. Almost all were text based, not GUI based with a graphical interface.
Although I am doing study now, I am not an expert at building kernel code or other GNU code for system applications 
and tools. Given that, I can't provide much deeper information at this time.

A suspician that I had when this problem began occurring was the fact that I was using two monitors, both ViewSonic
21.5". The primary monitor is plugged into the HDMI port of a simple 3 port video card (not a game card - it just has fins, 
not a fan). The second monitor was plugged into the VGA port. The third port, a DVI, was not used.
When the failures became fairly frequent I suspected the second monitor plugged into the VGA port was causing the
problem, possibly overloading the card. Although this setup had been working for some time before the failures began.
I disconnected this second monitor, but the failures continued.

I then dug out an older retired disk with FC-25 I believe. This also failed. So that lead me to think the video card was bad.
I had another identical card so I switched. This one failed as well. So now I am stuck.

I hope this information is useful. I also hope it isn't too much.
Thanks,
Paul

Version-Release number of selected component:
xorg-x11-server-Xorg-1.19.6-8.fc28

Additional info:
reporter:       libreport-2.9.5
crash_function: OsLookupColor
executable:     /usr/libexec/Xorg
kernel:         4.18.9-200.fc28.x86_64
runlevel:       N 5
type:           xorg
uid:            0

Truncated backtrace:
0: /usr/libexec/Xorg (OsLookupColor+0x13d) [0x59d5bd]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f6b7fb01fff]
2: /usr/lib64/dri/nouveau_dri.so (__driDriverGetExtensions_virtio_gpu+0xc31e4) [0x7f6b79a958e4]
3: /usr/lib64/dri/nouveau_dri.so (__driDriverGetExtensions_virtio_gpu+0x133e4d) [0x7f6b79b77d3d]
4: /usr/lib64/dri/nouveau_dri.so (__driDriverGetExtensions_virtio_gpu+0x1d43f7) [0x7f6b79cb8b37]
5: /usr/lib64/dri/nouveau_dri.so (__driDriverGetExtensions_virtio_gpu+0x1352df) [0x7f6b79b7a5af]
6: /usr/lib64/dri/nouveau_dri.so (__driDriverGetExtensions_virtio_gpu+0x135596) [0x7f6b79b7af46]
7: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0x10da9) [0x7f6b7b5757c9]
8: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0xd179) [0x7f6b7b56df89]
9: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0xd388) [0x7f6b7b56e558]
10: /usr/lib64/xorg/modules/libglamoregl.so (glamor_create_gc+0xa3a8) [0x7f6b7b568388]
11: /usr/libexec/Xorg (DamageRegionAppend+0x6af) [0x51e7bf]
12: /usr/libexec/Xorg (miCompositeRects+0x229) [0x50b759]
13: /usr/lib64/xorg/modules/libglamoregl.so (glamor_pixmap_exchange_fbos+0x568) [0x7f6b7b56cd18]
14: /usr/libexec/Xorg (AddTraps+0x47d5) [0x517f85]
15: /usr/libexec/Xorg (SendErrorToClient+0x35e) [0x434ece]
16: /usr/libexec/Xorg (InitFonts+0x416) [0x438f66]
17: /lib64/libc.so.6 (__libc_start_main+0xeb) [0x7f6b7f75311b]
18: /usr/libexec/Xorg (_start+0x2a) [0x42290a]

Comment 1 Paul Olson 2018-10-01 00:50:09 UTC
Created attachment 1488794 [details]
File: Xorg.0.log

Comment 2 Paul Olson 2018-10-01 00:50:10 UTC
Created attachment 1488795 [details]
File: backtrace

Comment 3 Paul Olson 2018-10-01 00:50:11 UTC
Created attachment 1488796 [details]
File: cpuinfo

Comment 4 Paul Olson 2018-10-01 00:50:13 UTC
Created attachment 1488797 [details]
File: dmesg

Comment 5 Paul Olson 2018-10-01 00:50:14 UTC
Created attachment 1488798 [details]
File: dso_list

Comment 6 Paul Olson 2018-10-01 00:50:15 UTC
Created attachment 1488799 [details]
File: etc_X11_xorg_conf_d.tar.gz

Comment 7 Paul Olson 2018-10-01 00:50:16 UTC
Created attachment 1488800 [details]
File: usr_share_xorg_conf_d.tar.gz

Comment 8 Ben Cotton 2019-05-02 19:17:23 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 9 Ben Cotton 2019-05-02 20:46:35 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 10 Ben Cotton 2019-05-28 22:41:37 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.