Package Details: zoom 5.4.54779.1115-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: custom
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 350
Popularity: 26.77
First Submitted: 2015-08-15 13:18
Last Updated: 2020-11-16 21:09

Dependencies (24)

Required by (1)

Sources (1)

Pinned Comments

hv15 commented on 2020-06-23 10:43

Hi all, for the last 3 months I've been unable to get any sound/microphone in Zoom. I use https://aur.archlinux.org/packages/alibpulse (a differently packaged form of apulse), as an alternative to the full pulseaudio server. Initially (3 months ago) this worked fine, at which point it didn't (I don't know at what version of Zoom this started to fail, haven't checked). Within my logs it was clear that this has something to do with Zoom not being able to find/use pactl (which is part of libpulse, but not part of apulse).

Well, doing some googling I found that Zoom actually supports ALSA (since version 2.0.57232.0713, see https://support.zoom.us/hc/en-us/articles/205759689-New-updates-for-Linux). There is not other documentation about this that I could find, but when I looked into ~/.config/zoomus.conf I saw there is a line with system.audio.type=default. Again no documentation on this, so I played with it and when I set it to system.audio.type=alsa Zoom started using ALSA directly, and now I have working audio/microphone in Zoom! I hope people find this useful :)

EDIT 1: typos

kevinusername commented on 2020-03-25 18:41

@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

edh commented on 2016-08-26 11:03

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

1 2 3 4 5 6 ... Next › Last »

darose commented on 2020-11-30 19:13

Seems to hog a good bit of CPU. I'm not sure if that's just this version, or all versions.

phillipchaffee commented on 2020-11-30 19:08

Is the newest release just completely unusable for anyone else? It technically runs but is insanely slow for me.

Qt.ng commented on 2020-11-26 08:33

Does anyone have an issue that sometime the audio is extremely small when joining a new room or breakout room? I can only fix it by leave the room and comeback, sometime several times.

Nikita790 commented on 2020-11-19 16:28

anyone else have an issue where some meetings get stuck at "Connecting" (if they are in a breakout room this only happens after you are accepted). I found some other person who has this issue on r/zoom but they are on windows

edh commented on 2020-11-17 10:43

@daniell You are at the wrong AUR page for the zoom-system-qt package.

uwinkelvos commented on 2020-10-30 10:56

if you have problems with broken autoscaling, this can be disabled: ~/.config/zoomus.conf: autoScale=false

rgambord commented on 2020-10-27 20:28

@je-vv I use jack2 with alsa-plugin and apulse for programs that don't support jack. I can quit jack2 and zoom will work with alsa directly (although alsa does not support my HDMI out, so I only have mic) but it won't work when jack2 is running.

Eothred commented on 2020-10-13 13:25

Regarding SSO, for me it was Firefox containers blocking me (I think). I did not have the "zoom domain" as "always open in work container", however I had our company SSO login page on that list. So by jumping from a "no container" to my work container during log in, I think the app opening feature failed.

nasci commented on 2020-10-10 08:34

@malexan I normally use picom so I installed xcompmgr but it's no different. When opening the whiteboard picom gives a bunch of warnings and errors, like "flags cleared on a destroyed window" and "failed to query info". Not sure if that's related.

MasterOne commented on 2020-10-09 08:53

@caleb, no that's not it. As said, everything was working just a few days ago, but the system update that was performed yesterday obviously broke something, because reverting to a previous system snapshot using Timeshift solved the issue.