Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()

Bug #1853266 reported by Michael Freitag on 2019-11-20
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Unknown
xorg-server (Fedora)
Won't Fix
Undecided
xorg-server (Ubuntu)
Undecided
Unassigned

Bug Description

Recently, my the xserver on my system has started randomly crashing due to a segmentation fault. As far as I can tell, this segmentation fault occurs as a result of libglamoregl encountering a GL_OUT_OF_MEMORY error (see attached Xorg.log). I have had a hard time reproducing this bug reliably, but it mostly happens when I have been using Inkscape for a while.

This appears to be the same bug that has been reported here

https://bugs.freedesktop.org/show_bug.cgi?id=110500
https://bugs.freedesktop.org/show_bug.cgi?id=110714

In those bug reports, the usual recommendation is to switch from the -modesetting video driver to the -nouveau video driver. By default, Ubuntu is not configured in this way, so this bug probably needs to be addressed in some other way.

My graphics card is listed as follows:

 *-display
       description: VGA compatible controller
       product: GK208B [GeForce GT 710]
       vendor: NVIDIA Corporation
       physical id: 0
       bus info: pci@0000:65:00.0
       version: a1
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
       configuration: driver=nouveau latency=0
       resources: irq:69 memory:d7000000-d7ffffff memory:c8000000-cfffffff memory:d0000000-d1ffffff ioport:b000(size=128) memory:d8000000-d807ffff

Please let me know if you need any additional information.

More information:

Release of Ubuntu: 19.04

Installed package versions:
xserver-xorg-video-nouveau/disco,now 1:1.0.16-1 amd64 [installed]
xserver-xorg-core/disco,now 2:1.20.4-1ubuntu3 amd64 [installed]
xserver-xorg/disco,now 1:7.7+19ubuntu12 amd64 [installed]
inkscape/disco,now 0.92.4-3 amd64 [installed]

Version-Release number of selected component:
xorg-x11-server-Xwayland-1.20.3-1.fc29

Additional info:
reporter: libreport-2.9.6
crash_function: OsLookupColor
executable: /usr/bin/Xwayland
kernel: 4.18.17-300.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55c99a7191ed]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f89f9d7bfbf]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55c99a5c3f91]
3: /usr/bin/Xwayland (glamor_create_gc+0x70c8) [0x55c99a5d5068]
4: /usr/bin/Xwayland (glamor_create_gc+0x74fc) [0x55c99a5d580c]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b0e) [0x55c99a5d5fae]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b0c) [0x55c99a5d9c0c]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55c99a686f3f]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a02) [0x55c99a5e80e2]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55c99a67c855]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55c99a6e321e]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55c99a6e7246]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f89f9bc7413]
13: /usr/bin/Xwayland (_start+0x2e) [0x55c99a5b535e]

Potential duplicate: bug 1617885

Created attachment 1503848
File: backtrace

Created attachment 1503849
File: cpuinfo

Created attachment 1503850
File: dmesg

Created attachment 1503851
File: dso_list

Created attachment 1503852
File: etc_X11_xorg_conf_d.tar.gz

Created attachment 1503853
File: usr_share_xorg_conf_d.tar.gz

Description of problem:
x11-server crushes from time to time without any obvious reason. I have single monitor.

Version-Release number of selected component:
xorg-x11-server-Xwayland-1.20.3-3.fc29

Additional info:
reporter: libreport-2.9.7
crash_function: OsLookupColor
executable: /usr/bin/Xwayland
kernel: 4.18.16-300.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55ca3afbb26d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7fef6568b07f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55ca3ae66041]
3: /usr/bin/Xwayland (glamor_create_gc+0x70c8) [0x55ca3ae77118]
4: /usr/bin/Xwayland (glamor_create_gc+0x74fc) [0x55ca3ae778bc]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b0e) [0x55ca3ae7805e]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b0c) [0x55ca3ae7bcbc]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55ca3af28fef]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a02) [0x55ca3ae8a192]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55ca3af1e915]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55ca3af852ae]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55ca3af892e6]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7fef654d6413]
13: /usr/bin/Xwayland (_start+0x2e) [0x55ca3ae5735e]

Can you please atthach the journalctl logs for gnome-shell around the time of the crash?

Download full text (10.1 KiB)

(In reply to Olivier Fourdan from comment #8)
> Can you please atthach the journalctl logs for gnome-shell around the time
> of the crash?

Feb 05 14:47:26 work gnome-shell[27447]: The property brightness doesn't seem to be a normal object property of [0x56065eeffbb0 StWidget] or a registered special property
Feb 05 14:47:26 work gnome-shell[27447]: The property vignette_sharpness doesn't seem to be a normal object property of [0x56065eeffbb0 StWidget] or a registered special property
Feb 05 15:04:47 work dbus-daemon[836]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.4506' (uid=1000 pid=27447 comm="/usr/bin/gnome-shell " label="unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023")
Feb 05 15:05:03 work gnome-shell[27447]: The property brightness doesn't seem to be a normal object property of [0x56065db42fd0 StWidget] or a registered special property
Feb 05 15:05:03 work gnome-shell[27447]: The property vignette_sharpness doesn't seem to be a normal object property of [0x56065db42fd0 StWidget] or a registered special property
Feb 05 15:21:49 work gnome-shell[27447]: Connection to xwayland lost
Feb 05 15:21:50 work gnome-shell[5262]: can't read lock file /tmp/.X1024-lock: Permission denied
Feb 05 15:21:50 work dbus-daemon[5230]: [session uid=42 pid=5230] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus-bus.service' requested by ':1.13' (uid=42 pid=5262 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Feb 05 15:21:50 work at-spi-bus-launcher[5328]: dbus-daemon[5334]: Activating service name='org.a11y.atspi.Registry' requested by ':1.0' (uid=42 pid=5262 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Feb 05 15:21:52 work dbus-daemon[836]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.5086' (uid=42 pid=5262 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Feb 05 15:21:52 work dbus-daemon[5230]: [session uid=42 pid=5230] Activating via systemd: service name='org.freedesktop.impl.portal.PermissionStore' unit='xdg-permission-store.service' requested by ':1.11' (uid=42 pid=5262 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Feb 05 15:21:52 work gnome-shell[5262]: g_dir_open_with_errno: assertion 'path != NULL' failed
Feb 05 15:21:52 work gnome-shell[5262]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Feb 05 15:21:52 work gnome-shell[5262]: g_dir_open_with_errno: assertion 'path != NULL' failed
Feb 05 15:21:52 work gnome-shell[5262]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
Feb 05 15:21:52 work dbus-daemon[836]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.5086' (uid=42 pid=5262 comm="/usr/bin/gnome-shell " label="system_u:system_r:xdm_t:s0-s0:c0.c1023")
Feb 05 15:21:52 work polkitd[29780]: Registered Authentication Agent for unix-session:c3 (system bus name :1.5086 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8)
...

Description of problem:
After looking a video on youtube with the chromium-browser, I closed the app. Then I opened claws-mail to read my mails

Version-Release number of selected component:
xorg-x11-server-Xwayland-1.20.3-3.fc29

Additional info:
reporter: libreport-2.10.0
crash_function: OsLookupColor
executable: /usr/bin/Xwayland
kernel: 4.20.10-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55e139a6c26d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f12a70a307f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55e139917041]
3: /usr/bin/Xwayland (glamor_create_gc+0x70c8) [0x55e139928118]
4: /usr/bin/Xwayland (glamor_create_gc+0x74fc) [0x55e1399288bc]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b0e) [0x55e13992905e]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b0c) [0x55e13992ccbc]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55e1399d9fef]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a02) [0x55e13993b192]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55e1399cf915]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55e139a362ae]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55e139a3a2e6]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f12a6eec413]
13: /usr/bin/Xwayland (_start+0x2e) [0x55e13990835e]

Can you check with "coredumpctl" if there's a core available for Xwayland and if by chance there's one, upload it somewhere I could download it?

Description of problem:
Starting Brave Browser

Version-Release number of selected component:
xorg-x11-server-Xwayland-1.20.3-3.fc29

Additional info:
reporter: libreport-2.10.0
crash_function: OsLookupColor
executable: /usr/bin/Xwayland
kernel: 4.20.10-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55689b21426d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7fac75c1b07f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55689b0bf041]
3: /usr/bin/Xwayland (glamor_create_gc+0x70c8) [0x55689b0d0118]
4: /usr/bin/Xwayland (glamor_create_gc+0x74fc) [0x55689b0d08bc]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b0e) [0x55689b0d105e]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b0c) [0x55689b0d4cbc]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55689b181fef]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a02) [0x55689b0e3192]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55689b177915]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55689b1de2ae]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55689b1e22e6]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7fac75a64413]
13: /usr/bin/Xwayland (_start+0x2e) [0x55689b0b035e]

Same thing as comment 11, can you please look for a core file, that would be helpful?

Description of problem:
Mär 01 15:55:14 org.gnome.Shell.desktop[6574]: (WW) glamor: Expect reduced performance.
Mär 01 15:55:14 org.gnome.Shell.desktop[6574]: (WW) glamor: Failed to allocate 1922x1175 FBO due to GL_OUT_OF_MEMORY.
Mär 01 15:53:48 org.gnome.Shell.desktop[6574]: (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage

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: 4.20.13-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x562c2391831d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f4284f8207f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x562c237c3061]
3: /usr/bin/Xwayland (glamor_create_gc+0x70e8) [0x562c237d4178]
4: /usr/bin/Xwayland (glamor_create_gc+0x751c) [0x562c237d491c]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b2e) [0x562c237d50be]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b2c) [0x562c237d8d1c]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x562c2388604f]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a22) [0x562c237e71f2]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x562c2387b955]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x562c238e235e]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x562c238e6396]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f4284dcd413]
13: /usr/bin/Xwayland (_start+0x2e) [0x562c237b437e]

Description of problem:
Starting Oracle Virtualbox v6.04 64bit

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: 4.20.13-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55dae6fdb31d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7fc674b5b07f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55dae6e86061]
3: /usr/bin/Xwayland (glamor_create_gc+0x70e8) [0x55dae6e97178]
4: /usr/bin/Xwayland (glamor_create_gc+0x751c) [0x55dae6e9791c]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b2e) [0x55dae6e980be]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b2c) [0x55dae6e9bd1c]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55dae6f4904f]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a22) [0x55dae6eaa1f2]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55dae6f3e955]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55dae6fa535e]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55dae6fa9396]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7fc6749a4413]
13: /usr/bin/Xwayland (_start+0x2e) [0x55dae6e7737e]

Description of problem:
After using and closing Google-Chrome-Beta, I opened Seamonkey

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: 4.20.13-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x560b11dd231d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f1c2fb8b07f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x560b11c7d061]
3: /usr/bin/Xwayland (glamor_create_gc+0x70e8) [0x560b11c8e178]
4: /usr/bin/Xwayland (glamor_create_gc+0x751c) [0x560b11c8e91c]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b2e) [0x560b11c8f0be]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b2c) [0x560b11c92d1c]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x560b11d4004f]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a22) [0x560b11ca11f2]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x560b11d35955]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x560b11d9c35e]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x560b11da0396]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f1c2f9d4413]
13: /usr/bin/Xwayland (_start+0x2e) [0x560b11c6e37e]

Description of problem:
Opening Gparted

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: 4.20.13-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x55da62a5d31d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f7cfd1c307f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x55da62908061]
3: /usr/bin/Xwayland (glamor_create_gc+0x70e8) [0x55da62919178]
4: /usr/bin/Xwayland (glamor_create_gc+0x751c) [0x55da6291991c]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b2e) [0x55da6291a0be]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b2c) [0x55da6291dd1c]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x55da629cb04f]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a22) [0x55da6292c1f2]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x55da629c0955]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x55da62a2735e]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x55da62a2b396]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f7cfd00c413]
13: /usr/bin/Xwayland (_start+0x2e) [0x55da628f937e]

So I think the key to this problem is in comment 14 (thanks Andreas!)

 (WW) glamor: Expect reduced performance.
 (WW) glamor: Failed to allocate 1922x1175 FBO due to GL_OUT_OF_MEMORY.
 (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage

because:

 - All these crashes occur in glamor_get_pixmap_texture() which is a pretty simple function.
 - Only case where this function can segfault is if `pixmap_priv->fbo` in NULL
 - "Failed to allocate ...x... FBO due to GL_OUT_OF_MEMORY" comes from `_glamor_create_tex()` and is called by `glamor_create_fbo()`

So I reckon this issue is caused by glamor failing to allocate a pixmap FBO because GL_OUT_OF_MEMORY and later trying to access it, and crash.

*But* AFAICS, `glamor_get_pixmap_texture()` is used by Xwayland *only* with EGLStream in `xwl_glamor_eglstream_post_damage()`

Are you all using NVidia closed-source driver?

Description of problem:
After viewing a video on youtube with Google-Chrome Unstable I started Kmahjongg

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: 4.20.13-200.fc29.x86_64
runlevel: N 5
type: xorg
uid: 0

Truncated backtrace:
0: /usr/bin/Xwayland (OsLookupColor+0x13d) [0x561e294e731d]
1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f703f63b07f]
2: /usr/bin/Xwayland (glamor_get_pixmap_texture+0x81) [0x561e29392061]
3: /usr/bin/Xwayland (glamor_create_gc+0x70e8) [0x561e293a3178]
4: /usr/bin/Xwayland (glamor_create_gc+0x751c) [0x561e293a391c]
5: /usr/bin/Xwayland (glamor_create_gc+0x7b2e) [0x561e293a40be]
6: /usr/bin/Xwayland (glamor_create_gc+0x9b2c) [0x561e293a7d1c]
7: /usr/bin/Xwayland (DamageRegionAppend+0x6af) [0x561e2945504f]
8: /usr/bin/Xwayland (glamor_create_gc+0x10a22) [0x561e293b61f2]
9: /usr/bin/Xwayland (AddTraps+0x4275) [0x561e2944a955]
10: /usr/bin/Xwayland (SendErrorToClient+0x35e) [0x561e294b135e]
11: /usr/bin/Xwayland (InitFonts+0x3c6) [0x561e294b5396]
12: /lib64/libc.so.6 (__libc_start_main+0xf3) [0x7f703f484413]
13: /usr/bin/Xwayland (_start+0x2e) [0x561e2938337e]

@Olivier Fourdan

I am on nouveau.

still seeing this 5.0.17-300.fc30.x86_64,:

May 29 15:41:37 ll612-04 systemd[1373]: Started dbus-:1.2-org.freedesktop.portal.IBus@0.service.
May 29 15:41:37 ll612-04 journal[1426]: g_dir_open_with_errno: assertion 'path != NULL' failed
May 29 15:41:37 ll612-04 journal[1426]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed
May 29 15:41:37 ll612-04 journal[1426]: g_dir_open_with_errno: assertion 'path != NULL' failed
May 29 15:41:37 ll612-04 journal[1426]: g_filename_to_utf8: assertion 'opsysstring != NULL' failed

Upstream Git says it's been fixed.

This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-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 '29'.

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 29 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.

Michael Freitag (freitagm) wrote :

Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.

Daniel van Vugt (vanvugt) wrote :

[775834.395] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[775834.395] (WW) glamor: Failed to allocate 5x5 FBO due to GL_OUT_OF_MEMORY.
[775834.395] (WW) glamor: Expect reduced performance.
[776320.877] (EE) glamor0: GL error: GL_OUT_OF_MEMORY in glTexSubImage
[776320.877] (EE)
[776320.877] (EE) Backtrace:
[776320.878] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55fb3d66d889]
[776320.878] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x50) [0x7f1c7b03ef8f]
[776320.878] (EE) 2: /usr/lib/xorg/modules/libglamoregl.so (glamor_get_pixmap_texture+0x7d) [0x7f1c7a61947d]
[776320.879] (EE) 3: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7bc8) [0x7f1c7a62bb28]
[776320.879] (EE) 4: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x7fc8) [0x7f1c7a62c298]
[776320.879] (EE) 5: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0x860e) [0x7f1c7a62ca6e]
[776320.879] (EE) 6: /usr/lib/xorg/modules/libglamoregl.so (glamor_create_gc+0xa656) [0x7f1c7a630766]
[776320.879] (EE) 7: /usr/lib/xorg/Xorg (DamageRegionAppend+0x6af) [0x55fb3d5efaef]
[776320.879] (EE) 8: /usr/lib/xorg/Xorg (AddTraps+0x3440) [0x55fb3d5e6950]
[776320.879] (EE) 9: /usr/lib/xorg/Xorg (SendErrorToClient+0x35e) [0x55fb3d50e9fe]
[776320.879] (EE) 10: /usr/lib/xorg/Xorg (InitFonts+0x3b6) [0x55fb3d5129c6]
[776320.880] (EE) 11: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xeb) [0x7f1c7ae64b6b]
[776320.880] (EE) 12: /usr/lib/xorg/Xorg (_start+0x2a) [0x55fb3d4fc67a]
[776320.880] (EE)
[776320.880] (EE) Segmentation fault at address 0x0
[776320.880] (EE)
Fatal server error:
[776320.880] (EE) Caught signal 11 (Segmentation fault). Server aborting

affects: xorg (Ubuntu) → xorg-server (Ubuntu)
tags: added: disco
Changed in xorg-server (Fedora):
importance: Unknown → Undecided
status: Unknown → Won't Fix
Changed in xorg-server:
status: Unknown → Fix Released

I recently upgraded to Ubuntu 19.10 and just ran into the exact same issue again. Xorg log attached.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xorg-server (Ubuntu):
status: New → Confirmed
tags: added: focal
summary: - xserver segfaults on GL_OUT_OF_MEMORY in libglamoregl
+ Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from
+ glamor_get_pixmap_texture() from glamor_create_gc()
Bryce Harrington (bryce) wrote :

From the upstream bug report, the failure in OsLookupColor() is just a common point where the system falls over once it's run out of graphics memory. There could be a number of reasons why the memory got exhausted in the first place (e.g. video drivers leaking memory, misc. bugs in GL apps, ...) which would be the root cause of the problem.

(Fwiw, I stumbled across this bug report because I also got a crash in /usr/lib/xorg/Xorg (OsLookupColor+0x13c), but this was with radeon_drv, unrelated to any GL errors. So, likely a different underlying bug than the OP, just that the crash looks similar.)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.