Package Details: zoom 7.0.0-1

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
Replaces: zoom-libs, zoom-libs-bin
Submitter: edh
Maintainer: edh (gromit)
Last Packager: edh
Votes: 730
Popularity: 7.47
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2026-03-26 02:00 (UTC)

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:

  • 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.

edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)

I contacted the zoom support on 13th July 2016 and tried to lure them into creating a proper PKGBUILD respectively adopting this one, considering they are providing a package over very none standard ways to the Arch Linux community (downloading via a *foreign* site) and not through the official repo or the AUR. However there was little to no progress so far.

Latest Comments

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 91 Next › Last »

edh commented on 2022-06-07 09:20 (UTC)

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

drybalka commented on 2022-06-07 08:42 (UTC)

@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?

a172 commented on 2022-06-06 20:37 (UTC)

@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.

charm001 commented on 2022-06-06 20:26 (UTC)

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?

drybalka commented on 2022-06-01 08:08 (UTC)

@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? =)

sameer commented on 2022-05-31 22:40 (UTC) (edited on 2022-05-31 22:41 (UTC) by sameer)

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.

darose commented on 2022-05-31 15:08 (UTC)

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

darose commented on 2022-05-31 15:06 (UTC)

@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.

drybalka commented on 2022-05-31 14:59 (UTC)

@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)?

darose commented on 2022-05-31 13:24 (UTC) (edited on 2022-05-31 13:25 (UTC) by darose)

I use zoom with pipewire with no issues, and I've not run into that error with pacmd either. I have the following pipewire packages installed:

gst-plugin-pipewire 1:0.3.51-1
libpipewire02 0.2.7-2
pipewire 1:0.3.51-1
pipewire-alsa 1:0.3.51-1
pipewire-pulse 1:0.3.51-1
wireplumber 0.4.10-3

And the following pulse packages installed:

libpulse 15.0-4
pipewire-pulse 1:0.3.51-1
xfce4-pulseaudio-plugin 0.4.3-2

HTH

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 91 Next › Last »