AUR (en) - zoom

Search Criteria

Enter search criteria

Search by

Keywords

Out of Date

Sort by

Sort order

Per page

Package Details: zoom 6.4.10-1

Package Actions

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)

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 .. 39 40 41 42 43 44 45 46 47 48 49 .. 84 Next › Last »

darose commented on 2021-09-21 18:26 (UTC)

@edh At your suggestion I went back and read old comments about the versioning. But I still don't understand what the issue is here.

I am currently running zoom 5.7.6 (31753.0818). Current build is 31792.0820. Would it not be possible to change the versioning scheme you're using to change the version number from 5.7.6 to 5.7.6.31753.0818? Then an update to the new build version of 5.7.6.31792.0820 would force an upgrade. Instead I see this:

warning: zoom: local (5.7.6-1) is newer than chaotic-aur (5.7.6a-1)

What am I missing here? Why would that not work?

nursoda commented on 2021-09-20 09:39 (UTC) (edited on 2021-09-20 09:45 (UTC) by nursoda)

Sorry for setting the "outdated" flag. I only now read all the discussion :( For reference in case someone stumbles upon this: Uninstalling zoom (5.7.6) and reinstalling zoom (to 5.7.6a) gives you the latest version.

edh commented on 2021-09-13 15:44 (UTC)

@dack Thank you for you comment. I am aware of the problem. Please read the previous comments. This issue has been extensively discussed. Touching pkgrel is the wrong thing to do here in my opinion.

dack commented on 2021-09-13 15:40 (UTC)

@edh Appending "a" to the version is a bit of a problem - it results in the wrong version ordering. For example, 1.0.0a is considered earlier than 1.0.0 (you can see this in man vercmp). For AUR helpers like yay, this will cause them to see the "new" version as a downgrade and not upgrade them. I think a better workaround would be to just bump pkgrel. That way it's treated as a newer package, and the upstream version number is kept as-is.

je-vv commented on 2021-09-10 17:44 (UTC)

@pinter3, have you tried combinations with pulseaudio-alsa and without it? That might help... Also combining setting and not setting the audio type with those other combinations... With pulseaudio-alsa, no matter your app uses alsa backend, it'll be proxied to pulseaudio. Zoom does work great without pulse, when you do not have pulse at all in your system. Actually I don't use pulse at all, only plain alsa, neither I have ever configured the audio type, and I never had issues with mute/unmute, neither audio in general, but if you use pulse, the best should be for apps to use their pulseaudio backends if available, I'd guess... As an alterantive to plain alsa, and pulse, have you tried using pipewire instead? Perhaps with pipewire-pulse and pipewire-alsa, or a combination of them? The other thing you might try is dropping pulseaudio/pipewire at all, while you figure out the pulseaudio mess with zoom. Zoom is proprietary, so perhaps getting help from them, or a zoom hosted forum might also help get some answers. Proprietary apps are really annoying. I only use zoom given I have no choice at work, :(

pintert3 commented on 2021-09-10 11:40 (UTC)

Ok, so I'm pretty late to bring this up. And from the comments, a few others have had the same (or similar) issue. But I'm going to be more specific and bring it up again, cause the pinned solution doesn't seem to work for me. So ever since some update I think in June/July, when I enter some meetings not hosted by me, (I'm not yet sure what the criteria is exactly, except that it appears whenever I enter a meeting muted, and I'm not the host), I can't unmute myself to speak, so I basically only the chat bar to talk. I use pulseaudio for sound. I tried changing system.audio.type=default to alsa, but no difference after I restarted zoom. I don't know if there's any other fix, I tried waiting for an update, but no difference, and I'm surely now getting desperate. Do I need to change from pulse audio to something else entirely?

internetuser commented on 2021-09-09 20:41 (UTC)

:: Searching AUR for updates... -> zoom: local (5.7.6-1) is newer than AUR (5.7.6a-1)

yay seems to think that 5.7.6a-1 is older than 5.7.6-1

edh commented on 2021-09-09 19:06 (UTC)

@darose Please read the previous comments. This issue has been extensively discussed.

P.s. a quick glance in the PKGBUILD will tell you that such an URL is already in use...

darose commented on 2021-09-09 18:22 (UTC)

When I went to the download page on their web site today (https://us05web.zoom.us/support/down4j) and checked what URL my browser used to do the download, I saw it used the full version number, including build: https://cdn.zoom.us/prod/5.7.31792.0820/zoom_x86_64.tar.xz . Any chance we could use that URL scheme for download going forward in order to avoid the version number issues?