| 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: | 669 |
| Popularity: | 7.39 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2024-10-28 11:11 (UTC) |
@flops
The default configuration seems absolutely reasonable to me and considering that this is what upstream does, I would for now like to stick to it.
Note that there is no need to introduce hooks or any additional configuration on your side though! Just delete the content of the file and as it is a backup file pacman will not overwrite it on a system update. You may however not delete the file completely.
@edh
I agree with you that if you install it.
In my case it was just a nasty surprise when i installed this package and got global /etc/asound.conf from nowhere as dependency. I'm just not sure that this is right to deliver pulseadio configuration with conference app. It's not a big deal for me, cause if i will reinstall it i've just added a hook that delete this file in my system. It is just a feature request.
@flops
I am struggling to really understand you problem. The package pulseaudio-alsa properly declares /etc/asound.conf, its only file, as backup file and hence will not be overridden by a system update. Further, no package in any officially supported repository contains /etc/asound.conf. Hence, there should be no conflict if you just change the configuration in said file to your needs.
Hi, could you please change pulseadio-alsa package directly to pulseaudio + alsa-plugins? pulseaduio-alsa is just an asound.conf file. And if you need a custom one and zoom, you doomed to resolve conflicts.
Ditto @Maduvi @reptile, sometimes on sharing screen my whole system will freeze and I'll have to be kicked of the zoom call by someone else. This seems to happen when there are more people >3 on the call and not when there are fewer. I've had this issue since around version 2.4, I downgraded to 2.1 which seems to work better, but I thought it would be fixed by now - apparently not!
I am experiencing the same problem as @reptile:
"when I share the screen, sometimes it goes black, and I can see only the mouse pointer"
It also happens that I can't share a Whiteboard because the window is black as well. So I believe both things could be related. Maybe some Xorg or mesa driver configuration I have overlooked. Is anyone able to share a Whiteboard instance?
EDIT: fixed the issue installing and enabling compton. Now I can see a whiteboard instance and I hope Zoom will work just fine.
Note on Friday there's supposed to be fix: https://www.wired.com/story/zoom-flaw-web-server-fix. Sources about the security issue talk about MAC, not quite sure the issue is only a MAC one though (see all references in https://www.reddit.com/r/security/comments/cb054u/if_you_have_installed_zoom_any_website_can_turn). I agree with @edh, it's an upstream issue, not a package issue.
Just to clarify, this PKGBUILD is fetching the official package provided by zoom and merely modifies the dependency arrays.
Installers beware, this is a binary package and the upstream provider has recently been caught doing some very dodgy things. Use this package at your own risk.
works like a charm thanks!
Pinned Comments
arash-m commented on 2024-09-15 15:56 (UTC)
Tested 6.2.0-1. Sharing works for me, but it still crashes after stopping. The workaround for me is still downgrading pipewire and libpipewire to 1.0.7 before meetings.
a172 commented on 2022-06-13 14:25 (UTC) (edited on 2022-06-13 14:25 (UTC) by a172)
@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.
Some
~/.config/zoomus.confupdates:qt5-webengineinstalled, and theebeddedBrowserForSSOLoginline doesn't exist in my configzoomus.conf. SSO login works just fine (issues with Firefox containers aside).pipewire-pulse.system.audio.typedefaulted toalsafor me (or I changed it without realizing it). I probably could have installedpipewire-alsaand fixed my issues, but I setsystem.autio.type=pulse(a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.If anyone finds documentation on
~/.config/zoomus.conf, please let us know.edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)