Bug 1775929 - [abrt] xorg-x11-server-Xwayland: OsLookupColor(): Display server crashed
Summary: [abrt] xorg-x11-server-Xwayland: OsLookupColor(): Display server crashed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-server
Version: 32
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: X/OpenGL Maintenance List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:232fa296257d0af4bc797ecc47a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-23 17:43 UTC by Mikhail
Modified: 2021-05-25 15:11 UTC (History)
12 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2021-05-25 15:11:56 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: cpuinfo (2.38 KB, text/plain)
2019-11-23 17:43 UTC, Mikhail
no flags Details
File: dmesg (237.28 KB, text/plain)
2019-11-23 17:43 UTC, Mikhail
no flags Details
File: etc_X11_xorg_conf_d.tar.gz (405 bytes, application/octet-stream)
2019-11-23 17:43 UTC, Mikhail
no flags Details
File: usr_share_xorg_conf_d.tar.gz (2.21 KB, application/octet-stream)
2019-11-23 17:43 UTC, Mikhail
no flags Details
reproducer: image with eog (106.50 KB, image/png)
2020-02-25 16:22 UTC, Martin Pitt
no flags Details

Description Mikhail 2019-11-23 17:43:17 UTC
Version-Release number of selected component:
xorg-x11-server-Xwayland-1.20.5-9.fc32

Additional info:
reporter:       libreport-2.11.3
backtrace:      0: /usr/bin/Xwayland (OsLookupColor+0x13c) [0x561ab2ca45fc]
crash_function: OsLookupColor
dso_list:       /usr/bin/Xwayland xorg-x11-server-Xwayland-1.20.5-9.fc32.x86_64 (Fedora Project) 1572987665
executable:     /usr/bin/Xwayland
kernel:         5.4.0-0.rc8.git0.2.fc32.x86_64
runlevel:       N 5
type:           xorg
uid:            0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13c) [0x561ab2ca45fc]

Potential duplicate: bug 1669840

Comment 1 Mikhail 2019-11-23 17:43:18 UTC
Created attachment 1639028 [details]
File: cpuinfo

Comment 2 Mikhail 2019-11-23 17:43:21 UTC
Created attachment 1639029 [details]
File: dmesg

Comment 3 Mikhail 2019-11-23 17:43:22 UTC
Created attachment 1639030 [details]
File: etc_X11_xorg_conf_d.tar.gz

Comment 4 Mikhail 2019-11-23 17:43:24 UTC
Created attachment 1639031 [details]
File: usr_share_xorg_conf_d.tar.gz

Comment 5 Ben Cotton 2020-02-11 17:44:52 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 6 Martin Pitt 2020-02-25 16:06:33 UTC
I updated to Fedora 32 today, and get this all the time now, but not with Xwayland, but classic Xorg. Xorg.0.log says

[    88.542] (II) intel(0): Modeline "1366x768"x0.0   75.20  1366 1414 1478 1582  768 772 779 792 +hsync -vsync (47.5 kHz eP)
[  3941.198] (EE) 
[  3941.198] (EE) Backtrace:
[  3941.200] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x13c) [0x55662d14df9c]
[  3941.201] (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x60) [0x7f162147caef]
[  3941.202] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3941.202] (EE) 2: /usr/lib64/xorg/modules/drivers/intel_drv.so (?+0x0) [0x7f16209b9990]
[  3941.202] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3941.202] (EE) 3: /usr/lib64/xorg/modules/drivers/intel_drv.so (?+0x0) [0x7f16209eb6f0]
[  3941.202] (EE) unw_get_proc_name failed: no unwind info found [-10]
[  3941.202] (EE) 4: /usr/lib64/xorg/modules/drivers/intel_drv.so (?+0x0) [0x7f1620a0b7f0]
[  3941.202] (EE) 5: /usr/libexec/Xorg (BlockHandler+0x40) [0x55662cff3800]
[  3941.202] (EE) 6: /usr/libexec/Xorg (WaitForSomething+0x122) [0x55662d147752]
[  3941.203] (EE) 7: /usr/libexec/Xorg (SendErrorToClient+0x117) [0x55662cfeeba7]
[  3941.203] (EE) 8: /usr/libexec/Xorg (InitFonts+0x3b4) [0x55662cff2e94]
[  3941.205] (EE) 9: /lib64/libc.so.6 (__libc_start_main+0xf2) [0x7f16212c5042]
[  3941.205] (EE) 10: /usr/libexec/Xorg (_start+0x2e) [0x55662cfdc88e]
[  3941.205] (EE) 
[  3941.205] (EE) Segmentation fault at address 0x0
[  3941.205] (EE) 
Fatal server error:
[  3941.205] (EE) Caught signal 11 (Segmentation fault). Server aborting


journal says:

Process 987 (Xorg) of user 0 dumped core.

Stack trace of thread 987:
#0  0x00007f16212daa35 raise (libc.so.6 + 0x3ca35)
#1  0x00007f16212c3895 abort (libc.so.6 + 0x25895)
#2  0x000055662d150bb0 OsAbort (Xorg + 0x1bebb0)
#3  0x000055662d155fa9 AbortServer (Xorg + 0x1c3fa9)
#4  0x000055662d156e0a FatalError (Xorg + 0x1c4e0a)
#5  0x000055662d14def9 OsSigHandler (Xorg + 0x1bbef9)
#6  0x00007f162147ca90 __restore_rt (libpthread.so.0 + 0x14a90)
#7  0x00007f16209b9a24 kgem_retire__buffers (intel_drv.so + 0x24a24)
#8  0x00007f16209eb717 sna_accel_block (intel_drv.so + 0x56717)
#9  0x00007f1620a0b867 sna_block_handler (intel_drv.so + 0x76867)
#10 0x000055662cff3800 BlockHandler (Xorg + 0x61800)
#11 0x000055662d147752 WaitForSomething (Xorg + 0x1b5752)
#12 0x000055662cfeeb47 Dispatch (Xorg + 0x5cb47)
#13 0x000055662cff2e54 dix_main (Xorg + 0x60e54)
#14 0x00007f16212c5042 __libc_start_main (libc.so.6 + 0x27042)
#15 0x000055662cfdc88e _start (Xorg + 0x4a88e)

Comment 7 Martin Pitt 2020-02-25 16:22:22 UTC
Created attachment 1665694 [details]
reproducer: image with eog

I now got two crashes in a row when I try to look at this image with eog:

  eog TestApplication-testBasicUser-fedora-31-127.0.0.2-2201-FAIL.png

When I look at it in firefox, it works.

Another crash earlier today happened when I tried to join a BlueJeans session in Firefox, and yet another one was completely random.

Comment 8 Martin Pitt 2020-03-14 10:54:39 UTC
For the record, this still happens with today's packages, with exact same reproducer as above.

Comment 9 Alexei Podtelezhnikov 2020-04-10 03:45:54 UTC
Please change component to xorg-x11-drv-intel, or better yet, close as a duplicate of bug 1808767, which has more information.

Comment 10 Adam Williamson 2020-04-10 07:01:53 UTC
Please don't. These may well not be the same bug.

X, when it crashes, very commonly crashes in OsLookupColor. That alone does not mean two bugs with that symptom in common are the same; it's just an artefact of how X works. Just google "OsLookupColor" and you will find a whole array of quite different bugs.

Martin's may well not be the same as Mikhail's, and Mikhail's is almost certainly not the same as Alexei's; Mikhail's system does not have an Intel graphics adapter at all, it has an AMD one.

I've found that at minimum we need to see the journals from around the time of the crash to start figuring out the issue.

Comment 11 Adam Williamson 2020-04-10 07:09:52 UTC
Looking at the Xorg backtrace and the symptoms, I guess *Martin's* issue may well be the same as the one Alexei is looking into. But I don't think Mikhail's is.

Comment 12 Olivier Fourdan 2020-04-10 07:20:32 UTC
(In reply to Adam Williamson from comment #11)
> Looking at the Xorg backtrace and the symptoms, I guess *Martin's* issue may
> well be the same as the one Alexei is looking into. But I don't think
> Mikhail's is.

Original report is about Xwayland, whereas comment 6 is from Xorg and points toward the intel DDX indeed.

FTR, Xwayland does not load not nor use any Xorg DDX so these aren't the same issue.

Comment 13 Martin Pitt 2020-04-13 06:43:59 UTC
Indeed, I just confirmed that my crash is bug 1808767. I installed the Intel driver from https://bodhi.fedoraproject.org/updates/FEDORA-2020-81d6a5b194 and +1'ed it. Thanks for pointing out!

Comment 14 Fedora Program Management 2021-04-29 16:00:16 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
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 '32'.

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 32 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 15 Ben Cotton 2021-05-25 15:11:56 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 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.