Version-Release number of selected component: xorg-x11-server-Xwayland-1.20.4-1.fc29 Additional info: reporter: libreport-2.10.0 crash_function: OsLookupColor executable: /usr/bin/Xwayland kernel: 5.0.3-200.fc29.x86_64 runlevel: N 5 type: xorg uid: 0 Truncated backtrace: 0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x562ce3de631d] 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f91dc24a07f] 2: /lib64/libc.so.6 (gsignal+0x10f) [0x7f91dc0a953f] 3: /lib64/libc.so.6 (abort+0x127) [0x7f91dc093895] 4: /lib64/libc.so.6 (__assert_fail_base.cold.0+0xf) [0x7f91dc093769] 5: /lib64/libc.so.6 (__assert_fail+0x46) [0x7f91dc0a19f6] 6: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_nouveau_vieux+0x41cbb5) [0x7f91db738675] 7: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_nouveau_vieux+0x41d125) [0x7f91db738c15] 8: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_i915+0x137c8b) [0x7f91dafbf16b] 9: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_i915+0x1381ff) [0x7f91dafbfe9f] 10: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_i915+0x130049) [0x7f91dafaf8d9] 11: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_i915+0x11b04c) [0x7f91daf851cc] 12: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_nouveau_vieux+0x1d17ba) [0x7f91db2a1e0a] 13: /usr/lib64/dri/i965_dri.so (__driDriverGetExtensions_nouveau_vieux+0x1d1b2e) [0x7f91db2a250e] 14: /usr/bin/Xwayland (glamor_create_gc+0xd5e5) [0x562ce3cae8c5] 15: /usr/bin/Xwayland (DamageRegionAppend+0x1a0c) [0x562ce3d5689c] 16: /usr/bin/Xwayland (miPaintWindow+0x24f) [0x562ce3cce83f] 17: /usr/bin/Xwayland (miWindowExposures+0x142) [0x562ce3cce5b2] 18: /usr/bin/Xwayland (miHandleValidateExposures+0x6e) [0x562ce3cdc1ce] 19: /usr/bin/Xwayland (MapWindow+0x159) [0x562ce3ddc309] 20: /usr/bin/Xwayland (ProcBadRequest+0x69b) [0x562ce3daa7db] 21: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x562ce3db035e] 22: /usr/bin/Xwayland (InitFonts+0x3c6) [0x562ce3db4396] 23: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f91dc095413] 24: /usr/bin/Xwayland (_start+0x2e) [0x562ce3c8237e]
Created attachment 1546828 [details] File: backtrace
Created attachment 1546829 [details] File: cpuinfo
Created attachment 1546830 [details] File: dmesg
Created attachment 1546831 [details] File: dso_list
Created attachment 1546832 [details] File: etc_X11_xorg_conf_d.tar.gz
Created attachment 1546833 [details] File: usr_share_xorg_conf_d.tar.gz
Can you please provide the journalctl logs of gnome-shell around the time of the crash?
I think this is https://gitlab.freedesktop.org/xorg/xserver/issues/661 fixed with https://gitlab.freedesktop.org/xorg/xserver/merge_requests/142
Created attachment 1546907 [details] journal around the time of crash
Sorry, that's not what I'm asking for... I am after the content of the journalctl log for gnome-shell around the time of the crash (ie something "journalctl /usr/bin/gnome-shell" around the time of the crash) More precisely, I am looking for a message like "XXX fail to create fbo" because I reckon your crash is the same as the one I fixed upstream.
Created attachment 1546908 [details] Journal log for gnome-shell arround the time of crash I see, but the message you are looking for, is not in there.
Right, not even before the crash? (I mean, the log starts precisely at the exact time of the crash -11:08:23- whereas I would expect the message to show up slightly before that). Anyway, if not the same, then we can't rule out a bug in mesa itself (the abort is caused by an assertion failed in mesa code).
FEDORA-2019-84694484f4 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-84694484f4
xorg-x11-server-1.20.5-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-84694484f4
xorg-x11-server-1.20.5-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.