Package Details: zoom 6.3.6-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: LicenseRef-zoom
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 677
Popularity: 7.68
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2025-01-17 02:35 (UTC)

Dependencies (31)

Sources (1)

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 .. 36 37 38 39 40 41 42 43 44 45 46 .. 80 Next › Last »

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?

internetuser commented on 2021-09-08 06:52 (UTC)

Anyone able to get hardware acceleration working?

jonathon commented on 2021-09-07 11:17 (UTC) (edited on 2021-09-07 11:21 (UTC) by jonathon)

Thanks for your patience. I didn't realise they reused the same build number in addition to version number (which is completely ridiculous - why even bother having a build number?).

edh commented on 2021-09-07 11:09 (UTC)

@jonathon As has been outlined a couple of times: This is not possible if upstream does not use unique identifiers. See for example the last commit. The version nor the build changed, the binary file though did change.

Now, there are only two options: I force an upgrade for every user by artificially changing the version to 5.7.6.a. This would require users who have already updated to reinstall the package without an actual need. The second option is to just wait and endure the current state of affairs until a new release is made. As of now, I am sticking to the second option.

jonathon commented on 2021-09-07 11:03 (UTC) (edited on 2021-09-07 11:16 (UTC) by jonathon)

Is there a reason not to include the build number at the end of the pkgver? e.g. 

_rel=5.7
_sub=6
_build=31792.0820
pkgver=$_rel.$_sub.$_build
...
source=("${pkgname}-${pkgver}_orig_x86_64.pkg.tar.xz"::"https://zoom.us/client/$_rel.$_build/zoom_x86_64.pkg.tar.xz")

This should help avoid all future issues with different builds of the same subversion?

alerque commented on 2021-09-05 08:38 (UTC)

@hexhu, @mnussbaum, and others commenting on the versioning issue. This has been covered at length in previous comments but it cannot be corrected until the next release upstream. Zoom release the same version twice with a silent update using the same version. No, using pkgrel to indicate this would not have been correct. The use of a to indicate this was correct and standard procedure. The only mistake was that it should have been separated from the version as its own segment .a so that it didn't get sorted incorrectly as an alpha version indicator. The maintainer has already indicated they will get that right next time, but it isn't possible to fix this time without introducing an obnoxious epoch version that will never go away.

« First ‹ Previous 1 .. 36 37 38 39 40 41 42 43 44 45 46 .. 80 Next › Last »