libQt drivers and libwayland client shared object
I'm mindful of the warning that "Issues with Wayland during day-to-day usage are almost certainly a bug in your compositor and not a bug with in this repository" so my apologies if this falls in that category.
I've been having a lot of trouble with Zoom on Wayland (I run Arch+Sway on a lenovo thinkpad x1 carbon gen 14). Roughly 1/3 times opening Zoom, it crashes early during launch, or when I start a meeting. I pursued this for a long time with the Zoom support, who eventually sent me this message, hence my raising an issue here:
From Zoom support:
I would like to let you know that I have an update from our engineering team and they have asked If you are able to reach out to the support team with libwayland to figure out the crash reported with libwayland-client.so
Furthermore, I would like to share with you the information from the crash dump
Operating system: Linux
0.0.0 Linux 5.17.4-arch1-1 #1 SMP PREEMPT Wed, 20 Apr 2022 18:29:28 +0000 x86_64
CPU: amd64
family 6 model 140 stepping 1
1 CPU
GPU: UNKNOWN
Crash reason: SIGSEGV /SEGV_MAPERR
Crash address: 0x0
Process uptime: not available
Thread 38 (crashed)
0 libwayland-client.so.0.20.0 + 0xa45d
rax = 0x0000000000000000 rdx = 0x0000000000000000
rcx = 0x0000000000000000 rbx = 0x00007f04a404eba0
rsi = 0x0000000000000002 rdi = 0x0000000000000000
rbp = 0x0000000000000000 rsp = 0x00007f04ea0fc3c0
r8 = 0x0000000000000196 r9 = 0x000000000000001e
r10 = 0x00007f058a61ed38 r11 = 0x00007f058a9d85e0
r12 = 0x0000000000000002 r13 = 0x00007f04ea0fc590
r14 = 0x00007f04a4112bc8 r15 = 0x00007f04a4112bf8
rip = 0x00007f05801c645d
Found by: given as instruction pointer in context
1 libQt5WaylandClient.so.5.12.10 + 0x65590
rsp = 0x00007f04ea0fc560 rip = 0x00007f055ac65590
Found by: stack scanning
2 libqt-plugin-wayland-egl.so + 0x88ea
rsp = 0x00007f04ea0fc600 rip = 0x00007f0549c088ea
Found by: stack scanning
3 libQt5Core.so.5.12.10 + 0xa51f6
rsp = 0x00007f04ea0fc660 rip = 0x00007f0588ea51f6
Found by: stack scanning
4 libQt5Gui.so.5.12.10 + 0x1918bc
rsp = 0x00007f04ea0fc740 rip = 0x00007f058a7918bc
Found by: stack scanning
5 libQt5Quick.so.5.12.10 + 0x1ba2ba
rsp = 0x00007f04ea0fc790 rip = 0x00007f058bfba2ba
Found by: stack scanning
6 libQt5Quick.so.5.12.10 + 0x1bd5a2
rsp = 0x00007f04ea0fc7f0 rip = 0x00007f058bfbd5a2
Found by: stack scanning
7 libQt5Core.so.5.12.10 + 0x2cc8ff
rsp = 0x00007f04ea0fc800 rip = 0x00007f05890cc8ff
Found by: stack scanning
8 libQt5Quick.so.5.12.10 + 0x1bd8ac
rsp = 0x00007f04ea0fc840 rip = 0x00007f058bfbd8ac
Found by: stack scanning
9 libQt5Core.so.5.12.10 + 0xa3b97
rsp = 0x00007f04ea0fc850 rip = 0x00007f0588ea3b97
Found by: stack scanning
10 libQt5Core.so.5.12.10 + 0xa6163
rsp = 0x00007f04ea0fc880 rip = 0x00007f0588ea6163
Found by: stack scanning
11 libQt5Core.so.5.12.10 + 0x39b780
rsp = 0x00007f04ea0fc888 rip = 0x00007f058919b780
Found by: stack scanning
12 libc.so.6 + 0x8d5c2
rsp = 0x00007f04ea0fc8e0 rip = 0x00007f0588a5d5c2
Found by: stack scanning
13 libc.so.6 + 0x112584
rsp = 0x00007f04ea0fc980 rip = 0x00007f0588ae2584
Found by: stack scanning
From the stack trace, the crash appears to be related to libQt drivers and libwayland client shared object.