| 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: | 7.69 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2025-05-21 02:34 (UTC) |
Recreated the zoom package, reused the filename from the PKGBUILD file. Stripped the shared libraries from the package. Then used ldd to figure out what was missing. Had to add qt designer for it to start after that.
Result is a 20mb package that uses the system libraries, rather than a ~260mb package.
Seems a lot quicker, and more secure.
Binary is still 50mb, with a 2010 version of zlib statically compiled in :(
Hi,
For some reason my USB Blue Yeti microphone is recognized by zoom as an audio input option, but it's not actually picking up any sound.
In discord, audacity, and all other programs it seems to be recognized and work fine, but for some reason zoom is having issues.
In pavucontrol, the microphone is showing that it's picking up sound and it's set as the default/fallback input device.
Anyone else having a similar issue?
@edh That would be an acceptable outcome. I'll go post about it in apulse's comments, I guess.
@ypoluektovich Considering that apulse is a pulseaudio emulator for ALSA, I suppose it makes more sense to let apulse provide pulseaudio-also instead of changing every package that depends on the latter.
Please add an option to not install pulseaudio-alsa - it can be replaced with apulse.
@electricprism The vulnerability you are talking about is in the preinstall script of the macOS installer (see here for an in-depth analysis). This PKGBUILD is therefore immune to this particular form of privilege escalation. Nevertheless the Linux version of Zoom is still vulnerable to all other flaws that have been detected recently, such as information leak of email addresses, unauthorized sharing of personal data with Facebook, or the fake end-to-end encryption. However, running Zoom in flatpak or another container solution will not protect you from these vulnerabilities because they are either conceptual or server-side flaws. The only way to mitigate these is to not use Zoom.
Due to backdoor root access on MacOS I suggest others consider using a flatpak or other containerized version of this:
"The application is installed without the user giving his final consent and a highly misleading prompt is used to gain root privileges. The same tricks that are being used by macOS malware."
@hmenke Thanks a lot for the input! I will add those dependencies with the next release.
I just set up Zoom in a systemd-nspawn container and discovered the following missing dependencies:
libxcursor: Zoom will just refuse to start with
error while loading shared libraries: libXcursor.so.1: cannot open shared object file: No such file or directory
libxkbcommon-x11: Without this, keyboard input will just be ignored. There is a little hint in the log:
Qt: Failed to create XKB context!
ttf-dejavu: Without this, Zoom just won't show any fonts. A different font would probably do as well, so depending on the ttf-font metapackage might be sufficient.
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)