Package Details: zoom 7.0.5-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-05-19 01:50 (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 .. 68 69 70 71 72 73 74 75 76 77 78 .. 91 Next › Last »

jonathanl commented on 2020-03-30 20:15 (UTC)

The zoom app seems to not be re-rendering for me. It seems to be responding to events i.e. clicking on 'sign in', but only re-renders when I open a secondary window (the 'about' window). I am running arch (5.5) using xmonad and LG3D. If anyone has any ideas that would be that would be really helpful!

p.s. when I open zoom from the commandline the only error I see in the output is this, but it seems minor

qt.svg: link image0 hasn't been detected!
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument

edh commented on 2020-03-27 10:09 (UTC)

@natrio Officially it is listed as dependency.

natrio commented on 2020-03-27 09:34 (UTC)

"pulseaudio-alsa" dependency is not nesessary. The Zoom can work with Pulseaudio without ALSA, and it also can work with ALSA without Pulseaudio.

losbehamos commented on 2020-03-26 08:21 (UTC)

@matthias and @bidskii I have to say that after the last update the SSO Login for me stopped working with the embedded browser. The embedded browser shows a randomly generated very long string after submitting my credentials. The only cause why I tried Installing qt5-webengine was that I saw it by running zoom in terminal so I can't share any insights.

@kevinusername thanks disabling the embedded browser for SSO Login did also work for me.

I think we can consider the automatically embedded browser feature as unreliable

matthias commented on 2020-03-25 22:28 (UTC)

@kevinusername: Thank you so much. Works for me now too :-)

ph2545 commented on 2020-03-25 21:49 (UTC)

@kevinusername PERFECT!! That worked for me. Thanks for sharing

kevinusername commented on 2020-03-25 18:41 (UTC)

@matthias @bidskii @ph2545 I was having the same issue with SSO login failing with the 'referrer policy' warning. In my case this turned out to be an issue with the embedded browser zoom was using to open my SSO login.

I was able to resolve this by editing ~/.config/zoomus.conf with the line embeddedBrowserForSSOLogin=false. After restarting zoom, clicking "sign in with SSO" now opened my default browser (Firefox), and I was able to successfully login.

Found the idea from a somewhat similar GitHub issue: https://github.com/NixOS/nixpkgs/issues/69352

je-vv commented on 2020-03-25 18:04 (UTC)

@ph2545, I only use zoom for work (just because IT chose to use zoom), and the only way to login is through sso authentication. It's been working fine since I had to start using zoom. Just a reminder that for sso authentication you need to provide your company's domain 1st...

ph2545 commented on 2020-03-25 17:38 (UTC)

@edh What you say sounds reasonable. However, it worked fine prior the March 23 update. Nevertheless thank you for your contribution.

edh commented on 2020-03-25 17:29 (UTC)

@je-vv Thanks for the explanation. I will add picom to the optdepends array with the next update.

@ph2545 I am not part of the zoom support team and the SSO problem very much does not sound like a packaging problem.

« First ‹ Previous 1 .. 68 69 70 71 72 73 74 75 76 77 78 .. 91 Next › Last »