Package Details: zoom 6.2.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: 670
Popularity: 6.81
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2024-11-25 17:39 (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 .. 60 61 62 63 64 65 66 67 68 69 70 .. 78 Next › Last »

projectgus commented on 2019-12-11 09:19 (UTC)

Is anyone else having problems with the X11 session freezing on latest Zoom (3.5.330166.1202-1)? I find after a few minutes on a video call, the entire X session including the mouse cursor stops responding. Parts of the display update once every 2-3 minutes, some parts never update. It never seems to recover. Haven't seen this in any other circumstances.

Have rolled back to 3.0.317369.1110-1 which is fine so far.

Haven't bothered reporting to Zoom yet as it might be some unique quirk of my X11/hardware/desktop setup, but thought I'd ask if anyone else was seeing it.

diogobaeder commented on 2019-11-25 14:39 (UTC) (edited on 2019-11-25 14:41 (UTC) by diogobaeder)

I'm getting errors trying to run zoom after upgrading my system this weekend (I upgrade every weekend), seems to be some incompatibility with the currently installed Qt version I guess (unfortunately the log file it referenced in the output doesn't exist, so I don't have more info):

https://pastebin.com/TLH7K44j

jago commented on 2019-11-14 15:33 (UTC) (edited on 2019-11-14 15:37 (UTC) by jago)

$ /opt/zoom/zoom zoom started. Client: Breakpad is using Single Client Mode! client fd = -1 QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled /opt/zoom/zoom: symbol lookup error: /opt/zoom/imageformats/libqsvg.so: undefined symbol: _ZdlPvm, version Qt_5

the_10 commented on 2019-11-02 15:39 (UTC)

google auth is working again for me, thanks a lot for updating

the_10 commented on 2019-10-23 14:20 (UTC)

looks like the package is hardlinked to qt5.9.6 which causes the issues when trying to authenticate with for example google. kde-open5 seems torequire the libs to be the same version as the systems qt packages (5.13 in my case)

jpulec commented on 2019-10-10 16:28 (UTC)

@jsravn At least google login appears to be completely busted in 3.0.3X. Downgrading to 3.0.291715.0908-1 fixed it for me.

jsravn commented on 2019-10-08 19:22 (UTC)

Anyone else having difficulties logging in after upgrading from 2.x to 3.x? Any tips?

edh commented on 2019-09-19 19:40 (UTC)

@flops

The default configuration seems absolutely reasonable to me and considering that this is what upstream does, I would for now like to stick to it.

Note that there is no need to introduce hooks or any additional configuration on your side though! Just delete the content of the file and as it is a backup file pacman will not overwrite it on a system update. You may however not delete the file completely.

flops commented on 2019-09-19 18:19 (UTC) (edited on 2019-09-19 18:23 (UTC) by flops)

@edh I agree with you that if you install it. In my case it was just a nasty surprise when i installed this package and got global /etc/asound.conf from nowhere as dependency. I'm just not sure that this is right to deliver pulseadio configuration with conference app. It's not a big deal for me, cause if i will reinstall it i've just added a hook that delete this file in my system. It is just a feature request.

edh commented on 2019-09-19 17:22 (UTC)

@flops

I am struggling to really understand you problem. The package pulseaudio-alsa properly declares /etc/asound.conf, its only file, as backup file and hence will not be overridden by a system update. Further, no package in any officially supported repository contains /etc/asound.conf. Hence, there should be no conflict if you just change the configuration in said file to your needs.

« First ‹ Previous 1 .. 60 61 62 63 64 65 66 67 68 69 70 .. 78 Next › Last »