| 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: | 690 |
| Popularity: | 9.24 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2025-05-21 02:34 (UTC) |
@kuzyn: Read this: https://community.zoom.com/t5/Meetings/An-empty-folder-created-in-Ubuntu/m-p/69059
Apparently, when XDG_DOWNLOAD_DIR in $HOME/.config/user-dirs.dirs is set to an "unsafe" directory, Chrome CEF decides to create $HOME/Downloads instead.
Setting XDG_DOWNLOAD_DIR in $HOME/.config/user-dirs.dirs to a directory inside my $HOME directory (e.g. $HOME/downloads) helped, so Zoom is no longer creating the annoying Downloads folder.
Would love to know if someone has found a way to specify the downloads directory, either via zoomus.conf or env var. Default is $USER/Downloads.
PSA, the prebuild package is available at https://build.kilabit.info/aur .
A short heads-up in case you did not receive Zoom's notification:
Zoom's rpm packages are signed with a GPG key. For releases after Nov 02, 2022 the Linux and Docker GPG signature thumbprint will change from "Key fingerprint: 3960 60CA DD8A 7522 0BFC B369 B903 BF18 61A7 C71D" to "Key fingerprint: 59C8 6188 E22A BB19 BD55 4047 7B04 A1B8 DD79 B481".
Their package signing PGP key may be downloaded from https://zoom.us/download?os=linux, direct link to the new key is https://zoom.us/linux/download/pubkey?version=5-12-6
Any idea why there's no blur option and cannot use virtual background without green screen? Do I need to install any package?
It seems to be that https://aur.archlinux.org/zoom.git no longer exist ? Page 404 Error from the web services.
@mattelacchiato
This seems to be irrelevant for the Arch Linux package (dpkg-sig and rpm instructions are not relevant).
@koryu I hope that the maintainers will include this in the install script. Just for completeness, here is the mail from Zoom:
As an admin or owner of an account with users using the Zoom Desktop Client for Linux, we are reaching out to notify you that we will be retiring the current key pair used to sign the Linux client on November 2, 2022. To avoid service interruption, we advise that you ask your users to download and trust the new public key.
Please follow the instructions below to download the new GPG validation key by 11/2/22 to avoid service interruption.
Download package-signing-key.pub from http://click.zoom.us/e/84442/linux-download-pubkey/c4cjlj/3984217233?h=qog9fl3QsdPRA_5sUBqTXu7PMesnrN2t8rMhUyOgfUY Run the following commands based on the package you’re validating //////////////////////////////////////////////////////////////// // deb package validation gpg --import ~/Downloads/package-signing-key.pub // import gpg public key, only do it once dpkg-sig --verify ./zoom.deb
//////////////////////////////////////////////////////////////// // rpm package validation rpm --import ~/Downloadspackage-signing-key.pub // import gpg public key, only do it once rpm -K zoom.rpm
We apologize for any inconvenience this may cause. If you have any questions, please contact our Support Team or reach out to your Customer Success Manager.
I got a notification, that the public key for the Zoom Linux client will change on November 2nd, 2022. Should this package be adjusted to trust the new key? Or does each one have to do it themselves?
Here's a dirty fix for a specific error when attempting to run zoom after installation. If you get the following error, install the chromium package to workaround the issue:
$ zoom
ZoomLauncher started.
Zoom path is: /opt/zoom
cmd line:
Start subprocess: /opt/zoom/zoom sucessfully, proces pid: [something]
Can't load /home/user/.config/zoomus.conf
/opt/zoom/zoom: error while loading shared libraries: libatk-bridge-2.0.so.0: cannot open shared object file: No such file or directory
Something went wrong while running zoom, exit code is 127.
ZoomLauncher exit.
If you get an error just talking about the non-existence of libatk, just intall the atk package.
(How did I figure this out? I googled for issues related to libatk-bridge and found this page that led me to test whether installing the chromium package would fix this.)
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)