Package Details: zoom-system-qt 5.4.53391.1108-3

Git Clone URL: (read-only, click to copy)
Package Base: zoom-system-qt
Description: Video Conferencing and Web Conferencing Service - system Qt libraries
Upstream URL:
Keywords: call conference meeting video
Licenses: custom
Conflicts: zoom
Provides: zoom
Submitter: netcrusher
Maintainer: netcrusher (alerque)
Last Packager: alerque
Votes: 27
Popularity: 0.91
First Submitted: 2020-05-03 20:50
Last Updated: 2020-12-14 20:43

Dependencies (15)

Required by (1)

Sources (1)

Pinned Comments

alerque commented on 2021-02-09 18:04

To flagger @billypilgrim and all curious: I've tested the current upstream release 5.5.7011.0206 and it has the same systemic problem we've seen with everything since 5.4.53391.1108. If anybody finds a way to make it usable know that we're open to fixing this up, we just haven't figured out how to make it work yet.

I'm unflagging again as this is the last known viable release for this method.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 Next › Last »

redapted commented on 2020-06-14 00:37

Edit: Found a bug in Qt, and have some guesses as to how this triggers a bug in Zoom. Will file bugs with each of them. Leaving the below in case this workaround helps anyone else.

I also was having the blank-video problem, but have a (hacky) workaround. Quick info about my environment:

  • Lenovo ThinkPad x1 Carbon, Gen 7 uses uvcvideo
  • Compositor: Sway, have qt5-wayland installed
  • ~/.config/environment.d/envvars.conf contains QT_QPA_PLATFORM=wayland-egl, tried with both XDG_CURRENT_DESKTOP=Unity and XDG_CURRENT_DESKTOP=sway also
  • Ran LD_PRELOAD=/usr/lib/libv4l/ zoom (without success)

Apparently, this laptop's webcam actually has three nodes; /dev/video0, /dev/video1, and /dev/media0. When testing with mpv, only /dev/video0 actually output frames. Maybe Zoom/Qt is defaulting to one of the other nodes for some reason?

The solution that worked was adapted from the wiki: Webcam Setup - Invert the video stream. The only differences were not inverting the video, and using /dev/video2 as the dummy device; ffmpeg -f v4l2 -i /dev/video0 -f v4l2 /dev/video2. After that, I ran Zoom from my launcher (without LD_PRELOAD), selected Dummy video device, and everything worked fine.

This workaround is hardly ideal, this seems very much like an upstream-problem. If this works for other folks, and they want to use it, it might be most-convenient for them to modify their relevant .desktop file to run/fork the above ffmpeg command before Zoom, and kill it after exit. But TBH, I hope someone comes up with a better workaround.

alerque commented on 2020-06-05 10:09

@netcrusher No I haven't! And honestly I'm kind of glad of that, the contents is is so much junk it seemed like security theater to even consider validating archive signatures.

netcrusher commented on 2020-06-05 09:09

@caleb: I had a quick look and as far as I understood, only the RPMs are signed. I tried adding an .asc/.sig suffix to the download path but got 403s. Have you found any downloadable signatures for the Arch package?

alerque commented on 2020-06-04 22:12

Thanks for that fix.

One more thing I noticed that needs fixing but I don't plan on jamming in too abruptly is that the upstream Zoom releases are GPG signed and this does not validate the key. Arch packaging standards dictate that if upstream provides security features like that they should be passed on to the end user. In this cases it's somewhat disruptive to add since many people don't know how to locally sign the key as trusted, but it should be addressed at some point.

(And the fact that Zoom is far more likely to suffer a security breach from insecure coding internally than have their packaging hijacked over the wire when AUR people download it is neither here nor there.)

netcrusher commented on 2020-06-03 11:36

FYI: I was able to fix my webcam issues (webcam showing only black screen) by applying the workaround mentioned in the wiki, i.e. using LD_PRELOAD=/usr/lib/libv4l/

netcrusher commented on 2020-06-03 11:11

@caleb: Thanks! I've added you as a co-maintainer. I went ahead and directly added the provides=('zoom') line while I was at it :)

alerque commented on 2020-06-03 08:57

@netcrusher You can add me as a co-maintainer and I'll help bump this for you. You can look around, I have a bit of a track record with maintaining packages and co-maintain a lot of others.

Also this is missing provides=('zoom') which would make it possible to use with zoom-firejail and such. Adding that would be my first action ;-)

netcrusher commented on 2020-05-19 15:14

@brmbr: Regarding update delay, the only reason zoom-system-qt updates sometimes arrive later than zoom updates is my free time (or rather the lack of it :) ). It is really only about changing the pkgver. Maybe I can find a co-maintainer to help with updating.

netcrusher commented on 2020-05-19 15:14

@huyizheng: Interesting - the webcam does not work for me as well. I am not quite sure why that is, a brief investigation did not uncover any obvious error messages.

netcrusher commented on 2020-05-19 15:13

@LazyGeniusMan: Zoom provides a pre-built Arch Linux package (not on the AUR) that contains a bundled (outdated) version of Qt, currently Qt 5.9.6 (the current Arch Qt version is 5.14.2). The other Zoom package on the AUR, zoom, only extracts the contents and re-packages them. This package on the other hand actively removes the bundled Qt libraries, which means that the normal, Arch Qt libraries will be used that's why this package is called zoom-system-qt). That has some up- and some downsides.

Reasons to choose zoom-system-qt instead of zoom:

  • The bundled Qt libraries in zoom do not include the Qt Wayland support libraries. This means that using the Qt Wayland backend (QT_QPA_PLATFORM=wayland-egl) is not supported in the zoom package, it has to run on Xwayland. zoom-system-qt on the other hand fully supports running Zoom on Wayland as long as you have the qt5-wayland package installed.
  • Bundling Qt means wasting disk space since the Qt libraries are duplicated. This in turn means that the zoom-system-qt package is smaller than the zoom package.
  • Bundling Qt means you do not benefit from more recent Qt improvements and bug fixes.

Reasons to choose zoom instead of zoom-system-qt:

  • Removing the bundled Qt libraries is definitely not supported by Zoom. You can try to report incompatibilities with newer Qt versions upstream, however you can't expect Zoom to help you in any way.
  • Adding to the previous point, it seems that Zoom (from zoom-system-qt) can't correctly open the webcam on some systems.

The dependencies are different because zoom-system-qt obviously depends on the system Qt installation, while zoom does not require on Qt, rather the bundled Qt libraries depend on some packages required by the X11 backend.

I hope that cleared up any confusion.