FS#76825 - [xorg-server-xephyr] Segfault

Attached to Project: Arch Linux
Opened by Radu Potop (wooptoo) - Wednesday, 14 December 2022, 12:00 GMT
Last edited by Toolybird (Toolybird) - Thursday, 15 December 2022, 20:18 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

I get a segfault when trying to run the latest version of Xorg Xephyr (xorg-server-xephyr).


Additional info:

Packages:

Name : xorg-server-xephyr
Version : 21.1.5-1

Name : xorg-server
Version : 21.1.5-1

Kernel:
Linux optiplex 6.1.0-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 11 Dec 2022 23:35:00 +0000 x86_64 GNU/Linux

I don't use any special Xorg config. This is an integrated Intel GPU running with the KMS driver:
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-S GT1 [UHD Graphics 770] (rev 0c)

The hardware is a standard Dell Optiplex 7000 Micro form factor. `cat /proc/cpuinfo`:
model name : 12th Gen Intel(R) Core(TM) i5-12500T
microcode : 0x26

An older version of Xephyr worked just fine. I last tested maybe a month ago or so.


Steps to reproduce:

❯ Xephyr -br -ac -noreset -screen 2560x1440 :9

(EE)
(EE) Backtrace:
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 0: Xephyr (?+0x0) [0x55fefba81e44]
(EE) 1: /usr/lib/libc.so.6 (__sigaction+0x50) [0x7ffad6d29a00]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 2: /lib64/ld-linux-x86-64.so.2 (?+0x0) [0x7ffad763c03d]
(EE) 3: /usr/lib/libc.so.6 (_dl_catch_exception+0x7e) [0x7ffad6e40e3e]
(EE) 4: /usr/lib/libc.so.6 (_dl_catch_error+0x33) [0x7ffad6e40ef3]
(EE) 5: /usr/lib/libc.so.6 (dlerror+0x29f) [0x7ffad6d734af]
(EE) 6: /usr/lib/libc.so.6 (dlclose+0x36) [0x7ffad6d73206]
(EE) 7: /usr/lib/dri/swrast_dri.so (nouveau_drm_screen_create+0x1dc8bc) [0x7ffad451ef4c]
(EE) 8: /usr/lib/dri/swrast_dri.so (nouveau_drm_screen_create+0x1dbac9) [0x7ffad451e159]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 9: /usr/lib/dri/swrast_dri.so (?+0x0) [0x7ffad3aa8324]
(EE) 10: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x62914a) [0x7ffad40d163a]
(EE) 11: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x62909a) [0x7ffad40d158a]
(EE) 12: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0x72b) [0x7ffad3aa8c1b]
(EE) 13: /usr/lib/dri/swrast_dri.so (__driDriverGetExtensions_d3d12+0xa46f) [0x7ffad3ab295f]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 14: Xephyr (?+0x0) [0x55fefba98785]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 15: Xephyr (?+0x0) [0x55fefba97a07]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 16: Xephyr (?+0x0) [0x55fefb9ddc1c]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 17: Xephyr (?+0x0) [0x55fefbabb111]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 18: Xephyr (?+0x0) [0x55fefb9dfa92]
(EE) 19: /usr/lib/libc.so.6 (__libc_init_first+0x90) [0x7ffad6d14290]
(EE) 20: /usr/lib/libc.so.6 (__libc_start_main+0x8a) [0x7ffad6d1434a]
(EE) unw_get_proc_name failed: no unwind info found [-10]
(EE) 21: Xephyr (?+0x0) [0x55fefb95f915]
(EE)
(EE) Segmentation fault at address 0x337
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
fish: Job 1, 'Xephyr -br -ac -noreset -screen…' terminated by signal SIGABRT (Abort)
This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 15 December 2022, 20:18 GMT
Reason for closing:  Fixed
Additional comments about closing:  mesa 22.3.1-1
Comment by Toolybird (Toolybird) - Thursday, 15 December 2022, 07:34 GMT
Cannot repro in a fresh VM. Could you please provide a proper backtrace with symbols [1]? These days it should be as simple as having gdb installed and:

$ coredumpctl gdb

then answer Y to download the symbols. Once you have the trace, it might then need to be reported upstream.

[1] https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment by Radu Potop (wooptoo) - Thursday, 15 December 2022, 10:08 GMT
Thanks for getting back to me. So I think I got extra lucky.
I upgraded to the latest mesa 22.3.1 packages from testing/ and the issue has now fixed itself:

upgraded xz (5.2.10-1 -> 5.4.0-1)
upgraded openssl (3.0.7-2 -> 3.0.7-4)
upgraded apr-util (1.6.1-10 -> 1.6.1-11)
upgraded db (5.3.28-5 -> 6.2.32-1)
upgraded iproute2 (6.0.0-1 -> 6.1.0-3)
installed db5.3 (5.3.28-2)
upgraded jack2 (1.9.21-1 -> 1.9.21-3)
upgraded libva-mesa-driver (22.3.0-1 -> 22.3.1-1)
upgraded logrotate (3.20.1-1 -> 3.21.0-2)
upgraded mesa (22.3.0-1 -> 22.3.1-1)
upgraded mesa-vdpau (22.3.0-1 -> 22.3.1-1)
upgraded opencl-mesa (22.3.0-1 -> 22.3.1-1)
upgraded openssl-1.1 (1.1.1.s-2 -> 1.1.1.s-4)
upgraded perl (5.36.0-1 -> 5.36.0-3)
upgraded vulkan-intel (22.3.0-1 -> 22.3.1-1)

The issue might've been mesa 22.3.0 (also previously installed from testing).

Loading...