Crash when host admits me into a room

[ankhmor]

Description
Every time I join a meeting through a web link, after the host lets me in, Zoom crashes

Which Desktop Meeting SDK version?
Linux, AUR 5.9.3-1

To Reproduce(If applicable)
Steps to reproduce the behavior:

1. Click web link
2. Wait for host to let you in
3. Crash

Device (please complete the following information):

• Device: Desktop, custom build.
• OS: Arch linux

Additional context

Exit zoom as another zoom instance is running!
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
zoom exited normally, exit code is 0 .
ZoomLauncher exit.
qt.scenegraph.general: texture atlas dimensions: 512x512
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 2048x1024
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.67 ms
qt.scenegraph.general: texture atlas dimensions: 512x512
qt.scenegraph.general: animation driver switched to timer mode
zoom was exited due to a handled signal: 11
ZoomLauncher exit.

[jcmcnch]

For me, the issue was "Wayland" (https://en.wikipedia.org/wiki/Wayland_(display_server_protocol)) which I accidentally switched to on my login screen (KDE Neon) when I was having another, unrelated issue. I just switched back to "X11" on my login screen and the issue seems to be resolved.

[SPython]

This may be an issue with Wayland as @jcmcnch says - but Wayland has now been a default on both Gnome and KDE desktops for a while now and Zoom folks should have ironed out those bugs.  I have only experienced the same crash recently and now even with the most recent version of Zoom 5.12.2 (4816).  We are using Linux Fedora 36 with KDE Plasma 5.25.5 and Wayland. 

[SPython]

Tried disabling the hardware acceleration etc - that does not resolve the issue.  The problem appears to occur only when the host "admits" the invitee.  If the host does not set a passcode or the requirement to be admitted by the host - the program does not crash when joining the meeting.

[SPython]

I can confirm that this is related to the way Zoom interacts with Wayland.  It does not occur in an X11 session.  Curious, though, that it crashes in Wayland only when the host requires the client to be admitted.