Package Details: zoom 6.3.0-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: 670
Popularity: 5.17
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2024-12-17 15:18 (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 .. 79 Next › Last »

hristov commented on 2024-12-20 08:24 (UTC)

Finally! The sharing is working as expected under wayland. Both desktop and window seems working with latest pipewire packages and doesn't crash after stopping the share. Very good Christmas present I can say.

AloisP commented on 2024-12-20 08:12 (UTC)

I am getting the following error:

curl: (33) HTTP server does not seem to support byte ranges. Cannot resume. ==> ERROR: Failure while downloading https://zoom.us/client/6.3.0.5527/zoom_x86_64.pkg.tar.xz Aborting... -> error downloading sources: /home/…/.cache/yay/zoom context: exit status 1

Any ideas how to update zoom?

kullfar commented on 2024-12-16 15:51 (UTC)

I still have audio problems with all 6.1.X and 6.2.X versions. Output is great, but mic makes choppy sound, other participants can't even understand what I say.

ps.I don't use pulse

Have someone resolve problems with audio?

danko commented on 2024-12-02 18:39 (UTC)

Zoom cannot start due to failure to find symbol.

ZoomLauncher started.
Zoom path is: /opt/zoom
cmd line:
Start subprocess: /opt/zoom/zoom sucessfully,  process pid: 23220
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
                             Class      App      Lib Possible Culprit Flags
                resip::Connection      656      656
                      resip::Data       36       36
                 resip::DnsResult     1080     1080
                   resip::Headers        1        1
          resip::MsgHeaderScanner       40       40
                resip::SipMessage     5224     5224
         resip::TransportSelector      896      896
                     resip::Tuple      128      128
              resip::UdpTransport     1144     1144
          resip::GenericIPAddress       28       28

zoom started.
Client: Breakpad is using Single Client Mode! client fd = -1
loadZoomWebviewHostProcess newPath is /opt/zoom/ZoomWebviewHost
loadZoomWebviewHostProcess libpath is /opt/zoom/Qt/lib:/opt/zoom/cef:/opt/zoom
Start subprocess: /opt/zoom/ZoomWebviewHost sucessfully,  process pid: 23233
Interface wlan0 is a wireless interface
Interface: ipv4 wlan0, IP Address: 192.168.0.219
qt.scenegraph.general: threaded render loop
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.65 ms
/opt/zoom/zoom: symbol lookup error: /opt/zoom/QtQuick/Controls.2/libqtquickcontrols2plugin.so: undefined symbol: _ZN13QQmlDirParserC1Ev, version Qt_5_PRIVATE_API
Something went wrong while running zoom, exit code is 127.
ZoomLauncher exit.

Shalrath commented on 2024-11-30 23:12 (UTC)

As of today, 6.1.11-1 is still the most recent version that runs fine on XOrg. Newer versions start without UI (only visible with pgrep or similar). Once killed, the UI shows up at the next start. The suggested workaround of setting xwayland=false in ~/.config/zoomus.conf does not change this behavior.

fuhry commented on 2024-11-25 15:34 (UTC)

Here's a script I wrote to automatically update PKGBUILD and .SRCINFO using the latest upstream versions:

https://gist.github.com/fuhry/7fc8c799e93fbfecf7616282cfe17b83

For the maintainers, this should make it significantly easier to quickly respond to new upstream versions. Just run the script, commit PKGBUILD and .SRCINFO, and push.

Cyb3rD4d commented on 2024-11-22 15:02 (UTC)

OMG @ElementalWarrior you're right, the version 6.2.10 finally works! But the upgrade has reverted the pipewire mode, I had to re-enabled it in the settings (really annoying).

Now let's hope the Zoom developers won't break it again, or at least not for so long.

ElementalWarrior commented on 2024-11-20 19:11 (UTC) (edited on 2024-11-20 19:12 (UTC) by ElementalWarrior)

@Cyb3rD4d to counter your point.

I am running:

pipewire==1.2.6

sway-git==1.10.r7407.4fe054c-1

zoom=6.2.10-1

And just turned screen share to pipewire, and it worked for me. (after an eternity of it not working).

I do have to have it running xwayland though.

Cyb3rD4d commented on 2024-11-20 13:26 (UTC)

I tried to set the screen capture mode to Pipewire Mode but it does not work for me. I use Sway, the screen sharing works with Firefox and OBS so I think it's still an issue with Zoom.

Rhinoceros commented on 2024-11-20 02:16 (UTC)

Ah brilliant. Thank you @VanClaussen and @erbrecht. I can confirm it's working for me now too. I did some testing on two systems, and I didn't need to modify ~/.config/zoomus.conf, nor set an environment variable. The only change required was setting Screen capture mode on Wayland to Pipewire Mode as per @VanClaussen's comment.

@edh It would be helpful to pin a comment, at least linking to the wiki entry.