Anyone able to get hardware acceleration working?
Search Criteria
Package Details: zoom 6.3.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: | 680 |
Popularity: | 7.94 |
First Submitted: | 2015-08-15 13:18 (UTC) |
Last Updated: | 2025-02-17 18:45 (UTC) |
Dependencies (31)
- dbus (dbus-gitAUR, dbus-selinuxAUR)
- fontconfig (fontconfig-gitAUR, fontconfig-ubuntuAUR)
- glib2 (glib2-gitAUR, glib2-selinuxAUR, glib2-patched-thumbnailerAUR)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libdrm (libdrm-gitAUR)
- libpulse (pulseaudio-dummyAUR, libpulse-gitAUR)
- libsm
- libx11 (libx11-gitAUR)
- libxcb (libxcb-gitAUR)
- libxcomposite
- libxcursor
- libxfixes
- libxi (libxi-gitAUR)
- libxkbcommon-x11 (libxkbcommon-x11-gitAUR)
- libxrandr (libxrandr-gitAUR)
- libxrender
- libxshmfence
- libxslt (libxslt-gitAUR)
- libxtst
- mesa (mesa-minimal-gitAUR, mesa-wsl2-gitAUR, mesa-amd-bc250AUR, amdonly-gaming-mesa-gitAUR, mesa-gitAUR, mesa-amber)
- Show 11 more dependencies...
Required by (3)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 37 38 39 40 41 42 43 44 45 46 47 .. 81 Next › Last »
internetuser commented on 2021-09-08 06:52 (UTC)
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.
hexhu commented on 2021-09-05 07:46 (UTC) (edited on 2021-09-05 07:48 (UTC) by hexhu)
The versioning seems wrong, should probably be 5.7.6-2 not the current 5.7.6a-1. Breaks pacman upgrade check (see below). On https://zoom.us/download#client_4meeting it shows "Version 5.7.6 (31792.0820)", we should stick to that when packaging. Same format is followed by the latest .PKGINFO: pkgver = 5.7.31792.0820-1
.
:: Searching AUR for updates...
-> zoom: local (5.7.6-1) is newer than AUR (5.7.6a-1)
-> Flagged Out Of Date AUR Packages: zoom
James-T commented on 2021-08-30 09:32 (UTC)
To those commenting on the checksum error.
If you are using yay
then you'll need to remove the zoom
tree in ~/.cache/yay
otherwise it doesn't do the download properly.
edh commented on 2021-08-26 18:46 (UTC)
@daniel_shub Well, I am still to blame. I should have checked that in advance. Right, I will do that next time as well.
P.S. thank you for answering @daniel_shub questions.
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)