| Git Clone URL: | https://aur.archlinux.org/zoom.git (read-only, click to copy) |
|---|---|
| Package Base: | zoom |
| Description: | Video Conferencing and Web Conferencing Service |
| Upstream URL: | https://zoom.us/ |
| Keywords: | call conference meeting video |
| Licenses: | LicenseRef-zoom |
| Submitter: | edh |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 689 |
| Popularity: | 8.89 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2025-04-22 04:41 (UTC) |
@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.
BTW, when I google "sh: line 1: pacmd: command not found" this is the only link that comes up:
https://forum.garudalinux.org/t/garuda-nvidia-wayland-gnome-and-zoom/19679
Seems like this must be something wayland related.
HTH
@drybalka That's a really odd error by the way. Zoom isn't a shell script:
[darose@titan ~]$ file /usr/bin/zoom
/usr/bin/zoom: symbolic link to /opt/zoom/ZoomLauncher
[darose@titan ~]$ file /opt/zoom/ZoomLauncher
/opt/zoom/ZoomLauncher: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=6ea54f33432041c8c1cfba3bfd1948ca717d398c, stripped
So I'm not even clear what shell script is getting executed that's calling pacmd and failing. I would suggest trying to track that down.
@darose Well, it still doesn't work for me =( I am not sure why this may be important, but I'll specify the question a bit more: does anyone have a positive experience running zoom with pipewire on wayland (sway, in particular)?
Pinned Comments
erbrecht commented on 2024-11-19 13:06 (UTC)
@Rhinoceros - I finally got screen sharing to work under KDE with Wayland. Looks like I'm using the same versions as you:
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.
edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)