Package Details: zoom 6.3.11-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: 682
Popularity: 7.64
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2025-03-01 01:53 (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 .. 10 11 12 13 14 15 16 17 18 19 20 .. 81 Next › Last »

robbystk commented on 2024-04-29 18:45 (UTC)

A while ago after an upgrade, zoom started exiting immediately after launch with no output or error message. Today I tried removing the src and pkg directories and rebuilding the package. Running makepkg --cleanbuild will clear the src directory before extraction which might also be sufficient. The newly built package worked after installing, so it seems that there were some old files left in the src directory that were causing problems. I'm posting here in case it helps anyone else with a similar issue.

MajorMayer commented on 2024-04-19 14:59 (UTC)

If i want to open the Zoom desktop app after opening a Zoom link in a browser (Firefox/ Chromium) nothing happens. Is there some additional configuration required?

nursoda commented on 2024-04-15 22:03 (UTC)

I updated to 6.0 and have no issues on wayland, neither with video nor with screen share.

a172 commented on 2024-04-15 18:33 (UTC)

@GaryScottMartin - When I started zoom from the terminal with no previous state, it printed stuff out to the terminal, but not on later launches. That might be a coincidence, but it is worth a shot to see if there is something helpful there. I don't have any other advice, sorry.

For reference, I'm running sway.

GaryScottMartin commented on 2024-04-15 18:25 (UTC) (edited on 2024-04-15 18:26 (UTC) by GaryScottMartin)

@a172 I just installed Zoom this morning and in my ~/,config/zoomus.conf that line was xwayland=true. I am running KDE/Plasma6/Wayland and it won't start at all for me, even after deleting the state. It does work OK in the browser, though.

a172 commented on 2024-04-15 13:16 (UTC) (edited on 2024-04-15 13:19 (UTC) by a172)

A heads up: I upgraded to Zoom 6.0.0 (4563), ahead of the AUR release. First attempts just crashed. I cleared all the local state I could find (~/.zoom/, ~/.cache/zoom/, ~/.config/zoom{,us}.conf), and now zoom will successfully launch, but only in X11/xwayland. I haven't figured out how to get it working natively in Wayland yet (this is a regression). I expect this also breaks screen sharing.

edit: it looks like it was just the xwayland=false in ~/.config/zoomus.conf that was causing issues.

edh commented on 2024-03-08 20:52 (UTC)

@archisman Please raise your concerns regarding the outdated qt dependency upstream.

archisman commented on 2024-03-08 17:24 (UTC)

The package depends explicitly on qt5-webengine and qt5-remoteobjects. Can we change them to the respective qt6 versions instead?

skyefi commented on 2024-02-29 15:38 (UTC)

@nursoda thought it couldn't be a download issue bc I removed and tried again several times, but I was able to download the package a successfully build independent of paru (pkgbuild + pacman), so seems to be either a paru issue or a corrupted package on my end (that was cached so never re-downloaded). Seems like everything is fine with the package - Thanks for the help!

edh commented on 2024-02-29 07:19 (UTC)

@nursoda Yes, I'll switch with the next release.

« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 81 Next › Last »