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: 29
Popularity: 1.59
First Submitted: 2020-05-03 20:50
Last Updated: 2020-12-14 20:43

Dependencies (15)

Required by (3)

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 »

coxackie commented on 2020-11-18 12:26

There are also wayland-related Qt libraries that are being removed from the package, as I can see from the PKGBUILD. Shouldn't the equivalent system Qt wayland libraries be installed?

je-vv commented on 2020-11-18 06:15

Can "pulseaudio-alsa" be moved to optdepends please? Zoom supports plain ALSA audio on GNU+Linux, so no need to make pulseaudio plugin hard required. Thanks !

michaldybczak commented on 2020-11-17 20:35

I have the same problem. It launches only icon in the tray and zoom doesn't really work. I had to downgrade it to previous version. I don't think it's a matter of too new libraries, because the issue would show up after system update, not zoom-qt update and the old version works still fine. I noticed that the new version had another requirement which was auto-installed: patchelf. So maybe patchelf's version or libraries are too new? The worst part is, that there is no output in the terminal, so we have no clue what is happening.

netcrusher commented on 2020-11-17 14:16

@coxackie: Yep, I noticed that as well. The size increase is solely from the actual zoom binary which went from ~63MB to ~73MB.

I've now spent a considerable time trying to debug this issue, but so far I couldn't narrow down a cause. My guess would be that the included QML files are somehow incompatible with newer system Qt libraries (even though the version difference hasn't been an issue previously). It seems that at some point the process just waits for something to happen, but I couldn't find out what it is actually waiting for.

For now, my advice would be not updating to 5.4.54779.1115-1 or, if you already installed the update, downgrading to the previous version 5.4.53391.1108-1, which still works fine for me.

coxackie commented on 2020-11-17 12:09

@netcrusher: I did notice that the package size increased for some 8MB or so. Maybe more libraries were introduced in the bundle? I am sure you guys will figure it out.

netcrusher commented on 2020-11-17 10:14

@coxackie: Thanks for the report. I just noticed the same issue on my system and I'll try to investigate.

coxackie commented on 2020-11-17 09:53

Does anyone else have a problem with the latest update (5.4.54779.1115-1)? When launched, I can only see the tray icon with a menu, but nothing happens upon pressing any of the entries.

alerque commented on 2020-11-08 13:27

@mnabid I hadn't noticed the /opt/zoom/version.txt file, I'd looked in-app and seen the .1 scheme. Given that file (not to mention other distros) it does sound like the most official think anyway and .1 (or whatever it changes to) is just and end user alias for some specific build numbers. Thanks for the research.

mnabid commented on 2020-11-08 12:53


Just wanted to put my two cents in.

I looked into the official Debian and Arch binaries and both of them show the package version as 5.4.53350.1027. /opt/zoom/version.txt shows the same. I think it'd be best to follow the version scheme in the official package, unless the Zoom devs change it.

alerque commented on 2020-11-08 08:49

@netcrusher I updated the version fetcher to work with the current scheme, but I think the scheme is wrong. No great foul but this should be (note the .1). Unfortunately fixing this would require adding an epoch to the build. For sure the next time the minor version changes can we take the chance to fix our version scheme?