Bug#1102031: xwayland: Xwayland Crash on First X Client
On 2025-04-04 03:29, Leo L. Schwab wrote:
>
> (gdb) bt
> #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at ./nptl/pthread_kill.c:44
> #1 0x00007f387f36f9ff in __pthread_kill_internal (threadid=<optimized out>, signo=6) at ./nptl/pthread_kill.c:89
> #2 0x00007f387f31acc2 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
> #3 0x00007f387f3034ac in __GI_abort () at ./stdlib/abort.c:73
> #4 0x0000560fbd3301c0 in ?? ()
> #5 0x0000560fbd3349b9 in ?? ()
> #6 0x0000560fbd335ab9 in ?? ()
> #7 0x0000560fbd32d2a9 in ?? ()
> #8 <signal handler called>
> #9 0x00007f387ebe04c0 in ?? () from /lib/x86_64-linux-gnu/libnvidia-tls.so.535.216.03
> #10 0x00007f3878a4124c in give_pwd_free (pwd=pwd@entry=0x7ffcd98a55f0) at nss_compat/compat-pwd.c:106
Looks like the original signal is raised in libnvidia-tls.so. Xwayland's signal handler then calls abort() to terminate the process.
Looks like you need to report this to Nvidia.
--
Earthling Michel Dänzer \ GNOME / Xwayland / Mesa developer
https://redhat.com \ Libre software enthusiast
Reply to: