Arch Linux User Repository

@Rhinoceros - I finally got screen sharing to work under KDE with Wayland. Looks like I'm using the same versions as you:

• Zoom 6.2.10
• pipewire 1.2.6

I followed the Screen share section on the Zoom wiki page:

https://wiki.archlinux.org/title/Zoom_Meetings

The only thing I didn't need to do was set XDG_CURRENT_DESKTOP=gnome. I followed the other steps, and now I can choose my desktop/window to share. Prior to following the wiki I couldn't stop screen sharing without the hanging issue, which I was experiencing prior to 6.2.10.

Has anyone figured out how to make zoom forcibly run in x11 if the rest of the session is in wayland or a way to get screen share to work in wayland (and not using OBS camera workaround)?

Using KDE and wayland and I have tried QT_QPA_PLATFORM=xcb though it seemingly makes no difference for me

EDIT: I got it working from terminal but I cannot get it to work by editing the desktop file. (although I guess that gets overwritten if I get a zoom update). From terminal this works: QT_QPA_PLATFORM=xcb XDG_SESSION_TYPE=x11 nohup zoom %U &; disown

EDIT2: apparently it did not work as it seems to work from my side however then people in the meeting reports that the share was just a black screen even though the preview before share on my side was showing correctly.

@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.

Some ~/.config/zoomus.conf updates:

• SSO Login: I don't have qt5-webengine installed, and the ebeddedBrowserForSSOLogin line doesn't exist in my config zoomus.conf. SSO login works just fine (issues with Firefox containers aside).
• Audio: I am using Pipewire via pipewire-pulse. system.audio.type defaulted to alsa for me (or I changed it without realizing it). I probably could have installed pipewire-alsa and fixed my issues, but I set system.autio.type=pulse (a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.

If anyone finds documentation on ~/.config/zoomus.conf, please let us know.

@a172 That is actually a great question because I did not restart sway and solely relied on lsof -d DEL | awk "\$8~/\/usr\/lib/ { print \$NF }" to check for loaded but now deleted libraries. Since none were shown I assumed I had no program using xorg-xwayland and I could avoid exiting sway. However, if I do restart sway, zoom does not work :(

I will add xorg-xwayland to the dependencies list.

@edh - dumb question, but did you exit and restart Sway after uninstalling xorg-wayland? If so, what are your relevant env vars? Something like env | grep -ie wayland -e qt. Here's mine (minus a few irrelevant ones):

CLUTTER_BACKEND=wayland
ECORE_EVAS_ENGINE=wayland-egl
ELM_ENGINE=wayland_egl
MOZ_ENABLE_WAYLAND=1
QT_QPA_PLATFORM=wayland-egl
SDL_VIDEODRIVER=wayland
WAYLAND_DISPLAY=wayland-1
XDG_SESSION_TYPE=wayland

@drybalka,a172 I can uninstall xorg-xwayland and zoom still works for me. I am running sway and use no special configuration for zoom.

@a172 Thank you for the insight! This solved my issue and now Zoom works again. I needed to have xwayland after all (and probably to also set the environment variable QT_QPA_PLATFORM="wayland;xcb") or zoom simply would not start. Maybe it can be added to the dependencies somehow?

@drybalka - even when Zoom is running natively in Wayland, it still need XWayland to start up. I've seen a few other apps with similar behavior. If anyone has insight on how to get native Wayland apps to run without XWayland, I'm all ears.

Was getting a Core Dump when starting Zoom:

zoom[2733] trap int3 ip:62813b9285a5 sp:7e9710e216a0 error:0 in libcef.so
systemd-coredump[3170]: [🡕] Process 3161 (zoom) of user 1000 dumped core.

Zoom Log ( ~/.zoom/logs/zoom_stdout_stderr.log) shows:

FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/zoom/cef/chrome-sandbox is owned by root and has mode 4755. 

I did what it says and Zoom is working again:

chmod 4755 /opt/zoom/cef/chrome-sandbox
chown root:root /opt/zoom/cef/chrome-sandbox

Are there issues with doing what it says?

@sameer Indeed, after symlinking I do not get any relevant error info anymore - zoom just does not start at all with an error "zoom was exited due to a handled signal: 5". Any ideas? =)

does anyone have a positive experience running zoom with pipewire on wayland (sway, in particular)?

@drybalka

Yes -- I am running Sway + Pipewire + Zoom with no issues.

The pacmd not found error is because pipewire-pulse does not provide pacmd but does provide pactl. You can just symlink /usr/bin/pacmd to /usr/bin/pactl to get rid of the warning. This works because pactl is a subset of operations supported in pacmd, and Zoom does not need any options other than those in pactl (AFAIK).

It is not a big deal though, Zoom worked fine for me even if it couldn't find pacmd.