Package Details: zoom 6.4.3-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: 683
Popularity: 7.83
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2025-04-01 01:55 (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

1 2 3 4 5 6 .. 82 Next › Last »

edh commented on 2025-03-31 13:27 (UTC)

@sbrl Please alert the zoom team.

sbrl commented on 2025-03-31 12:55 (UTC)

Potential security issue: the following files this package builds are marked as executable on install when they probably shouldn't be:

opt/zoom/ring.pcm
opt/zoom/ringtone/ring.pcm
opt/zoom/sip/dtmf_dial.wav
opt/zoom/timezones/ko/timezones.txt

Package zoom-6.4.1-1-x86_64.pkg.tar.zst, uname -a Linux DEVICE_NAME 6.12.18-1-lts #1 SMP PREEMPT_DYNAMIC Sat, 08 Mar 2025 23:06:20 +0000 x86_64 GNU/Linux

oech3 commented on 2025-03-23 18:27 (UTC) (edited on 2025-03-26 17:07 (UTC) by oech3)

  1. Part of qt5-remoteobjects is bundled in original zoom. It may removable from deps.

  2. (Upstream bug?)ZoomWebviewHost stop with pure wayland setting (xwayland=false in zoomus.conf) even for zoom with native runtime (https://aur.archlinux.org/packages/zoom-system-qt).

edh commented on 2025-03-22 15:33 (UTC)

@oech3

Thanks for the pointer regarding the prepare method. I'll drop it with the next release.

AFAIK xdg-desktop-portal-impl is an optional dependency of wayland respectively your display manager not of zoom itself.

oech3 commented on 2025-03-22 07:26 (UTC)

optdepends=('xdg-desktop-portal-impl: Portals for screen sharing, etc... for Wayland') may worth to add.

oech3 commented on 2025-03-21 08:22 (UTC) (edited on 2025-03-21 19:47 (UTC) by oech3)

Fixing Icon and StartupWMClass of Zoom.desktop seens no longer needed.

oech3 commented on 2025-03-20 09:59 (UTC) (edited on 2025-03-22 07:28 (UTC) by oech3)

Zoom crush after mic test on test room. Edit:Sorry,it seems standard behavior even for web version for test room.

Q.Why picom,xcompmgr is optdepends for screen sharing instead of supress screen tearing?

Rhinoceros commented on 2025-03-07 00:48 (UTC)

For anyone else still struggling with screen sharing broken in Wayland (again), I tested Zoom on the web browser. Screen sharing in Firefox just doesn't work, and Chromium only lets you share a tab (although I didn't actually test to see if it worked).

Has anyone tried screen sharing on the Flatpak version?

Other than that, the only solution I can see is to use X11.

ChrisLane commented on 2025-02-25 17:15 (UTC)

I'm having the same issue that @sergeG239 mentioned on 2024-12-26.

I have moments where Zoom appears unresponsive while audio still works and then eventually everything returns to normal.

Looking in the logs I see

ZoomWebviewHost[44394]: segfault at 19 ip 00007116b059bdb4 sp 00007116837fb430 error 6 in libcef.so[8d9adb4,7116a9cb7000+b156000] likely on CPU 0 (core 0, socket 0)