Package Details: zoom 5.11.1-1

Git Clone URL: (read-only, click to copy)
Package Base: zoom
Description: Video Conferencing and Web Conferencing Service
Upstream URL:
Keywords: call conference meeting video
Licenses: custom
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 544
Popularity: 11.74
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2022-06-30 09:17 (UTC)

Pinned Comments

a172 commented on 2022-06-13 14:25 (UTC) (edited on 2022-06-13 14:25 (UTC) by a172)

@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.

Some ~/.config/zoomus.conf updates:

  • SSO Login: I don't have qt5-webengine installed, and the ebeddedBrowserForSSOLogin line doesn't exist in my config zoomus.conf. SSO login works just fine (issues with Firefox containers aside).
  • Audio: I am using Pipewire via pipewire-pulse. defaulted to alsa for me (or I changed it without realizing it). I probably could have installed pipewire-alsa and fixed my issues, but I set system.autio.type=pulse (a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.

If anyone finds documentation on ~/.config/zoomus.conf, please let us know.

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

ahercor commented on 2022-07-02 04:11 (UTC)

Hi I'm running on some trouble with the package which I was unable to solve till now.

I have my windowing system working just fine (I'm using Xmonad + Lightdm + Xorg), I also changed the /sys/class/backlight/intel_backlight/brightness to basically match the maximum brightness and again works fine, the problem comes when screen sharing on Zoom meetings. In that case my screen brightness decays a lot for me and for the shared content to the point I can't see a lot.

Is this a well known problem? I see below other issues when screen sharing but for me is just the brightness.

edh commented on 2022-06-28 10:23 (UTC)

Sure, will do with the next release.

ReyJamonico commented on 2022-06-28 10:04 (UTC)

+1 to making xorg-xwayland optional. For non-wayland users it's an unnecessary dependency. Thanks!

TioDuke commented on 2022-06-23 11:27 (UTC)

I can run zoom without xorg-xwayland without problems. Surely I am not running sway nor wayland at all.

Please consider making the dependency on xorg-xwayland opional.


Natherul commented on 2022-06-23 04:46 (UTC) (edited on 2022-06-23 07:46 (UTC) by Natherul)

Has anyone figured out how to make zoom forcibly run in x11 if the rest of the session is in wayland or a way to get screen share to work in wayland (and not using OBS camera workaround)?

Using KDE and wayland and I have tried QT_QPA_PLATFORM=xcb though it seemingly makes no difference for me

EDIT: I got it working from terminal but I cannot get it to work by editing the desktop file. (although I guess that gets overwritten if I get a zoom update). From terminal this works: QT_QPA_PLATFORM=xcb XDG_SESSION_TYPE=x11 nohup zoom %U &; disown

EDIT2: apparently it did not work as it seems to work from my side however then people in the meeting reports that the share was just a black screen even though the preview before share on my side was showing correctly.

a172 commented on 2022-06-13 14:25 (UTC) (edited on 2022-06-13 14:25 (UTC) by a172)

@edh - That's not the answer I was hoping for (I was really hoping we could get it to launch without xwayland), but at least I know I'm not missing something.

Some ~/.config/zoomus.conf updates:

  • SSO Login: I don't have qt5-webengine installed, and the ebeddedBrowserForSSOLogin line doesn't exist in my config zoomus.conf. SSO login works just fine (issues with Firefox containers aside).
  • Audio: I am using Pipewire via pipewire-pulse. defaulted to alsa for me (or I changed it without realizing it). I probably could have installed pipewire-alsa and fixed my issues, but I set system.autio.type=pulse (a lucky guess) and this worked. This should work for anyone using straight PulseAudio as well.

If anyone finds documentation on ~/.config/zoomus.conf, please let us know.

edh commented on 2022-06-08 15:56 (UTC)

@a172 That is actually a great question because I did not restart sway and solely relied on lsof -d DEL | awk "\$8~/\/usr\/lib/ { print \$NF }" to check for loaded but now deleted libraries. Since none were shown I assumed I had no program using xorg-xwayland and I could avoid exiting sway. However, if I do restart sway, zoom does not work :(

I will add xorg-xwayland to the dependencies list.

a172 commented on 2022-06-07 21:34 (UTC)

@edh - dumb question, but did you exit and restart Sway after uninstalling xorg-wayland? If so, what are your relevant env vars? Something like env | grep -ie wayland -e qt. Here's mine (minus a few irrelevant ones):


edh commented on 2022-06-07 09:20 (UTC)

@drybalka,a172 I can uninstall xorg-xwayland and zoom still works for me. I am running sway and use no special configuration for zoom.

drybalka commented on 2022-06-07 08:42 (UTC)

@a172 Thank you for the insight! This solved my issue and now Zoom works again. I needed to have xwayland after all (and probably to also set the environment variable QT_QPA_PLATFORM="wayland;xcb") or zoom simply would not start. Maybe it can be added to the dependencies somehow?

a172 commented on 2022-06-06 20:37 (UTC)

@drybalka - even when Zoom is running natively in Wayland, it still need XWayland to start up. I've seen a few other apps with similar behavior. If anyone has insight on how to get native Wayland apps to run without XWayland, I'm all ears.

charm001 commented on 2022-06-06 20:26 (UTC)

Was getting a Core Dump when starting Zoom:

zoom[2733] trap int3 ip:62813b9285a5 sp:7e9710e216a0 error:0 in
systemd-coredump[3170]: [🡕] Process 3161 (zoom) of user 1000 dumped core.

Zoom Log ( ~/.zoom/logs/zoom_stdout_stderr.log) shows:] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/zoom/cef/chrome-sandbox is owned by root and has mode 4755. 

I did what it says and Zoom is working again:

chmod 4755 /opt/zoom/cef/chrome-sandbox
chown root:root /opt/zoom/cef/chrome-sandbox

Are there issues with doing what it says?

drybalka commented on 2022-06-01 08:08 (UTC)

@sameer Indeed, after symlinking I do not get any relevant error info anymore - zoom just does not start at all with an error "zoom was exited due to a handled signal: 5". Any ideas? =)

sameer commented on 2022-05-31 22:40 (UTC) (edited on 2022-05-31 22:41 (UTC) by sameer)

does anyone have a positive experience running zoom with pipewire on wayland (sway, in particular)?


Yes -- I am running Sway + Pipewire + Zoom with no issues.

The pacmd not found error is because pipewire-pulse does not provide pacmd but does provide pactl. You can just symlink /usr/bin/pacmd to /usr/bin/pactl to get rid of the warning. This works because pactl is a subset of operations supported in pacmd, and Zoom does not need any options other than those in pactl (AFAIK).

It is not a big deal though, Zoom worked fine for me even if it couldn't find pacmd.

darose commented on 2022-05-31 15:08 (UTC)

BTW, when I google "sh: line 1: pacmd: command not found" this is the only link that comes up:

Seems like this must be something wayland related.


darose commented on 2022-05-31 15:06 (UTC)

@drybalka That's a really odd error by the way. Zoom isn't a shell script:

[darose@titan ~]$ file /usr/bin/zoom
/usr/bin/zoom: symbolic link to /opt/zoom/ZoomLauncher

[darose@titan ~]$ file /opt/zoom/ZoomLauncher
/opt/zoom/ZoomLauncher: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/, for GNU/Linux 2.6.32, BuildID[sha1]=6ea54f33432041c8c1cfba3bfd1948ca717d398c, stripped

So I'm not even clear what shell script is getting executed that's calling pacmd and failing. I would suggest trying to track that down.

drybalka commented on 2022-05-31 14:59 (UTC)

@darose Well, it still doesn't work for me =( I am not sure why this may be important, but I'll specify the question a bit more: does anyone have a positive experience running zoom with pipewire on wayland (sway, in particular)?

darose commented on 2022-05-31 13:24 (UTC) (edited on 2022-05-31 13:25 (UTC) by darose)

I use zoom with pipewire with no issues, and I've not run into that error with pacmd either. I have the following pipewire packages installed:

gst-plugin-pipewire 1:0.3.51-1
libpipewire02 0.2.7-2
pipewire 1:0.3.51-1
pipewire-alsa 1:0.3.51-1
pipewire-pulse 1:0.3.51-1
wireplumber 0.4.10-3

And the following pulse packages installed:

libpulse 15.0-4
pipewire-pulse 1:0.3.51-1
xfce4-pulseaudio-plugin 0.4.3-2


drybalka commented on 2022-05-31 09:25 (UTC)

Does anyone have a positive experience with running zoom with pipewire instead of pulseaudio? When I run it I get “sh: line 1: pacmd: command not found”. However, pacmd is provided only by the pulseaudio base package and is absent in pipewire-pulseaudio. Am I missing some option to force zoom to use pipewire?

edh commented on 2022-05-27 19:06 (UTC)

@nursoda Yes, this is an upstream error and no it can not be fixed in the PKGBUILD with any amount of work that could be considered reasonable because they only ship binary packages.

nursoda commented on 2022-05-27 19:00 (UTC)

Zoom used to create './cache/zoom/'; since a while, it creates and uses './cache/zoom\ /'. Is that an upstream error? Could it be corrected in the PKGBUILD?

nursoda commented on 2022-05-23 17:33 (UTC)

Mic works fine for me before and after update to 5.10.6. I'm using pulseaudio (only): I uninstalled pipewire after I got bitten by

Energi commented on 2022-05-23 08:32 (UTC)

After updating to 5.10.6, none of my system microphones produces an output. Using pulseaudio. Works properly when downgraded to 5.10.4.

elynnaie commented on 2022-05-18 19:05 (UTC)

After the most recent update, when connected to a meeting, as soon as I connect a bluetooth audio device, Zoom crashes. Have others been having a similar issue?

Similar, but a bit different. When I try to select my bluetooth headphones in my zoom speaker settings, it blares a loud static noise that doesn't end until I quit zoom or disconnect my headphones. I'm using pipewire.

keiichiiownsu12 commented on 2022-05-18 12:54 (UTC)

After the most recent update, when connected to a meeting, as soon as I connect a bluetooth audio device, Zoom crashes. Have others been having a similar issue?

d_fajardo commented on 2022-05-18 11:57 (UTC)

Zoom crashes whenever I try to do a Share Screen. Just wondering if this is a bug worth reporting upstream or if this is a local problem.

d_fajardo commented on 2022-05-18 11:55 (UTC)

Zoom crashes whenever I try to do a Share Screen. Just wondering if others are having the same issue. Could this be a bug worth reporting upstream?

d_fajardo commented on 2022-05-18 11:55 (UTC)

Zoom crashes whenever I try to do a Share Screen. Just wondering if others are having the same issue. Could this be a bug worth reporting upstream?

kuba-gaj commented on 2022-05-18 10:11 (UTC)

Virtual backgrounds still not working for me. Every time I enable them my camera freezes and unfreezes if I disable them.



to ~/.config/ did not fix the issue.

I would appreciate any suggestions.

zalmanlew commented on 2022-05-17 18:56 (UTC)

Hey everyone. What do I actually need to include in the ~/.config/zoomus.conf file in order to get the settings to apply?

I've tried a few different ways but couldn't get it to work. I'm trying to disable login with google, facebook, sso and a few other settings. The configs for Windows are


brandons209 commented on 2022-05-17 16:28 (UTC) (edited on 2022-05-17 16:30 (UTC) by brandons209)

@fant0me Adding the section referenced in that support article to ~/.config/zoomus.conf worked for me!


  1. Edit ~/.config/zoomus.conf using whatever text editor.
  2. Scroll to the bottom and add this section:

Restart zoom and viola! Backgrounds work flawlessly again. I tried this with blur, default backgrounds, and custom backgrounds. There are other issues with audio on the latest version so you might want to downgrade as well.

fant0me commented on 2022-05-14 01:14 (UTC)

Virtual Backgrounds Zoom has a fix for virtual backgrounds not working listed on their website, although I cannot find the ZoomMedia.ini config file they are referring to. Maybe this is already enabled and I have the same problem as others have mentioned, but I have no way to confirm. Does anyone know where this file would be? I already tried /etc, and /opt/zoom, nor in ~/.zoom. Thanks in advance.

cge commented on 2022-05-11 14:58 (UTC)

The version here (5.10.6) is coming from Zoom, but is actually newer than the latest version available on Zoom's download center ( It may be that 5.10.6 was withdrawn because of microphone problems (I also have no microphone input on 5.10.6).

kallok commented on 2022-05-11 08:56 (UTC)

After the latest 5.10.6-1 update, zoom no longer gets audio from my microphone. It can see my microphone, but the level bar in the audio settings doesn't move as I speak and no one can hear me. Other applications and pavucontrol can use and see my microphone without problems. I fixed this by downgrading to 5.10.4-1.

kflak commented on 2022-05-05 17:53 (UTC)

Did anybody manage to get screensharing working with sway? I get the message that screen sharing is only supported on [lots of distros], arch... but apparently not with sway? I am using xdg-desktop-portal with the xdg-desktop-portal-wlr backend.

mir commented on 2022-05-04 16:25 (UTC)

@bigcajun826: You were right, it works again if I turn the background feature off. Thanks for pointing this out!

edh commented on 2022-05-04 09:37 (UTC)

@Coelacanthus Can you please file an issue upstream so that zoom updates their package dependencies accordingly? It is hard for me to reason about the blackbox that zoom is especially considering that upstream says ibus is a hard dependency.

Coelacanthus commented on 2022-05-04 06:34 (UTC)

zoom /opt/zoom/platforminputcontexts/
zoom /opt/zoom/platforminputcontexts/

Zoom now has both IBus and Fcitx input method modules, so ibus is not necessary, users can use fcitx/fcitx5 as the input method (available in actual measurement). So you can remove ibus from a strong dependency, or move it to an optional dependency, and add fcitx and fcitx5 as optional dependencies at the same time.

edh commented on 2022-05-03 22:03 (UTC)

@bigcajun826 Regarding the comments: Both (Pulseaudio and SSO login) still seem relevant to me. Is there a specific reason why you think otherwise?

bigcajun826 commented on 2022-05-03 21:49 (UTC)

@mir Do you happen to use the "blur background" feature? If so, try turning that off and see if your camera works again. For me, it seems to be hit-or-miss since the 5.10.x versions of Zoom. Sometimes I can use the blur background feature, sometimes it exhibits symptoms similar to you (black screen, frozen image)

mir commented on 2022-05-03 21:15 (UTC) (edited on 2022-05-04 16:24 (UTC) by mir)

After updating (pacman -Syu and updating zoom), my webcam stopped working in zoom. The webcam works fine for other applications, zoom detects it (but then shows a black picture) and picks up the microphone of the webcam. It is a Logitech, Inc. HD Pro Webcam C920.

Last good version is 5.9.6-1, first bad 5.10.0-1.

UPDATE: Found that it works when I turn the background feature off.

BTW, does it still make sense to pin the two comments from 2020?

wermington commented on 2022-04-30 08:55 (UTC)

Hi everybody, I decided to try Wayland on my desktop with NVidia GPU, but Zoom is crashing:

Process 18620 (zoom) of user 1000 dumped core.
    Stack trace of thread 18620:
    #0  0x00007fa0f46608a4 __pthread_mutex_lock@GLIBC_2.2.5 ( + 0x908a4)
    #1  0x00007fa0f06df8ca n/a ( + 0x68ca)
    Module with build-id bb9bd2657bfba9f60bd34d2050cc63a7eb024bc4
    Module with build-id 46ffdf3d477a170314060c26927470d7399bc900
    Module with build-id 9751ec2d3a5c4c60364aca75bc6005b7dc13f59c
    Module zoom with build-id fd507703cee817f9dc966e3c37fab7f15c75da23
    Stack trace of thread 18620:
    #0  0x00007fa0f46608a4 __pthread_mutex_lock@GLIBC_2.2.5 ( + 0x908a4)
    #1  0x00007fa0f06df8ca n/a ( + 0x68ca)
    #2  0x00007fa0f87a21a7 wl_egl_window_destroy ( + 0x11a7)
    #3  0x00007fa07d8098e8 _ZN15QtWaylandClient17QWaylandEglWindow17invalidateSurfaceEv ( + 0x98e8)

full stacktrace:

Has anybody else encountered a similar problem? I have tried --no-sandbox, but with the same crash.

DAC324 commented on 2022-04-29 10:41 (UTC)

Does anybody know if the Linux version is also affected?

sneakyturtle commented on 2022-04-28 15:22 (UTC)

For anyone having the same virtual background not working problem, try opening zoom client before clicking on the join room. I found out that this way the virtual backgrounds work and if I join the link directly the camera doesn't work with virtual backgrounds.

chovy commented on 2022-04-26 10:06 (UTC)

-> Flagged Out Of Date AUR Packages: zoom

dieelt commented on 2022-04-25 13:48 (UTC)

Crashes for me using Nvidia and Wayland. Adding --no-sandbox fixes the issue. Maybe this can help someone.

edh commented on 2022-04-25 10:17 (UTC)

@yinyangkoi To be quite frank my best guess would be that what you observe is a spurious effect. Both packages provide the exact same files after all! Please refer to the PKGBUILD to validate that this package just repackages whatever is provided upstream.

yinyangkoi commented on 2022-04-25 08:45 (UTC)

Sharing screen doesn't crash anymore on 5.10.3-1, but when trying to enable the blured background, the camera would just freeze. I installed the package provided from the zoom website, and now the blurring works again.

edh commented on 2022-04-22 08:13 (UTC)

@iRaS Calling the package simple is an overstatement. Since there is no source code available, it really just repackages what is available upstream. Thus, I think it is highly unlikely that the bug is related to the package/packaging itself. I would suggest filing a bug upstream to let the zoom folks know about your problem.

iRaS commented on 2022-04-22 06:55 (UTC)

@yavko no, also the latest version has the same "feature". I'm wondering if that is an issue from zoom or from the package.

Mordavolt commented on 2022-04-19 16:36 (UTC)

Can confirm the screen sharing is finally fixed in zoom-5.10.3-1.

smokeinbrain commented on 2022-04-19 11:45 (UTC)

Does anyone know if zoom still crashes when sharing screen on new version 5.10.3-1?

chovy commented on 2022-04-18 23:01 (UTC)

new version available.

yavko commented on 2022-04-17 00:52 (UTC)

@iRaS have you figured out how to fix the WM_CLASS thing? I have the same issue but the zoom app also doesn't use the correct icon anymore, I might try the flatpak to see if it fixes this. Btw I'm on gnome 42.

alexorso commented on 2022-04-07 02:08 (UTC)

I have exactly the same problem @krmath is having: enabling the virtual background without a green screen results in either a frozen or a completely black video feed.

In addition, trying to share my screen results in Zoom freezing and requiring a restart.

I am running Zoom version 5.10.0-1 on Xorg and did not have a problem using virtual backgrounds or sharing my screen until recently. Any solution or workaround would be very welcome.

chris_muc commented on 2022-04-04 13:55 (UTC)

as a workaround version 5.8.6 was working fine until today, where it says: "Update Required Your app version needs to be 5.9.3 (1911) or higher to sign in."

I am using company Sign On.

Anyone tested other later versions that do not crash?

krmath commented on 2022-04-01 04:00 (UTC)

Virtual background not working as of last update on multiple machines.

I have a thinkpad T470 and T480 that I have used for work, including Zoom meetings, for a while now, and have had no issues until over the past weekend, which was the first time I used Zoom since the lastest update (22 March). Using either laptop, I would get a black screen when unmuting my video feed (to be clear, it is my video feed that is completely black; not my actual screen). When I open up the video settings, it fills in a still snapshot from the webcam, but not a live feed. Closing and reopening the settings refreshes the still image.

After a bit of experimentation, I figured out that the video feed works fine when disabling the virtual background. I can also use the virtual background with the "I have a green screen" enabled and get a live feed, but since I don't actually have a green screen, the background image is not properly applied.

Again, I have the same behavior on multiple laptops, and Zoom was working fine prior to the past update on both laptops.

rosekunkel commented on 2022-03-31 00:22 (UTC)

@GreenAvocado thanks for your help. Making the sandbox binary SUID seems to have fixed it:

$ sudo chmod u+s /opt/zoom/cef/chrome-sandbox

GreenAvocado commented on 2022-03-30 15:05 (UTC) (edited on 2022-03-30 15:05 (UTC) by GreenAvocado)

@rosekunkel it seems to be a problem with the sandbox, which refuses to run if it is not SUID root. I was able to get Zoom to launch using the --no-sandbox option, but I had problems getting links to open in Zoom still.

You can probably also fix it by changing the sandbox binary to be SUID root, which is probably the better solution here.

rosekunkel commented on 2022-03-29 20:42 (UTC)

After upgrading to version 5.10.0, zoom no longer starts on my machine. Running it from the terminal prints no output and just exits after a second or two. The previous version (5.9.6) starts fine.

MarieSaphira commented on 2022-03-28 12:24 (UTC)

@bigcajun826 5.10 seems to have a problem with blurring the background. The camera was working fine after I turned the blur off.

iRaS commented on 2022-03-28 09:55 (UTC)

I had to downgrade to zoom 5.9 today because clicking zoom links caused the windows to have a strange WM_CLASS (the get parameters ?join=....). That is a problem with tiling window managers that have an exception for windows with WM_CLASS=zoom...

AchmadFathoni commented on 2022-03-25 16:59 (UTC)

I never have any screen sharing problem on KDE x11

branweb commented on 2022-03-23 18:34 (UTC)

@darose also tried screen-sharing on 5.10.0 and get the crash. Downgrading to 5.8.6 as others have done seems to have fixed it.

bigcajun826 commented on 2022-03-23 11:49 (UTC)

I can't speak much for screen sharing as I haven't really tried it. But 5.10 seems to have an issue for me where my camera doesn't transmit any data. The light on my laptop indicates I'm sharing video, but nothing shows up. Reverting back to 5.8.6 or any of the 5.9.x versions gets my camera working again.

mbaker442 commented on 2022-03-23 03:41 (UTC)

@darose I'm on 5.10.x and I can confirm screen sharing causes the client to crash completely.

darose commented on 2022-03-22 18:38 (UTC)

Anyone know if 5.10.x fixes the screen sharing crash issues a number of people ran into with the 5.9 series?

edh commented on 2022-03-22 17:28 (UTC)

@ddeville Please file a bug upstream. I am sure they are happy to fix it for all Linux distributions.

ddeville commented on 2022-03-22 17:23 (UTC)

Looks like WM_CLASS in 5.10.0-1 has a trailing space "zoom " which breaks bspc rules in bspwm.

darose commented on 2022-03-04 00:00 (UTC)

I can confirm as well that screen shares are crashing on the 5.9.x versions. (Found out the hard way - during a call today.) :-( And that downgrading to 5.8 works. If anyone hears of a fix, please post.

aggregat commented on 2022-03-01 15:36 (UTC)

@el_kleino I can confirm the exact same problem. 5.9.3 and 5.9.6 frequently crash hard when trying to share. It also seems to be worse with more people in the call. But it will also sometimes crash with one other participant.

I have downgraded to 5.8.6 for now but would love some solution for this problem.

chris_muc commented on 2022-02-25 14:48 (UTC)

@el_kleino I experienced same screen sharing crashed. I downgraded to 5.8.6-1 -> seems to work fine for now.

el_kleino commented on 2022-02-24 07:36 (UTC)

Hi, since the last upgrade, zoom frequently crashes when I try to do screen sharing. Does someone else have the same problem? It seems to happen more frequently if more people are in the call.


qt.scenegraph.general: Animation Driver: using vsync: 16.95 ms
qt.scenegraph.general: texture atlas dimensions: 1024x512
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.95 ms
qt.scenegraph.general: texture atlas dimensions: 1024x1024
qt.scenegraph.general: Using sg animation driver
qt.scenegraph.general: Animation Driver: using vsync: 16.95 ms
qt.scenegraph.general: texture atlas dimensions: 2048x2048
zoom was exited due to a handled signal: 11 
ZoomLauncher exit.

titaniumbones commented on 2022-02-15 18:09 (UTC)

@thuchuc, if you are a gnome user, then the problem is likely that zoom abuses the screensharing mechanism under wayland, and by default, gnome will not allow the security violation. The workaround is to use lookingglass (ALT-F2 --> lg) and set this variable to true in the console:

global.context.unsafe_mode = true

It works, but you have to do it every login.

tchuchuc commented on 2022-02-15 16:09 (UTC)

Hello everyone. It seems that I've lost the ability of sharing the screen in zoom. From what I'm reading it may be a problem of Gnome but I wanted to at least point this out here. Is anyone experiencing this issue?

RFSharpe commented on 2022-02-03 21:45 (UTC)

@tsujigiri_nin Thanks for reporting this to Zoom. Zoom is definitely the problem. I have tried using the Zoom Test meeting on two different Debian based systems. The test meeting crashed on both devices.

tsujigiri_nin commented on 2022-01-29 11:52 (UTC)

@lifestronaut, @RFSharpe - glad it's not just me. Fwiw I submitted a zoom bug report after trying another clean build and getting the same issue. Hopefully it might get fixed...

RFSharpe commented on 2022-01-28 18:13 (UTC)

@tsujigir_nin I had the same continuously scrolling "Zoom cannot detect your microphone" message today during a Zoom meeting. I am using EndeavourOS. My headphones are plugged in using the separate mini stereo jacks for speakers and microphone. Rebooting and rebooting with mic not plugged in did not remedy the situation for me. Output of "inxi -A"

Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio driver: snd_hda_intel Device-2: AMD Cedar HDMI Audio [Radeon HD 5400/6300/7300 Series] driver: snd_hda_intel Sound Server-1: ALSA v: k5.16.2-arch1-1 running: yes Sound Server-2: PulseAudio v: 15.0 running: yes Sound Server-3: PipeWire v: 0.3.44 running: yes

After the meeting I went to the Zoom Test site. I could not do any further troubleshooting because the Zoom crashed after when I attempted start a test Zoom meeting. No error messages were displayed.

arifer commented on 2022-01-27 20:06 (UTC)

Hi there, does anybody know how to get Zoom's configuration files to be stored in ~/.config? I was hoping that the installation would respect XDG_CONFIG_HOME but it didn't.

lifestronaut commented on 2022-01-27 13:52 (UTC)

@tsujigir_nin - I am experiencing the same issues. It doesn't appear to happen if I join with my mic plugged in, but it will happen if I disconnect my mic during the call or join without a mic. The only remedy I found is to reboot. Exiting zoom and restarting it yields the same unending cascade of notifications

tsujigiri_nin commented on 2022-01-26 11:38 (UTC) (edited on 2022-01-26 11:38 (UTC) by tsujigiri_nin)

Has anyone had issues with cascading/unstoppable 'Zoom cannot detect your [e.g.] microphone' messages on the 01/25 release? These cascading notifications prevented clicking any zoom buttons and continued after using keyboard shortcuts to exit the meeting. For me they occurred if I enter a meeting with the mic not set up (e.g. I forgot to plug it in). Zoom works as normal provided my mic is connected and configured in my system prior to joining a call. Weirdly, I don't get any notifications if I disconnect the mic during a zoom call.

ElijahLynn commented on 2022-01-10 21:33 (UTC) (edited on 2022-01-10 21:53 (UTC) by ElijahLynn)

Hi, does anyone know if Zoom unofficially supports any HID devices on Linux, for mute/unmute on a Jabra 410 speakerphone to mute/unmute in Zoom? Support says HID is only supported for macOS and Windows. I sent them a support request just now, asking here because not sure their support will actually know if there is anything under the hood.

Update: I opened a thread here too on this >

edh commented on 2022-01-02 21:30 (UTC)

@AchmadFathoni These dependencies are not required because they are pre-packaged with zoom. Since no source code is available for zoom, this is a plain re-packaging of the original zoom package. The package does not link against the system Qt but instead provides its own versions of these libraries.

AchmadFathoni commented on 2022-01-01 17:34 (UTC)

Looking at zoom binary dynamic link, it seems that zoom needs qt5-3d and qt5-gamepad as dependency.

zeroconf commented on 2021-12-13 21:13 (UTC)

Then we need just ignore that, as suggested here.

edh commented on 2021-12-13 20:20 (UTC)

@zeroconf There is no such thing as rebuilding zoom. This is a binary package with no source code provided whatsoever. This in itself is a bad situation but unfortunately the one we are in. Furthermore, most dependencies are bundled within the package itself since zoom requires old and outdated versions of many libraries.

Please investigate and think about the output of the commands you are posting a bit more before coming up with conclusions.

zeroconf commented on 2021-12-13 19:52 (UTC) (edited on 2021-12-13 20:00 (UTC) by zeroconf)

After updating system, rebuilding package:

yay --cleanmenu --rebuild -Syu zoom

... rebooting system, checkrebuild command claims that package zoom still needs to be rebuilt, although it is working properly. I hope this can be fixed. Below is the verbosed output of missing libraries locations.

$ checkrebuild -v

foreign zoom

ldd /opt/zoom/QtQuick/XmlListModel/ => not found

ldd /opt/zoom/QtQuick/Scene3D/ => not found => not found => not found => not found => not found => not found

ldd /opt/zoom/QtQuick/Scene2D/ => not found => not found => not found => not found => not found => not found => not found

ldd /opt/zoom/QtQml/RemoteObjects/ => not found

ldd /opt/zoom/ => not found

ldd /opt/zoom/ => not found => not found

ctcq commented on 2021-12-07 12:52 (UTC)

Got Screen Sharing to work on Gnome+Wayland (Manjaro) using the solution posted by @gj545rndmu

Here is what you have to do in detail:

  1. ALT + F2 to open Gnome Command Prompt
  2. Enter lg to open Looking Glass
  3. In the new Command Prompt that opens then, set global.context.unsafe_mode = true

Screen Sharing should work now.

Note: Much to everyone's surprise, enabling the unsafe_mode is considered unsafe. So take care and be sure to set it to false again when you don't need it anymore.

edh commented on 2021-11-25 10:14 (UTC)

@Adrades You should raise your issue with the upstream project, i.e. with zoom, the company.

Adrades commented on 2021-11-25 10:11 (UTC)

Thanks for the package !

I have an issue with my address mail, I can't put it in the field. I tested writing, deleting characters and Ctrl-V.

Maybe it doesn't fit the regex, my address is formatted like: name.surname1--surname2@server it's the '--' that can't fit in.

To whom should I complain about this issue ?

edh commented on 2021-11-19 09:04 (UTC)


Please read the previous comments on this exact topic!

kelen commented on 2021-11-19 08:53 (UTC)

May be we should change the ibus from depends to optdepends.

edh commented on 2021-11-15 14:37 (UTC)

@kleini Zoom is a dead simple package to maintain since they do not provide the means to build the package so I think I'll be fine. Thanks for the offer though.

kleini commented on 2021-11-15 14:07 (UTC)

@edh If you like to get help with upgrades, you can add me please as a co-maintainer?

PhotonX commented on 2021-11-15 13:03 (UTC)

I could solve my problem, for some reason the autoadjust for the microphone volume has put the volume of the USB webcam's microphone to zero...

gj545rndmu commented on 2021-11-10 09:30 (UTC) (edited on 2021-11-10 09:34 (UTC) by gj545rndmu)

Wayland Zoom screen sharing doesn't seem to work under Gnome 41 anymore!?

Edit: Okay just found this:

So either Zoom fixes it on their side, or as a workaround set global.context.unsafe_mode = true via Alt-F2.

PhotonX commented on 2021-11-05 12:03 (UTC)

After some update Zoom stopped recognizing the microphone from the USB webcam. In other applications the microphone works, Pulseaudio settings also show the input signal correctly.

I tried the solution from the pinned comment, that is, setting, but it didn't help. Zoom works with an old analog mic though.

Any ideas what I could try? Thanks!

sergefan commented on 2021-10-23 13:33 (UTC)

@harpium If you are using Wayland then currently there is no fix for this. Zoom under Wayland can only share the entire screen or the whiteboard according to the Zoom official support.

harpium commented on 2021-10-22 05:24 (UTC)

I'm only able to share my entire screen and not specific windows on Manjaro GNOME. Does anyone know a fix to this?

simple commented on 2021-10-15 05:35 (UTC)

I'm in agreement with @openmindead regarding the ibus requirement. As it is not explicitly required by Zoom for functionality (only specified as such in the .deb packaging) it should be made an optional dependency since it's likely that those needing ibus for alternate character input will already have it installed but those who don't are just burdened by an unnecessary extra install.

Proposed change to PKGBUILD:

depends=('fontconfig' 'glib2' 'libpulse' 'libsm' 'ttf-font' 'libx11' 'libxtst' 'libxcb'
    'libxcomposite' 'libxfixes' 'libxi' 'libxcursor' 'libxkbcommon-x11' 'libxrandr'
    'libxrender' 'libxshmfence' 'libxslt' 'mesa' 'nss' 'xcb-util-image'
    'xcb-util-keysyms' 'dbus')
optdepends=('ibus: InputBus for alternate character/emoji entry'
    'pulseaudio-alsa: audio via PulseAudio'
    'qt5-webengine: SSO login support'
    'picom: extra compositor needed by some window managers for screen sharing'
    'xcompmgr: extra compositor needed by some window managers for screen sharing')

More info

mvdan commented on 2021-10-07 09:15 (UTC)

I've also been running Zoom with xwayland for over a year now - their Wayland support just crashes too easily. At every major release I try Wayland again, and it just crashes again :)

nadavz commented on 2021-10-07 09:12 (UTC)

I've fixed many Wayland related crashes by changing Zoom to use X11. cp /usr/share/applications/Zoom.desktop ~/.local/share/applications/ and apply

< Exec=/usr/bin/zoom %U
> Exec=env QT_QPA_PLATFORM=xcb /usr/bin/zoom %U

pintert3 commented on 2021-10-03 18:59 (UTC)

@je-vv thanks for your suggestions, I tried most of them but none in particular made immediate impact, however, I believe it was probably a sort of glitch when some hosts added me to a meeting. If the host ever went offline, the problem would clear from that point onwards. The last update cleared the issue. Thanks again

sispus commented on 2021-09-30 07:11 (UTC)

hi, I am unable to get sound in zoom with pipewire on archlinux. As hv15 says, changing the line to in ~/.config/zoomus.conf works. However, I cannot use bluetooth headphones, it requires bluetooth to connect for alsa ( using bluez-alsa ) package and make necessary configurations (which results not to use pipewire for bluetooth).

Are there anyone use pipewire without problem?

openmindead commented on 2021-09-25 16:05 (UTC) (edited on 2021-09-25 16:07 (UTC) by openmindead)

Speaking of ibus dependency: fcitx5 works with Zoom just fine. So there's no need to force ibus to be installed as Zoom's dependency. Those who use it already have it installed right? And as of now those who don't use it just get a bunch of extra useless packages.

async commented on 2021-09-23 19:50 (UTC)

I looked through some of the recent comments and didn't see anything about this.. after a recent update, Zoom is now adjusting the volume of my microphone down to near-zero each time I join a call. It is driving me absolutely crazy.

I am using zoom-firejail.. combined with recent updates, I'm thinking it may have introduced a bug?

edh commented on 2021-09-22 20:27 (UTC)

Yes! Finally! I have been patiently waiting for a new release to free me from the current situation! :)

zeroconf commented on 2021-09-22 14:52 (UTC)

Zoom 5.8.0 has arrived - Appreciate, that available at Arch!

bulletmark commented on 2021-09-21 22:23 (UTC) (edited on 2021-09-21 22:26 (UTC) by bulletmark)

@alerque, why wouldn't that fix it? When this issue arose, the checksum could have just been updated (for the new binary), along with a pkgrel bump, and all of this drama would have been averted. Marking it version 5.7.6.a is less semantically correct because it implies an upstream version number change, which did not occur.

alerque commented on 2021-09-21 22:05 (UTC)

@bulletmark Bumping the pkgrel would not fix this, nor would it be semantically correct.

@edh Marking this as 5.7.6.a isn't a bad option actually. I don't think many who have already built this will care about doing so again, most are going to be using AUR helpers anyway that will just take care of it.

bulletmark commented on 2021-09-21 21:59 (UTC)

But the upstream binary package has changed, thus everybody should update! It is odd and undesirable when upstream packagers do this but it is not unprecedented and in cases where I have seen this before, the AUR maintainer just bumps the pkgrel without any of the ongoing confusion and dialog we have seen here.

edh commented on 2021-09-21 18:38 (UTC)

The current version number is not the issue here! Zoom released a new binary package under the same seemingly unique URL thereby breaking this package. To correct for this I introduced an artificial version bump. During this step I did a mistake in updating the pkgver and appended an a instead of an .a. Thus, I did not force a rebuild but actually decreased the version number.

For the time being please update manually (e.g. by uninstalling and then re-installing zoom again). The seemingly lower version is actually the most recent version.

Note, while I could still "fix" this by appending the .a, doing so would force everybody who already manually upgrade to rebuild the package as well. In my opinion this bother people unnecessarily who already put in the effort.

alerque commented on 2021-09-21 18:36 (UTC)

@darose I think you're missing the fact that this is a two part problem. There is a general issue of the upstream releases updates without changing the build number and there is a current temporary issue in that this a business missed the necessary segment separator.

Your scheme would be a viable scheme, but it would not solve the problem that upstream keeps changing their package without changing versions. Neither the "5.7.6" version nor the "31753.0818" build data changed when the package was updated last. In other words following your scheme would still have required a .a version bump on the part of this PKGBUILD.

There are ways out of the current mishapp with a instead of the .a that it should have been, but those are temporary and introduce other problems down the road (switching to build numbers means we can't go back to chis schemed when they don't add them properly, and adding an epoch is ugly and confusing).

Just "downgrade" your package to 5.7.6a-1 and move on. The next time around I doubt @edh will make the same mistake.

darose commented on 2021-09-21 18:26 (UTC)

@edh At your suggestion I went back and read old comments about the versioning. But I still don't understand what the issue is here.

I am currently running zoom 5.7.6 (31753.0818). Current build is 31792.0820. Would it not be possible to change the versioning scheme you're using to change the version number from 5.7.6 to Then an update to the new build version of would force an upgrade. Instead I see this:

warning: zoom: local (5.7.6-1) is newer than chaotic-aur (5.7.6a-1)

What am I missing here? Why would that not work?

nursoda commented on 2021-09-20 09:39 (UTC) (edited on 2021-09-20 09:45 (UTC) by nursoda)

Sorry for setting the "outdated" flag. I only now read all the discussion :( For reference in case someone stumbles upon this: Uninstalling zoom (5.7.6) and reinstalling zoom (to 5.7.6a) gives you the latest version.

edh commented on 2021-09-13 15:44 (UTC)

@dack Thank you for you comment. I am aware of the problem. Please read the previous comments. This issue has been extensively discussed. Touching pkgrel is the wrong thing to do here in my opinion.

dack commented on 2021-09-13 15:40 (UTC)

@edh Appending "a" to the version is a bit of a problem - it results in the wrong version ordering. For example, 1.0.0a is considered earlier than 1.0.0 (you can see this in man vercmp). For AUR helpers like yay, this will cause them to see the "new" version as a downgrade and not upgrade them. I think a better workaround would be to just bump pkgrel. That way it's treated as a newer package, and the upstream version number is kept as-is.

je-vv commented on 2021-09-10 17:44 (UTC)

@pinter3, have you tried combinations with pulseaudio-alsa and without it? That might help... Also combining setting and not setting the audio type with those other combinations... With pulseaudio-alsa, no matter your app uses alsa backend, it'll be proxied to pulseaudio. Zoom does work great without pulse, when you do not have pulse at all in your system. Actually I don't use pulse at all, only plain alsa, neither I have ever configured the audio type, and I never had issues with mute/unmute, neither audio in general, but if you use pulse, the best should be for apps to use their pulseaudio backends if available, I'd guess... As an alterantive to plain alsa, and pulse, have you tried using pipewire instead? Perhaps with pipewire-pulse and pipewire-alsa, or a combination of them? The other thing you might try is dropping pulseaudio/pipewire at all, while you figure out the pulseaudio mess with zoom. Zoom is proprietary, so perhaps getting help from them, or a zoom hosted forum might also help get some answers. Proprietary apps are really annoying. I only use zoom given I have no choice at work, :(

pintert3 commented on 2021-09-10 11:40 (UTC)

Ok, so I'm pretty late to bring this up. And from the comments, a few others have had the same (or similar) issue. But I'm going to be more specific and bring it up again, cause the pinned solution doesn't seem to work for me. So ever since some update I think in June/July, when I enter some meetings not hosted by me, (I'm not yet sure what the criteria is exactly, except that it appears whenever I enter a meeting muted, and I'm not the host), I can't unmute myself to speak, so I basically only the chat bar to talk. I use pulseaudio for sound. I tried changing to alsa, but no difference after I restarted zoom. I don't know if there's any other fix, I tried waiting for an update, but no difference, and I'm surely now getting desperate. Do I need to change from pulse audio to something else entirely?

internetuser commented on 2021-09-09 20:41 (UTC)

:: Searching AUR for updates... -> zoom: local (5.7.6-1) is newer than AUR (5.7.6a-1)

yay seems to think that 5.7.6a-1 is older than 5.7.6-1

edh commented on 2021-09-09 19:06 (UTC)

@darose Please read the previous comments. This issue has been extensively discussed.

P.s. a quick glance in the PKGBUILD will tell you that such an URL is already in use...

darose commented on 2021-09-09 18:22 (UTC)

When I went to the download page on their web site today ( and checked what URL my browser used to do the download, I saw it used the full version number, including build: . Any chance we could use that URL scheme for download going forward in order to avoid the version number issues?

internetuser commented on 2021-09-08 06:52 (UTC)

Anyone able to get hardware acceleration working?

jonathon commented on 2021-09-07 11:17 (UTC) (edited on 2021-09-07 11:21 (UTC) by jonathon)

Thanks for your patience. I didn't realise they reused the same build number in addition to version number (which is completely ridiculous - why even bother having a build number?).

edh commented on 2021-09-07 11:09 (UTC)

@jonathon As has been outlined a couple of times: This is not possible if upstream does not use unique identifiers. See for example the last commit. The version nor the build changed, the binary file though did change.

Now, there are only two options: I force an upgrade for every user by artificially changing the version to 5.7.6.a. This would require users who have already updated to reinstall the package without an actual need. The second option is to just wait and endure the current state of affairs until a new release is made. As of now, I am sticking to the second option.

jonathon commented on 2021-09-07 11:03 (UTC) (edited on 2021-09-07 11:16 (UTC) by jonathon)

Is there a reason not to include the build number at the end of the pkgver? e.g.


This should help avoid all future issues with different builds of the same subversion?

alerque commented on 2021-09-05 08:38 (UTC)

@hexhu, @mnussbaum, and others commenting on the versioning issue. This has been covered at length in previous comments but it cannot be corrected until the next release upstream. Zoom release the same version twice with a silent update using the same version. No, using pkgrel to indicate this would not have been correct. The use of a to indicate this was correct and standard procedure. The only mistake was that it should have been separated from the version as its own segment .a so that it didn't get sorted incorrectly as an alpha version indicator. The maintainer has already indicated they will get that right next time, but it isn't possible to fix this time without introducing an obnoxious epoch version that will never go away.

hexhu commented on 2021-09-05 07:46 (UTC) (edited on 2021-09-05 07:48 (UTC) by hexhu)

The versioning seems wrong, should probably be 5.7.6-2 not the current 5.7.6a-1. Breaks pacman upgrade check (see below). On it shows "Version 5.7.6 (31792.0820)", we should stick to that when packaging. Same format is followed by the latest .PKGINFO: pkgver = 5.7.31792.0820-1.

:: Searching AUR for updates...
 -> zoom: local (5.7.6-1) is newer than AUR (5.7.6a-1)
 -> Flagged Out Of Date AUR Packages:  zoom

James-T commented on 2021-08-30 09:32 (UTC)

To those commenting on the checksum error.

If you are using yay then you'll need to remove the zoom tree in ~/.cache/yay otherwise it doesn't do the download properly.

edh commented on 2021-08-26 18:46 (UTC)

@daniel_shub Well, I am still to blame. I should have checked that in advance. Right, I will do that next time as well.

P.S. thank you for answering @daniel_shub questions.

aditya commented on 2021-08-25 16:24 (UTC)

Thanks for the clarification regarding pkgrel. :)

keiichiiownsu12 commented on 2021-08-25 16:04 (UTC)

Wanting to verify if other Linux users have this issue: When I try to set an alternative host for a scheduled meeting, it appears no email is forwarded to the recipients. Neither do they gain host-privileges when connecting to the meeting. Is this feature disabled on Linux?

daniel_shub commented on 2021-08-25 13:36 (UTC)

@hellojack upstream provides the Arch package that this PKGBUILD is based on. That upstream package lists ibus as a dependency. Not obvious to me why it is a dependency, but generally I believe the upstream developers when they say something is a dependency. You can always remove it from your PKGBUILD.

alerque commented on 2021-08-25 08:47 (UTC)

@roper I can see from your error message that you are not using the latest version of this package. The current version saves the source with an extra a in there that does not show in your error message. Please update to the latest commit of this packaging repository.

roper commented on 2021-08-25 08:29 (UTC)

==> Validating source files with sha512sums...
    zoom-5.7.6_orig_x86_64.pkg.tar.xz ... FAILED
==> ERROR: One or more files did not pass the validity check!

hellojack commented on 2021-08-25 04:42 (UTC) (edited on 2021-08-25 04:45 (UTC) by hellojack)

Hello, are there reason for ibus being dependency? It is one of the input methods, not needed for people who use another ime.

spsf64 commented on 2021-08-24 14:26 (UTC)

@daniel_shub thanks for the tip (¨.a¨)!

daniel_shub commented on 2021-08-24 13:51 (UTC)

@edh first, thanks for maintaining the package. I maintain the rememberthemilk package and they pull the same crap of updating the binary without changing the version number. I want to say that I think your approach was almost spot on and what I am going to do in the future. Bumping the pkgrel for a change in the upstream binary is not what pkgrel is designed for while updating the pkgver to trigger a new download and rebuild is the way to go. Had you set pkgver to be 5.7.6.a instead of 5.7.6a, then vercmp would detect the change and everything would be fine. Of course no one should expect a maintainer to nail all the nuances of vercmp and the package build process every time. Again, thanks for maintaining this package.

edh commented on 2021-08-23 22:53 (UTC)


Sorry, I forgot about the vercmp specifics here. I indeed intended to make the new version large than the one before. However, since the checksum was in a sense outdated, users who did not adapt the PKGBUILD could not upgrade anyways and those who did, do not need upgrade now.

No, this is simply not what pkgrel is for. Upstream updating the binary package is not the same as a mere rebuild with different configuration flags or changes to the PKGBUILD. See @aditya comment on the definition of pkgrel.

The reason why I was reluctant to change the pkgrel is because it does not force users to re-download the binary file. Of course I could have included pkgrel in the target filename but this did not seem proper to me.

bulletmark commented on 2021-08-23 22:10 (UTC)

Adding that 'a' doesn't trigger an update. Upstream has published a new binary so I would say an update is required, i.e. the pkgrel should be updated.

edh commented on 2021-08-23 19:01 (UTC)


The PKGBUILD really did not change, i.e. it is not a consecutive build. It is zoom that pushed a new binary package to the same URL.

aditya commented on 2021-08-23 18:48 (UTC) (edited on 2021-08-23 18:50 (UTC) by aditya)

Shouldn't the pkgrel have been bumped instead of adding the "a"?

The release number. This is usually a positive integer number that allows to differentiate between consecutive builds of the same version of a package. As fixes and additional features are added to the PKGBUILD that influence the resulting package, the pkgrel should be incremented by 1. When a new version of the software is released, this value must be reset to 1. In exceptional cases other formats can be found in use, such as major.minor.


rockneurotiko commented on 2021-08-23 09:31 (UTC) (edited on 2021-08-23 09:32 (UTC) by rockneurotiko)

The checksum of the last release (5.7.6-1) is different than the one specified on the PKGBUILD, maybe they changed the file without releasing a new version?

The sha512 for the file at the moment is 7c34f2f1951a22391ced31960fedba4f1058abf55f1e530b1069bc9b2946f54cd3a12713135ab7ea0ae57131e2ce30521315ce4a67673f7f024cd23f6e03c4be

Edit: I just saw the last comments, just ignore this one

edh commented on 2021-08-23 07:56 (UTC)

@sarovin Zoom changed the package without changing the URL. I'll update the package soon.

sarovin commented on 2021-08-23 07:54 (UTC)

Hi, I have a problem with the sha512sums validation.

:: (1/1) Parsing SRCINFO: zoom
==> Creazione del pacchetto: zoom 5.7.6-1 (lun 23 ago 2021, 09:50:20)
==> Download dei sorgenti in corso...
  -> È stato trovato zoom-5.7.6_orig_x86_64.pkg.tar.xz
==> Validazione di source file con sha512sums...
    zoom-5.7.6_orig_x86_64.pkg.tar.xz ... NON RIUSCITO
==> ERRORE: Uno o più file non hanno superato il controllo di validità!
error downloading sources: zoom

filotek commented on 2021-08-20 00:08 (UTC) (edited on 2021-08-20 00:10 (UTC) by filotek)

The Zoom desktop client isn't calling ::UnInhibit() method (against org.freedesktop.ScreenSaver) via DBUS when the meeting is over and the video window is closed. The call to ::Inhibit() is working fine when the video starts.

For services that observe the DBus calls to org.freedesktop.ScreenSaver (ie. caffeine or xssproxy), without the corresponding ::UnInhibit() call the screensaver stays inhibited, preventing xss-lock from kicking in and locking the screen, even if no video is playing, until the Zoom process is terminated.

I submitted a support request to Zoom, but I thought of mentioning it here in-case someone had some kind of work-around that I'm not aware of. Well... I do have a work-around; it's terminating the Zoom Desktop Client every-time I'm done with a conference call :(

EDIT: Missing DBus reference and grammar.

ElijahLynn commented on 2021-07-22 17:02 (UTC)

I found a workaround for my intermittent "Can't hear others on first join". And it is that if I go to "video settings" on the bottom left video dropdown, then go to Audio section and "test speaker", then I instantly hear the other participants without having to leave and re-join the meeting.

alerque commented on 2021-07-22 09:15 (UTC)

After installing the pkg.tar.xz debtapped package, pacman installed some other dependencies. AUR Zoom works now.

Specifically what other dependencies @BobbyBoohoo?

commented on 2021-07-22 02:18 (UTC)

Every time I used Zoom on sway, it crashed shortly after I joined the call. This seems to have been fixed after I downloaded a deb version of Zoom and debtapped it. After installing the pkg.tar.xz debtapped package, pacman installed some other dependencies. AUR Zoom works now.

keiichiiownsu12 commented on 2021-07-13 23:32 (UTC)

Anyone have luck with zoom on gnome and wayland? Whenever I use zoom in a gnome wayland session, I get noticeable slowdowns that only disappear when I go to gnome activities view.

ikke commented on 2021-07-10 19:02 (UTC)

@ElijahLynn I have the same issue, also fails the first time, but succeeds the second.

ElijahLynn commented on 2021-07-08 18:38 (UTC) (edited on 2021-07-12 17:21 (UTC) by ElijahLynn)

About 1 out of 15 meeting joins, I can't hear anyone, but they can hear me. Every time, I just have to say "Linux bug, rejoining" then leave the meeting (not exit zoom though) and rejoin and it works fine. Anyone else have this issue?

Update 1: I am still using Alsa/Pulsa, no Pipewire yet.

ElijahLynn commented on 2021-07-08 18:36 (UTC) (edited on 2021-07-08 18:41 (UTC) by ElijahLynn)

Nearly every time I login via Google with Zoom, it just hangs. Then I close it and relaunch Zoom, and login again and it is instant. Anyone else hit this issue, I wonder if I should report to Zoom.

Update1: I have embeddedBrowserForGoogleLogin=false

BlackPhoenix commented on 2021-06-23 08:24 (UTC)

If you have audio problems with pulseaudio, try replacing it with pipewire instead, it worked for me

oech3 commented on 2021-05-20 04:36 (UTC) (edited on 2021-05-20 04:37 (UTC) by oech3)

Why this package depends on ibus?

Edit:sorry this is duplicate

edh commented on 2021-05-15 08:02 (UTC)

@sonarypt Please contact the zoom support on this matter. I will remove it from the dependency array of it is not listed as hard dependency by upstream.

sonarypt commented on 2021-05-15 07:26 (UTC)

Please remove ibus as dependency from this package! For fcitx users: sudo pacman -Rdd ibus as it conflicts with your fcitx.

Loader009 commented on 2021-05-14 20:57 (UTC)

I have problems with annotating screen sharings of others for a few months now. Using LXQt from aur with KWin from aur. The whole second window with the screen share goes black, an overlay which only goes away if the second window disappears (e.g. switch to some room or closing/opening zoom).

I am switching to zoom-system-qt now, maybe this helps me for now.

edh commented on 2021-05-14 11:53 (UTC)

@aragon123 That sounds really strange and is not the case for me.

aragon123 commented on 2021-05-14 10:43 (UTC)

I had a problem with Zoom crashing when the electron [1] package was missing, after installing this, Zoom does not crash anymore.


killshot commented on 2021-05-09 02:10 (UTC)

Like hv15 commented, I tried pipewire instead of alsa and now I can use my bluetooth earphones with mic

edh commented on 2021-04-30 07:59 (UTC)

@dobedobedo, @angelsl As mentioned in a previous comment, ibus was added to the list of hard-dependencies by the folks at zoom.

bestfriend commented on 2021-04-29 20:20 (UTC) (edited on 2021-04-29 20:20 (UTC) by bestfriend)

Most Zoom functionality is good for me, but I have a persistent issue where participants cannot see annotations when I'm the one sharing.

  • I can annotate when others share.
  • I can annotate when using the whiteboard.
  • But Zoom isn't capturing the annotation overlay when I'm sharing.

Any ideas? Using i3wm here.

dobedobedo commented on 2021-04-29 18:26 (UTC)

May I ask what does ibus do in this package? I remove it from PKGBUILD and it still works.

angelsl commented on 2021-04-28 07:50 (UTC)

Why is ibus added to the required dependencies?

edh commented on 2021-04-27 19:57 (UTC)

@ewtoombs According to zoom, pulseaudio-alsa is actually a hard dependency. To make it easier for users to circumvent using pulseaudio, I moved it to the list of optional dependencies.

ewtoombs commented on 2021-04-27 19:46 (UTC)

Is pulseaudio-alsa really an optional dependency, now that zoom natively supports pulseaudio? What's with that?

edh commented on 2021-04-22 07:41 (UTC) (edited on 2021-04-22 07:42 (UTC) by edh)

@bulletmark Yes, those who updated within the three hours in which the source was still named the same need to prune their *_orig packages. I did so to not force people who already pruned their cache to perform a "fake" update.

bulletmark commented on 2021-04-22 07:32 (UTC)

@edh, but you didn't bump the pkgrel, so won't the helpers just use the cached PKGBUILD?

edh commented on 2021-04-22 07:20 (UTC)

I renamed the source files so that AUR helpers don't get confused. One shouldn't need to do anything anymore.

bulletmark commented on 2021-04-22 05:17 (UTC)

@abdulhakeem, just rm -rf ~/.cache/yay/zoom and then yay -S zoom.

abdulhakeem commented on 2021-04-22 05:12 (UTC) (edited on 2021-04-22 05:13 (UTC) by abdulhakeem)

@edh what do you mean by "remove any old *_orig packages lying around that match the current version"? I don't have anything like that in my yay cache folder, should I be looking somewhere else?

michaldybczak commented on 2021-04-21 13:58 (UTC)

Won't build because SHA512 sums won't match.

edh commented on 2021-04-21 11:37 (UTC)

Please forcefully remove any old *_orig packages lying around that match the current version. Zoom messed up their download portal and for a moment advertised old versions under a new name.

archChecker commented on 2021-04-21 11:16 (UTC) (edited on 2021-04-21 11:17 (UTC) by archChecker)

hi there, today i could not login into a zoom session because they did not update the available for arch although they stated its but is an old one.

As workaround i build the package via debtap from .deb to pkg.tar.xz. Hope it's helpfull.

rufat.badal commented on 2021-04-21 10:53 (UTC)

You should update the sha512sum to the new value: 68168b5841dc1700695be5628fcfc042836809f7a4ddc9d2746b081d6256e8285f12e6830b1b39f849c1848c92d893b7041bcb9e8c24e9f5a3db6991c3768d6c Currently a wrong one is listed in the PKGBUILD.

edh commented on 2021-04-20 07:10 (UTC)

@Nikita790 Sorry, according to zoom it is a hard dependency.

Nikita790 commented on 2021-04-20 04:47 (UTC)

Can we get rid of the ibus dependancy? it seems to work fine without it

edh commented on 2021-04-19 19:55 (UTC)

@yywrobbie You are absolutely right! Downloading the package via their website is broken too. Sorry for unflagging the package that quickly. We will have to wait for zoom to fix this issue.

yywrobbie commented on 2021-04-19 19:34 (UTC)

It appears there's a problem with the upstream 5.6.3 url ( where the downloaded file shows it's the 5.6.1 version (13632.0328). As a result, this AUR package (5.6.3-1) only gives you version 5.6.1 for the time being.

herod2k commented on 2021-04-13 16:43 (UTC)

Latest version of zoom makes awesome wm crash. I use arch + awesome wm + picom. It happens specially when I change it from floating to tiling or full screen and vice versa. With the appImage (same version) it doesn't happen. I can't replicate it, it happens randomly and I'm not 100% sure that zoom is the culprit. It could be some libraries.

edh commented on 2021-04-09 17:50 (UTC)

@caduser2020 You're right! Thanks! I'll add it with the next release. Given that most users will have pulseaudio or gtk3 installed, they will not notice that this dependency is missing.

caduser2020 commented on 2021-04-09 17:31 (UTC)

Missing libxtst as dependency. I don't know when it was added, but the package failed to run on a clean chroot.

mvdan commented on 2021-03-23 10:02 (UTC)

With the update to 5.6.0, I am finally able to run zoom on Wayland without xwayland :)

mooncher commented on 2021-03-22 18:52 (UTC)

@rogala you can downgrade by downloading the pacman package from zoom's website at The UI only supports downloading the latest version but you can get any version by grabbing a version number from and formatting the URL like so:

For the previous release that would be

From there you can install by doing # pacman -U zoom_x86_64.pkg.tar.xz

rogala commented on 2021-03-17 05:25 (UTC)

5.9.16-1-MANJARO, Zoom 5.5.4 (7938-0228).

Screen sharing after the latest Zoom update is majorly affected. The upload frame-rate is stuck precisely at 1 fps, and does not increase regardless of internet speed or screen resolution. I would appreciate any ideas that people might have how to solve it. Perhaps there's a way to downgrade Zoom?

keren_sky commented on 2021-03-13 19:52 (UTC)

@hv15 thanks for this. Here is hoping Zoom keeps maintaining the alsa backend.

ferretwithaberet commented on 2021-02-23 11:10 (UTC) (edited on 2021-02-23 11:39 (UTC) by ferretwithaberet)

On Manjaro Linux with KDE Plasma 5.20.5, when trying to login using gmail or trying to join meetings by link, it fails because it cannot find application handler for Zoom:

Could not find any application or handler for zoommtg:// 

Edit: Fixed by replacing ~/.local/share/applications/Zoom.desktop with /usr/share/applications/Zoom.desktop

daze commented on 2021-02-16 21:41 (UTC)

I had problems with microphone being jittery, to a degree that it was hardly usable. It might have been related to pipewire and/or pipewire-pulse with PulseEffects enabled. Bypassing PulseEffects didn't work, though.

What helped me was installing pipewire-alsa and setting in ~/.config/zoomus.conf, as hv15 suggested. Now the mic is usable again :)

misharash commented on 2021-02-10 21:11 (UTC) (edited on 2021-02-10 21:15 (UTC) by misharash)

Using "GNOME on Xorg" I suddenly found out that I can't share screen (neither full desktop nor specific window, in both cases only the wallpaper was seen zooming in and out or with glitching window top bar). Switching to "GNOME" (Wayland) solved this.

sscp commented on 2021-02-08 03:01 (UTC) (edited on 2021-02-08 03:01 (UTC) by sscp)

Hi all, I just rebooted my machine after updating and zoom is majorly glitching out. Specifically clicking on buttons in the GUI doesn't update the window unless I click on the profile or resize the window. I'm using i3 so perhaps that's related. I suspect it's due to updates in either the kernel or other dependencies, as downgrading zoom to the original version does nothing. Has anyone else encountered this problem?

edh commented on 2021-02-07 18:33 (UTC)


I updated the checksum with the release and can validate that it still corresponds to the package that is distributed at . Please check your network configuration!

kouros17 commented on 2021-02-07 17:56 (UTC) (edited on 2021-02-07 17:58 (UTC) by kouros17)

I cant build 5.5.2-1 because

==> ERROR: One or more files did not pass the validity check!

bhoney commented on 2021-02-07 14:21 (UTC) (edited on 2021-02-07 14:48 (UTC) by bhoney)

My issue right now is ever since 5.5.0-1 build when I request to control a shared session, my session instantly locks up audio cuts out and the session closes. Seems the two updates after have not addressed. Any advice from anyone else that has ran into this? What I have done in the meantime is downgrade back to 5.4 and all is good again.

jprobichaud commented on 2021-02-05 15:29 (UTC)

Since the last 5.4 release (and with both 5.5 ones), I have the problem where whenever I share my screen or an application or the zoom whiteboard, the sharing control disappear after few secs and I'm stuck sharing the same thing until someone else "steals" screen sharing. Anyone got this too?

My laptop has an nvidia card and I'm running X + KDE.

watdryhope commented on 2021-02-02 17:35 (UTC)

new update includes 'hide self view' option. however, when I click it all the others in the zoom disappear and I only see myself and can't get back to gallery view. Any ideas?

speedytux commented on 2021-01-31 22:08 (UTC)

No ALT-Y here also

ikke commented on 2021-01-31 10:14 (UTC)

Is anyone able to use the "raise hand" function? For me, the buttons for this are missing and alt+y is not working either.

Ta180m commented on 2021-01-29 15:04 (UTC) (edited on 2021-02-02 18:51 (UTC) by Ta180m)

Deselecting "Automatically join audio by computer when joining a meeting" in the Zoom settings seems to help as well with the issue of getting stuck on connecting when joining meetings.

Edit: This doesn't help and I still get this issue a lot.

orgarten commented on 2021-01-28 11:56 (UTC)

Does screen sharing work for anybody under Wayland? Supposedly, it is supported on Arch Linux but when I try to share my screen all I get is an message telling me that it only works for supported OSes (Fedore, Ubuntu, .. Arch Linux ..)

spsf64 commented on 2021-01-21 14:44 (UTC)

@archmylinux: the "orig" is the source file. Looks like you are using a helper, try to build manually. Ie makepkg -crs then pacman -U.

archmylinux commented on 2021-01-21 14:31 (UTC)

When I try to install the package I get : error: 'zoom-5.4.57862.0110_orig_x86_64.pkg.tar.xz': duplicate target. And what do you know, in /tmp/packerbuild-1000/zoom/zoom/ I ls two packages : zoom-5.4.57862.0110-1-x86_64.pkg.tar.xz and zoom-5.4.57862.0110_orig_x86_64.pkg.tar.xz. So I pacman -U one and got it installed. Why is there two of them?

rugalx commented on 2021-01-20 19:11 (UTC)

I have the exact same problem as @smolloy and it's driving me crazy (or better, my colleagues). I also start to speak and it's very low and then it increases the volume.

I've already tried to change the config to but it's still not working, I've also disabled the mic auto regulation from zoom and set the noise reduction to low, but still nothing.

For now I've "fixed" it by using the web version and keeping the native client open at the same time to see the gallery, but that's quite impractical.

Ta180m commented on 2021-01-19 18:14 (UTC) (edited on 2021-02-02 18:51 (UTC) by Ta180m)

Changing the line to in ~/.config/zoomus.conf appears to have fixed my Zoom issues. Now Zoom doesn't get stuck on connecting and the audio doesn't get very quiet when joining breakout rooms.

Edit: This doesn't help and actually introduces a number of other problems.

rsaini commented on 2021-01-15 21:24 (UTC)

@Ta180m I'm not sure if you've tried this, but I had to make sure no other application had any hold over alsa before starting the zoom session. In my case, it was a jack server.

rsaini commented on 2021-01-15 21:22 (UTC)

Does anyone have a good workflow for helping zoom and jackd share alsa? Right now I'm closing my jack server and every program connected to it before each zoom session. Any insight would be greatly appreciated!

Ta180m commented on 2021-01-15 15:14 (UTC)

anyone else have an issue where some meetings get stuck at "Connecting" (if they are in a breakout room this only happens after you are accepted). I found some other person who has this issue on r/zoom but they are on windows

Does anyone have a reliable fix for this? It's really annoying and none of the solutions in the comments have worked for me.

smolloy commented on 2021-01-15 11:34 (UTC) (edited on 2021-01-16 09:33 (UTC) by smolloy)

Hi all, I just found out from my work colleagues that my Zoom audio has been behaving such that my audio always sounds very low to them when I first start speaking, then ramping up to a reasonable volume over a couple of seconds. Setting in ~/.config/zoomus.conf fixed this behaviour.

Edit: This "fix" didn't work. :( Any tips would be appreciated.

iSSAC_103 commented on 2021-01-01 10:30 (UTC)

5.4.57450.1220-1 Missing audio disconnect option after audio connect. In windows version it is present in lower left corner.

cjquines commented on 2020-12-29 16:46 (UTC)

Hm, Zoom is unusable for me. I join a meeting, it works fine for a few seconds, and then it crashes. Log says Something went wrong while running zoom,exit code is 139. I suspect it's a qt issue but I don't really know where else to ask help.

edh commented on 2020-12-23 16:53 (UTC)

@caleb Yes, I am well aware of that. But considering that they advertise the version the same, I would consider the change an artifact of the publishing process and will silently change it when zoom 5.5 comes out eventually.

alerque commented on 2020-12-23 16:28 (UTC)

but the way they advertise their version has changed and thus pacman will think it is actually lower.

This is what the PKGBUILD epoch property is for.

keiichiiownsu12 commented on 2020-12-22 21:25 (UTC)

Like a couple users below (@phillipchaffee), on v5.4.57450.1220-1: Zoom is usable. Audio is fine and does not stutter. However, periodically the video framerate will drop (around 1-2 fps), and the UI will stutter. E.g. if I move the mouse in the zoom window, the bottom bar (with share screen, etc.) will take 2-4 seconds to appear.

Zoom does not appear to use large amounts of CPU % or memory when this happens. Issue doesn't seem to affect windows or OSX users atm.

edh commented on 2020-12-21 20:05 (UTC)

@vesath Tanks I forgot about that :D

@NGr Yes, the version number increased but the way they advertise their version has changed and thus pacman will think it is actually lower.

NGr commented on 2020-12-21 19:51 (UTC)

@vesath The version number has increased.

vesath commented on 2020-12-21 19:48 (UTC)

If you're taking the version number from 5.4.56259.1207 down to 5.4.7 you must add 'epoch=1' so that pacman will know this is actually an upgrade.

mvdan commented on 2020-12-14 16:10 (UTC)

The latest version, 5.4.56259.1207, unfortunately still crashes on me if I open a link directly. The workaround that others mentioned about opening Zoom separately first and logging in appears to do the trick sometimes.

iambeard commented on 2020-12-02 16:07 (UTC)

@Nikita790 I find that clicking links to launch zoom leaves it spinning to connect. Open zoom separately first, sign in if you do that, then click whatever join links. No idea what the issue is, but I'm guessing it's some sort of async loading thing that launching zoom first resolves.

darose commented on 2020-11-30 19:13 (UTC)

Seems to hog a good bit of CPU. I'm not sure if that's just this version, or all versions.

phillipchaffee commented on 2020-11-30 19:08 (UTC)

Is the newest release just completely unusable for anyone else? It technically runs but is insanely slow for me. commented on 2020-11-26 08:33 (UTC)

Does anyone have an issue that sometime the audio is extremely small when joining a new room or breakout room? I can only fix it by leave the room and comeback, sometime several times.

Nikita790 commented on 2020-11-19 16:28 (UTC)

anyone else have an issue where some meetings get stuck at "Connecting" (if they are in a breakout room this only happens after you are accepted). I found some other person who has this issue on r/zoom but they are on windows

edh commented on 2020-11-17 10:43 (UTC)

@daniell You are at the wrong AUR page for the zoom-system-qt package.

uwinkelvos commented on 2020-10-30 10:56 (UTC)

if you have problems with broken autoscaling, this can be disabled: ~/.config/zoomus.conf: autoScale=false

rgambord commented on 2020-10-27 20:28 (UTC)

@je-vv I use jack2 with alsa-plugin and apulse for programs that don't support jack. I can quit jack2 and zoom will work with alsa directly (although alsa does not support my HDMI out, so I only have mic) but it won't work when jack2 is running.

Eothred commented on 2020-10-13 13:25 (UTC)

Regarding SSO, for me it was Firefox containers blocking me (I think). I did not have the "zoom domain" as "always open in work container", however I had our company SSO login page on that list. So by jumping from a "no container" to my work container during log in, I think the app opening feature failed.

nasci commented on 2020-10-10 08:34 (UTC)

@malexan I normally use picom so I installed xcompmgr but it's no different. When opening the whiteboard picom gives a bunch of warnings and errors, like "flags cleared on a destroyed window" and "failed to query info". Not sure if that's related.

MasterOne commented on 2020-10-09 08:53 (UTC)

@caleb, no that's not it. As said, everything was working just a few days ago, but the system update that was performed yesterday obviously broke something, because reverting to a previous system snapshot using Timeshift solved the issue.

alerque commented on 2020-10-09 08:31 (UTC) (edited on 2020-10-09 08:33 (UTC) by alerque)

@MasterOne I've seen a similar crash not just recently but frequently across many versions in the last few months. The easiest way I found to avoid it is to make sure and enter the meeting ID with no spaces. I found copy and pasting the meeting ID from Zoom emails with their space separated groupings frequently caused crashes, but if I either type in or paste in a meeting ID with no spaces it us more stable.

Another one for me (because I‌ frequently type on a non-English keyboard layout and switch layouts to type digits) is that swapping keyboard layouts using a keyboard shortcut (and the resulting momentary switch of input focus) sometimes crashed the join meeting box too. If I switch to a layout that I can type Arabic numerals first, then hit join and enter the meeting ID it is less likely to crash.

Neither of these things are unique to recent Zoom versions. I find the zoom-system-qt package works better and crashes less frequently, but both are deeply troublesome. The upstream software quality is just abysmal and there isn't a lot the Arch packaging can do to fix it.

MasterOne commented on 2020-10-09 07:19 (UTC)

A system update performed on one of my laptops yesterday causes Zoom to crash after the Meeting ID and Passcode has been entered. Anyone else experiencing such a problem?

P.S. Sorry for being vague with no exact error diagnoses, but the problem was discovered yesterday at the beginning of a Zoom meeting and I had to get it going quickly again, so I just used Timeshift to revert to an earlier snapshot. I'm using GNOME on that laptop, if that matters.

je-vv commented on 2020-10-06 22:50 (UTC)

@rgambord, do you use alsa stand alone without pulse, or do you use pulse. It sounds you're using the former. Alsa stand alone without pulse works fine, and there's really no much to do on such a system. Just make sure your system audio works fine before using zoom, perhaps adjusting its configuration with alsactl. The Arch wiki for alsa is good: "". There can be some audio channels muted, and then you have to unmute them. Make sure to review capture as well, so you can set things up for the mic. To test sound, prior to using zoom, aplay can help, and to test the mic, then arecord can help, but you can find that on the wiki. If sounds works fine with alsa, then zoom should work great with no particular settings for it...

rgambord commented on 2020-10-06 22:29 (UTC) (edited on 2020-10-06 22:29 (UTC) by rgambord)

I tried @hv15's fix with JACK and alsa-plugins. No luck. Neither does aplay work.

electricprism commented on 2020-09-25 20:53 (UTC)

I noticed many zoom-related processes running in the background after zoom closes, can anyone confirm?

watdryhope commented on 2020-09-23 11:56 (UTC)

hi, just wondering where the functionality of 'hiding self view' went and how I can bring it back.

dpriskorn commented on 2020-09-22 21:18 (UTC)

@edh, I installed it on my 64-bit system instead, I could not get it to stop segfaulting on x86.

malexan commented on 2020-09-22 09:09 (UTC)

@AsukaLSoryu, @nasci, if you have an issue with annotation tools try to install and run xcompmgr.

AsukaLSoryu commented on 2020-09-14 19:34 (UTC)

Having the same issue where I have no annotation tools. Also, as of the latest release I am no longer able to input Japanese with fcitx.

Nora commented on 2020-09-10 19:38 (UTC)

Not going lie im kinda shocked this isnt in community by now

keiichiiownsu12 commented on 2020-09-03 02:29 (UTC)

@keiichiiownsu12 @luuuciano

Thank you both for your help. That seemed to fix the issue!

MastroRuggiero commented on 2020-09-02 20:58 (UTC)

@keiichiiownsu12 I was having the same issue with i3wm. The fix suggested by @luuuciano worked for me :)

luuuciano commented on 2020-09-02 19:53 (UTC)

When that happened I solved it by doing what is commented here

"Another fix for the scaling issue is to set autoScale=false in ~/.config/zoomus.conf."

keiichiiownsu12 commented on 2020-09-02 18:57 (UTC)

When using zoom on my laptop screen, the UI is "enlarged": buttons and other UI elements are roughly 2 to 3 times their conventional size. When used on my larger, but same resolution, screen, the UI displays a more conventional size. See here for visual comparison. I am using KDE Plasma DE.

Is there a setting that controls this? I have been having trouble finding others with a similar issue. . .

edh commented on 2020-09-01 09:26 (UTC)

@egils Do you actually use an i686 or Pentium4 platform or is this just an academic question? I am willing to add those platform though only if they are actually used. I would consider both of them to be deprecated and would highly recommend you to upgrade your system.

dpriskorn commented on 2020-09-01 07:37 (UTC)

Zoom also supports i686 and pentium4, could you add that to the pkgbuild? I can test it if you want.

nasci commented on 2020-08-25 02:06 (UTC)

@Novite I'm having the same issue with annotation tools not appearing (I can only use the pen)... I'm not sure if this is a universal issue or if the toolbar just isn't drawing due to an incompatibility with my picom/i3wm setup. If anyone else can confirm whether the annotation tools are available when sharing the screen/whiteboard that would be great.

vatai commented on 2020-08-02 11:13 (UTC)

On a running meeting the Participants window is completely empty if undocked/pop out. Can somebody confirm this bug. I have it on my two pc. On both it is the same.

+1 from me on this

HarryH commented on 2020-07-31 13:42 (UTC) (edited on 2020-08-06 07:39 (UTC) by HarryH)

On a running meeting the Participants window is completely empty if undocked/pop out. Can somebody confirm this bug. I have it on my two pc. On both it is the same.

Addendum at 2020-08-06: This bug was solved in version 5.2.440215.0803-1.

Novite commented on 2020-07-30 04:25 (UTC)

I've got a problem: There is no annotation tools on whiteboard when screen shared. My computer works on archlinux + Gnome 3.36.4

alerque commented on 2020-07-24 14:53 (UTC)

@MastroRuggiero You might try the zoom-system-qt package. I use that with Awesome+compton across dual monitors and can screen share app windows with a cursor coming across.

MastroRuggiero commented on 2020-07-23 03:09 (UTC)

Hi, I'm having issues with screen sharing: the other participants in the meeting cannot see my cursor. I'm using i3wm and I need the cursor to be visible in a libreoffice impress slideshow. I've tried two different X compositors (compton and xcompmgr). Anyone has a clue what may cause this problem?

whitterbit commented on 2020-07-14 20:52 (UTC)

Zoom has been unusable for me for the past couple weeks. I have a 4 monitor setup with a 32:9 ultrawide, 2 1080p and 1 1440p.

When I launch the app, it takes longer than usual and fills all 4 monitors with a black screen. When I unfloat it I can only see a black window and a blue one eventually appears also. I cannot access any controls and the tray icon has stopped working as well. I've tried a couple of the scaling fixes but they don't seem to work. It's a bummer because zoom used to work great for me, and now I have to connect through the browser.

edh commented on 2020-07-14 16:27 (UTC)

@ludenticus Can you elaborate a little on to why the string should be lower-case? I was of the impression that as long as the string is the same for all desktop entries than grouping works fine.

ludenticus commented on 2020-07-14 16:16 (UTC)

Zoom.desktop should use lowercase in StartupWMClass=zoom (instead of StartupWMClass=Zoom).

inverse commented on 2020-07-10 08:56 (UTC) (edited on 2020-07-10 09:00 (UTC) by inverse)

Recently I noticed that this app has scaling issues on my dual monitor setup. The secondary display is fine, however the primary is blown up.

Adding QT_SCALE_FACTOR=0.5 fixes it for the primary but when I drag to the secondary it's scaled tiny.

Both screens are 1920x1080 - One is the laptop and the other is a secondary display in portrait.

-- Applying this fixed it for me

captn3m0 commented on 2020-07-09 10:46 (UTC) (edited on 2020-07-09 10:49 (UTC) by captn3m0)

Is anyone else facing segfaults with the Zoom binary? Complete error log: The following line repeats more than 10k times:

load glyph failed err=24 face=0x55afbb106260, glyph=9

Edit: Running with env QT_SCALE_FACTOR=0.9 /usr/bin/zoom seems to be fine. I think its a missing font with my Qt config.

joehillen commented on 2020-07-08 20:16 (UTC)

@mercutio Thank you. That's very helpful.

Alternatively, it can be fixed by setting the QT_SCALE_FACTOR environment variable rather than editing the binary file. See


I created a wrapper script in my ~/.bin that runs:

env QT_SCALE_FACTOR=0.5 /usr/bin/zoom

mercutio commented on 2020-07-07 12:05 (UTC)

If anyone else has trouble with the GUI being scaled way to high (looking quite blurry on my 1080p display), you can use this fix:

Based on this fix for the zoom-snap package:

For a simple one off fix you can also run sudo sed -i s/T_AUTO_S/XXXXXXXX/g /opt/zoom/ZoomLauncher

kpetremann commented on 2020-07-03 11:10 (UTC)

5.1.418436.0628-1 is having issue with SSO on my side (running Manjaro, kernel 5.6.16-1).

Zoom client is being signed out after 30 sec when connected to a meeting.

FYI: last of 5.0 is working well

ElijahLynn commented on 2020-07-02 18:34 (UTC) (edited on 2020-07-02 18:34 (UTC) by ElijahLynn)

Anyone know why Zoom disables a Wacom touchscreen only in Zoom (Thinkpad X1 Yoga)? And is this something I can reactivate?

image28 commented on 2020-07-02 03:34 (UTC)

@dustmann you could use ffmpeg to capture the window then play it through a video loopback device

dustmann commented on 2020-07-02 03:19 (UTC)

Does anyone have a trick to get zoom to allow me to only share a specific application? I only have options to share my full desktop or the whiteboard using Gnome / wayland fwiw.

edh commented on 2020-06-30 14:25 (UTC)


Have a look at the PKGBUILD. It will become clear if you just take a glance.

In short: This PKGBUILD is just a thin wrapper around the official Arch package which zoom provides upstream (denoted by the _orig suffix). The main reason for this package's existence is to fix some dependencies and to make it easier for users to install.

Hence, it is very odd that one should work and not the other! I guess you are missing some optional dependency for your setup to work and zoom happens to flags the same dependency as non-optional.

colinkeenan commented on 2020-06-30 14:17 (UTC)

Why does this package build zoom-...-x86_64.pkg.tar.xz AND zoom-..._orig_x86_64.pkg.tar.xz? Only the "orig" works for me. Do some people need the other for some reason? Why?

edh commented on 2020-06-24 12:51 (UTC)

@hv15 Thanks a lot for digging into it. I was not aware of the fact that running zoom without pulseaudio-alsa is officially supported. I will flag the package as optional with the next release.

@je-vv Sorry for taking so long to only now do what you requested months ago. To be clear, the question of whether to mark pulseaudio-alsa as optional was more about whether it being officially supported.

seb-berger commented on 2020-06-24 07:37 (UTC)

Scaling issues: None of the recommendations below fully worked for my machine. Still, I apparently fixed the multi-screen scaling problems using QT_SCREEN_SCALE_FACTORS="1;0.5" /usr/bin/zoom. (The environment variable takes a list of scale factors, one per screen.)

je-vv commented on 2020-06-23 23:58 (UTC)

@hv15, you don't need any form of apulse to use zoom without pulse. Just edit the PKGBUILD and remove pulseaudio-alsa as a dependency, without tweaking anything else from pulse. That has been working for me all along, though I need to remember any time upgrading zoom to remove that dep. If you get pulse installed and the pulseaudio-alsa plugin installed, I'd guess apulse won't help...

I requested the maintainer to remove it from a hard dep, and have instead as a optional dep (indicating it's required for pulse use, or something similar), but he argued majority of people uses pulse, but I'd guess that breaks non pulse users.

hv15 commented on 2020-06-23 10:43 (UTC) (edited on 2020-06-23 10:43 (UTC) by hv15)

Hi all, for the last 3 months I've been unable to get any sound/microphone in Zoom. I use (a differently packaged form of apulse), as an alternative to the full pulseaudio server. Initially (3 months ago) this worked fine, at which point it didn't (I don't know at what version of Zoom this started to fail, haven't checked). Within my logs it was clear that this has something to do with Zoom not being able to find/use pactl (which is part of libpulse, but not part of apulse).

Well, doing some googling I found that Zoom actually supports ALSA (since version 2.0.57232.0713, see There is not other documentation about this that I could find, but when I looked into ~/.config/zoomus.conf I saw there is a line with Again no documentation on this, so I played with it and when I set it to Zoom started using ALSA directly, and now I have working audio/microphone in Zoom! I hope people find this useful :)

EDIT 1: typos

ubmarco commented on 2020-06-18 18:05 (UTC)

Another fix for the scaling issue is to set autoScale=false in ~/.config/zoomus.conf. It is set to true by default. This works for me on monitors with different DPIs.

Credits to this guy.

GAthan commented on 2020-06-18 08:43 (UTC)

ubmarco - thank you - this worked (so far) for me.

alerque commented on 2020-06-18 08:27 (UTC)

@ubmarco That is a function of old QT functions not handling per-monitor DPI settings, and not an issue with this packaging.

ubmarco commented on 2020-06-18 06:53 (UTC) (edited on 2020-06-18 08:05 (UTC) by ubmarco)

Starting zoom from the command line with QT_SCALE_FACTOR=0.5 zoom fixes the issue partially for me. I have a laptop and a 1080p monitor connected. On laptop it looks normal using above hack, when moving the app to the external monitor it's big however.

Edit: I just checked and my external HDMI monitor reports a wrong physical screen size (xrandr shows 160mm x 90mm), so maybe that's why it is not working there.

alerque commented on 2020-06-17 21:31 (UTC)

HIDPI monitor detection has changed several times between versions. That is an upstream Zoom issue not an issue with this package per se. Most recently they went from not detecting HiDPI at all to applying twice too much scaling when they do. I've been able to work around it locally by launching while reporting different DPI settings through Xft configuration.

je-vv commented on 2020-06-17 21:12 (UTC)

Besides the big uncontrolled size, it breaks for me, using fluxbox as WM and LXQt as DE. Only way to prevent breakages and avoiding the huse size is reverting to prior version, which was still 5.0, while latest version breaking is 5.1..

nonZero commented on 2020-06-17 19:58 (UTC)

I have issues controlling Breakout Rooms - all popups disappear immediately ( ). This is not a new issue. I am using Gnome. Can someone else confirm it is a linux/arch/gnome issue?

xdevnull commented on 2020-06-17 18:50 (UTC)

The interface, both the main conferencing one as well as the client with login, settings, etc. has increased in size, as if it has been scaled up for some reason. This is on Plasma.

luuuciano commented on 2020-06-17 18:29 (UTC)

It could be possible that in the latest update my zoom went really BIG? I mean, it is like all its interfase is zoomed in... and because that does not fit in the screen, it is barely usable

SpineEyE commented on 2020-06-17 15:11 (UTC)

Actually the crash was partly my fault. I had switched to Xorg from Wayland and still had set QT_QPA_PLATFORM=wayland.

I can run it via terminal, e.g.: QT_QPA_PLATFORM="" zoom

image28 commented on 2020-06-17 14:35 (UTC)

Made a PKGBUILD for a stripped version, doesn't work. Doing something wrong with the package build. Firstly I can't get the sha512sum I made of files to verify.

Haven't worked out all the deps so you may have to ldd the binary, and pacman -Fx the missing libs to find the right deps to install. Also it riquires files from qtdesigner.

Something like this

for d in ldd zoom | awk -F' ' '{print $3}'; do PACKAGES="$PACKAGES pacman -Fx "$d" | rev | awk -F'' '{print $2}' | rev"; done; pacman -S "$PACKAGES"

alerque commented on 2020-06-17 11:44 (UTC)

If it's not too much trouble @SpineEyE or @Revelation60 I would be interested in knowing whether the zoom-system-qt version of this causes the same core dump. Neither package does for me right now, but it looks like the problem you are seeing may be in the bundled QT libraries, so you might be able to side-step it by using the substituted Arch libraries instead.

Revelation60 commented on 2020-06-17 11:27 (UTC)

It's also core dumping for me with the latest version.

SpineEyE commented on 2020-06-17 09:24 (UTC) (edited on 2020-06-17 09:28 (UTC) by SpineEyE)

No one gets a coredump? It started with the latest version.

Message: Process 3044 (zoom) of user 1000 dumped core.

            Stack trace of thread 3044:
            #0  0x00007f78ba222355 raise ( + 0x3c355)
            #1  0x00007f78ba20b853 abort ( + 0x25853)
            #2  0x00007f78ba80cb5e _ZNK14QMessageLogger5fatalEPKcz ( + 0x93b5e)
            #3  0x00007f78bc085d6d _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv ( + 0x128d6d)
            #4  0x00007f78bc085efd _ZN22QGuiApplicationPrivate21createEventDispatcherEv ( + 0x128efd)
            #5  0x00007f78ba9f9bab _ZN23QCoreApplicationPrivate4initEv ( + 0x280bab)
            #6  0x00007f78bc08794b _ZN22QGuiApplicationPrivate4initEv ( + 0x12a94b)
            #7  0x00007f78bc8666e9 _ZN19QApplicationPrivate4initEv ( + 0x1586e9)
            #8  0x000055b3ad630e72 n/a (zoom + 0x367e72)
            #9  0x00007f78ba20d002 __libc_start_main ( + 0x27002)
            #10 0x000055b3ad6c5435 n/a (zoom + 0x3fc435)

bbaserdem commented on 2020-05-20 01:25 (UTC) (edited on 2020-05-20 01:25 (UTC) by bbaserdem)

A little nitpicky perhaps; but the provided desktop file has Icon=Zoom.png which causes the icon detection to fail. If it's switched to Icon=Zoom; the icon is correctly guessed. (XDG application does not need file extension unless the icon is a hard link. In this case it's not; the Zoom icons are unpacked to directories that allow them to be autodetected by the system.)

The patch would be a one-liner sed -i 's|Zoom\.png|Zoom|g' "${pkgdir}/usr/share/applications/Zoom.desktop"

bbrks commented on 2020-05-19 16:15 (UTC)

The current version (5.0.408598.0517-1) seems to be stable for me now.

I had tried previous suggestions of upgrading mesa, etc. and still experienced crashing on every version I tried prior to this.

sross commented on 2020-05-19 16:14 (UTC) (edited on 2020-05-19 16:14 (UTC) by sross)

I was having the freezing issue with SSO and after attempting various solutions, including the pinned ~/.config/zoom.conf suggestion, deleting zoom data directory worked:

cd ~/.zoom
rm -rf data
mkdir data

restart zoom, log into sso, all is well.

ElijahLynn commented on 2020-05-18 17:40 (UTC)

I just had another crash this morning right in the middle of an important discussion, and normally I can't restart it and have to logout/in again. I instead checked for an update, which there was, installed it in 20 seconds, and was back in the meeting with no crashes. Fingers crossed but this latest release today may have fixed it!

gps1539 commented on 2020-05-18 16:07 (UTC)

Also ran into this issue over the last week or so. This morning I could not start zoom after 20+ attempts. My setup has mesa 20.0.7-2 and zoom was at 5.0.408598.0517-1. I found that just reverting zoom to 5.0.398100.0427-1 works for me.

Our company IT dept, recently advised users to not update zoom 5.0.4 as they where seeing issues on Window and MACs.

wlritchi commented on 2020-05-15 21:32 (UTC)

Regarding the recent segfaults: I tried downgrading zoom with no luck, then I discovered it's actually all apps trying to access the webcam that segfault. Blame appears to lie with mesa 20.0.7-1. mesa 20.0.7-2 fixes the problem for me.

hamidzr commented on 2020-05-15 19:19 (UTC)

Yeah just z few comments below. I'd suggest sticking with 0427 build for now

ElijahLynn commented on 2020-05-15 19:16 (UTC) (edited on 2020-05-15 19:20 (UTC) by ElijahLynn)

Been getting a bunch of crashes (segfaults) with the latest Zoom AUR. Anyone else getting these? I haven't looked too deep yet. When it happens I cannot restart it, it keeps crashing, I have to logout and back in again. I'll try a system update soon I suppose.

journalctl --catalog --pager-end | grep zoom

May 15 11:30:48 archlinux Zoom.desktop[156802]: ZoomLauncher: new dump generated from pid 156847, path: /home/elijah/.zoom/logs/762c92de-c143-473c-d46a6fa3-4a494e64.dmp
May 15 11:30:48 archlinux audit[156847]: ANOM_ABEND auid=1000 uid=1000 gid=985 ses=3 pid=156847 comm="zoom" exe="/opt/zoom/zoom" sig=11 res=1
May 15 11:30:48 archlinux kernel: zoom[156847]: segfault at 0 ip 0000561c1da316be sp 00007ffe9d664ec0 error 4 in zoom[561c1d36c000+3386000]
May 15 11:30:48 archlinux kernel: audit: type=1701 audit(1589567448.767:599): auid=1000 uid=1000 gid=985 ses=3 pid=156847 comm="zoom" exe="/opt/zoom/zoom" sig=11 res=1
May 15 11:30:54 archlinux systemd-coredump[158187]: Process 156847 (zoom) of user 1000 dumped core.
                                                    #0  0x0000561c1da316be n/a (/opt/zoom/zoom + 0x6c56be)
-- Subject: Process 156847 (zoom) dumped core
-- Process 156847 (zoom) crashed and dumped core.
May 15 11:30:54 archlinux Zoom.desktop[156835]: sh: line 1: 156847 Segmentation fault      (core dumped) /opt/zoom/zoom ""
May 15 11:30:54 archlinux Zoom.desktop[156802]: zoom exited normally.
May 15 11:30:54 archlinux Zoom.desktop[156802]: Something went wrong while running zoom,exit code is 139.

bbaserdem commented on 2020-05-15 16:54 (UTC) (edited on 2020-05-20 01:21 (UTC) by bbaserdem)

I can't test audio; and audio is not working for me. Does anyone have any ideas what's the issue? (Solved: kernel update but did not reboot; for some reason it caused issues. Was fine after reboot.)

angelo81523 commented on 2020-05-12 08:27 (UTC)

if zoom is not starting, check if the git downloaded folder zoom is in the path /home/<whatever>/zoom, after install delete it or move it to another path like Downloads

alphazo commented on 2020-05-06 15:15 (UTC)

same as @hamidzr. Lots of seg faults with 5.0.399860.0429-1. Sometimes it takes me 10 attempts before I can get it to work.

matthias commented on 2020-05-05 12:31 (UTC)

@hamidzr: Me too. Seem to run fine for a while and then just crashes. Not sure that there is anything specific that I do other than listen/look/talk...

hamidzr commented on 2020-05-05 04:29 (UTC)

on version (5.0.399860.0429-1) I get a segfault when running zoom. anyone else running into this? works

async commented on 2020-04-27 23:41 (UTC)

I'm not sure if this is related to some of the recent discussions about pulseaudio, ALSA, and apulse, but I've noticed on two of my computers that any notification sounds happening from any other app cause a Zoom meeting's audio to temporarily cut out for about 3 seconds, and then playback quickly as Zoom tries to catch up. I'm on Manjaro Gnome (not sure about other DEs).

This happens every time I receive a message in Slack, for example. It also happens if I open a webpage that has any sort of autoplaying content. Could it be that these are because of recent changes in this package?

For reference, I did not have this issue until relatively recently.

dno commented on 2020-04-26 15:43 (UTC)

I am able to use this package without pulseaudio-alsa installed. Not sure if it's just no longer needed or should be optional.

nonZero commented on 2020-04-23 17:51 (UTC)

On Zoom 3.5.392530.0421 + Gnome 3.36.1 on X11, trying to manage breakout rooms is very buggy: After creating the rooms moving participants between rooms and broadcasting messages is done through small popup windows - however those windows disappear immediately after they appear and cannot be used. I wonder if this is an Arch, Gnome or X11 specific problem or a generic Linux client problem.

csirek commented on 2020-04-21 08:30 (UTC)

SSO login failing problem present in 3.5.385850.0413 too (if i try to log in i just got back a long random char list in a new window and thats all. The "embeddedBrowserForSSOLogin=false" workaround is working.

image28 commented on 2020-04-18 09:08 (UTC)

@edh and other responders, just tested, after 4 hour of failing to get effectv working through a v4l-compat layer with zoom, I decided to either lookup my previous attempt to port it to v4l2, or re-port it entirely with my recent improved understanding of automation and regex.

Zoom without the funky effect worked after testing, and I feel a little more secure using it.

Little bit tipsy, sorry, had to retype the first part of this.


Whats up with these crypto related build system forks? Downloading 1-3gb to compile something that could be in the 1-2kb range, source and binary!

gash commented on 2020-04-18 08:28 (UTC) (edited on 2020-04-18 16:16 (UTC) by gash)

Can not run installed package. First run after successful install freeze computer until hard reset. Next and other runs after reset program immediately quits without any effect.

edh commented on 2020-04-15 21:34 (UTC)

@image28 That's a really nice project and is an intriguing option for this package as well.

For now though, I will probably stick to the current upstream version as they specifically provide an Arch Linux package that does not build against system libraries. I don't want to risk that some library calls change slightly by updating to system libraries and break zoom.

image28 commented on 2020-04-15 16:48 (UTC)

Recreated the zoom package, reused the filename from the PKGBUILD file. Stripped the shared libraries from the package. Then used ldd to figure out what was missing. Had to add qt designer for it to start after that.

Result is a 20mb package that uses the system libraries, rather than a ~260mb package.

Seems a lot quicker, and more secure.

Binary is still 50mb, with a 2010 version of zlib statically compiled in :(

mattbass commented on 2020-04-10 18:28 (UTC)


For some reason my USB Blue Yeti microphone is recognized by zoom as an audio input option, but it's not actually picking up any sound.

In discord, audacity, and all other programs it seems to be recognized and work fine, but for some reason zoom is having issues.

In pavucontrol, the microphone is showing that it's picking up sound and it's set as the default/fallback input device.

Anyone else having a similar issue?

ypoluektovich commented on 2020-04-10 16:07 (UTC)

@edh That would be an acceptable outcome. I'll go post about it in apulse's comments, I guess.

edh commented on 2020-04-10 13:52 (UTC) (edited on 2020-04-10 13:53 (UTC) by edh)

@ypoluektovich Considering that apulse is a pulseaudio emulator for ALSA, I suppose it makes more sense to let apulse provide pulseaudio-also instead of changing every package that depends on the latter.

ypoluektovich commented on 2020-04-10 11:52 (UTC)

Please add an option to not install pulseaudio-alsa - it can be replaced with apulse.

hmenke commented on 2020-04-03 23:27 (UTC)

@electricprism The vulnerability you are talking about is in the preinstall script of the macOS installer (see here for an in-depth analysis). This PKGBUILD is therefore immune to this particular form of privilege escalation. Nevertheless the Linux version of Zoom is still vulnerable to all other flaws that have been detected recently, such as information leak of email addresses, unauthorized sharing of personal data with Facebook, or the fake end-to-end encryption. However, running Zoom in flatpak or another container solution will not protect you from these vulnerabilities because they are either conceptual or server-side flaws. The only way to mitigate these is to not use Zoom.

electricprism commented on 2020-04-03 19:58 (UTC)

Due to backdoor root access on MacOS I suggest others consider using a flatpak or other containerized version of this:

"The application is installed without the user giving his final consent and a highly misleading prompt is used to gain root privileges. The same tricks that are being used by macOS malware."

edh commented on 2020-04-03 11:40 (UTC)

@hmenke Thanks a lot for the input! I will add those dependencies with the next release.

hmenke commented on 2020-04-02 23:06 (UTC) (edited on 2020-04-02 23:19 (UTC) by hmenke)

I just set up Zoom in a systemd-nspawn container and discovered the following missing dependencies:

  • libxcursor: Zoom will just refuse to start with

    error while loading shared libraries: cannot open shared object file: No such file or directory
  • libxkbcommon-x11: Without this, keyboard input will just be ignored. There is a little hint in the log:

    Qt: Failed to create XKB context!
  • ttf-dejavu: Without this, Zoom just won't show any fonts. A different font would probably do as well, so depending on the ttf-font metapackage might be sufficient.

Gregoire commented on 2020-04-02 22:18 (UTC)

@archmylinux : It's what I did to install it (and it works great). (It's what I mean by at hand, I would like to understand how to correct the PKGBUILD for it to compil and install directly, I have done quiete a few try but none worked).

Thank for you answer.

archmylinux commented on 2020-04-02 22:04 (UTC)

@Gregoire, try ⇒ sudo pacman -U /tmp/packerbuild-1000/zoom/zoom/zoom-notTheOriginal.pkg.tar.xz

joaommartins commented on 2020-04-02 19:48 (UTC) (edited on 2020-04-02 20:09 (UTC) by joaommartins)

Hi, I've been trying to use Zoom on my PC, but every time I launch the program, my pc just crashes, no warning, nothing. I'm still unable to understand with is this happening. The screen just turns black, and I can't do anything but to force shutdown. Is there anyone who had this identic issue or knows how to fix this? I've been forced to use the browser version and it really sucks :(

(EDIT) I tried running from the command line and I was only able to capture the log with my phone before it crashed my pc. Hope it helps:

korikori commented on 2020-04-02 13:45 (UTC)

Can you confirm that pulseaudio is really required as a dependency? When the pulseaudio socket is enabled, my microphone actually works worse than when it's disabled.

Gregoire commented on 2020-04-01 08:56 (UTC) (edited on 2020-04-01 09:01 (UTC) by Gregoire)


I have a strange problem :

packer-aur -S zoom

Aur Targets    (1): zoom

Proceed with installation? [Y/n]

Edit zoom PKGBUILD with $EDITOR? [Y/n]

==> Making package: zoom 3.5.374815.0324-1 (Wed 01 Apr 2020 10:52:39 AM CEST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading zoom-3.5.374815.0324_orig_x86_64.pkg.tar.xz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  
                                 Dload  Upload   Total   Spent    Left  
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 69.3M  100 69.3M    0     0  16.4M      0  0:00:04  0:00:04 --:--:-- 
==> Validating source files with sha512sums...
    zoom-3.5.374815.0324_orig_x86_64.pkg.tar.xz ... Passed
==> Extracting sources...
  -> Extracting zoom-3.5.374815.0324_orig_x86_64.pkg.tar.xz with bsdtar
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issues...  
==> Creating package "zoom"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: zoom 3.5.374815.0324-1 (Wed 01 Apr 2020 10:53:19 AM 
loading packages...
error: 'zoom-3.5.374815.0324_orig_x86_64.pkg.tar.xz': duplicate target

I could go by hand to install it anyway but I don't understand what's wrong here...

Any idea ?

Thank you very much.

zethexx commented on 2020-03-31 22:24 (UTC)

Anyone been able to figure out why GIF's do not auto play in Zoom on Arch Linux? I have to click on it to open it up in Image Viewer. Other distros work out of the box. Is there an additionaly dependency I might need to install?

jonathanl commented on 2020-03-30 21:04 (UTC)

I just solved my below issue. For anyone who finds this the issue is that I had to uninstall xf86-video-intel it was causing issues with my intel gpu.

jonathanl commented on 2020-03-30 20:15 (UTC)

The zoom app seems to not be re-rendering for me. It seems to be responding to events i.e. clicking on 'sign in', but only re-renders when I open a secondary window (the 'about' window). I am running arch (5.5) using xmonad and LG3D. If anyone has any ideas that would be that would be really helpful!

p.s. when I open zoom from the commandline the only error I see in the output is this, but it seems minor

qt.svg: link image0 hasn't been detected!
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument
Error: Send error, 22 Invalid argument

edh commented on 2020-03-27 10:09 (UTC)

@natrio Officially it is listed as dependency.

natrio commented on 2020-03-27 09:34 (UTC)

"pulseaudio-alsa" dependency is not nesessary. The Zoom can work with Pulseaudio without ALSA, and it also can work with ALSA without Pulseaudio.

losbehamos commented on 2020-03-26 08:21 (UTC)

@matthias and @bidskii I have to say that after the last update the SSO Login for me stopped working with the embedded browser. The embedded browser shows a randomly generated very long string after submitting my credentials. The only cause why I tried Installing qt5-webengine was that I saw it by running zoom in terminal so I can't share any insights.

@kevinusername thanks disabling the embedded browser for SSO Login did also work for me.

I think we can consider the automatically embedded browser feature as unreliable

matthias commented on 2020-03-25 22:28 (UTC)

@kevinusername: Thank you so much. Works for me now too :-)

ph2545 commented on 2020-03-25 21:49 (UTC)

@kevinusername PERFECT!! That worked for me. Thanks for sharing

kevinusername commented on 2020-03-25 18:41 (UTC)

@matthias @bidskii @ph2545 I was having the same issue with SSO login failing with the 'referrer policy' warning. In my case this turned out to be an issue with the embedded browser zoom was using to open my SSO login.

I was able to resolve this by editing ~/.config/zoomus.conf with the line embeddedBrowserForSSOLogin=false. After restarting zoom, clicking "sign in with SSO" now opened my default browser (Firefox), and I was able to successfully login.

Found the idea from a somewhat similar GitHub issue:

je-vv commented on 2020-03-25 18:04 (UTC)

@ph2545, I only use zoom for work (just because IT chose to use zoom), and the only way to login is through sso authentication. It's been working fine since I had to start using zoom. Just a reminder that for sso authentication you need to provide your company's domain 1st...

ph2545 commented on 2020-03-25 17:38 (UTC)

@edh What you say sounds reasonable. However, it worked fine prior the March 23 update. Nevertheless thank you for your contribution.

edh commented on 2020-03-25 17:29 (UTC)

@je-vv Thanks for the explanation. I will add picom to the optdepends array with the next update.

@ph2545 I am not part of the zoom support team and the SSO problem very much does not sound like a packaging problem.

ph2545 commented on 2020-03-25 17:22 (UTC)

Thanks for the quick update. However there is still a problem with sso login could you please look at it? Thanks

je-vv commented on 2020-03-25 17:00 (UTC) (edited on 2020-03-25 17:01 (UTC) by je-vv)

They generically recommended a X compositor, and the one mentioned was xcompmgr. When I started to experiment with an X compositor (long time ago) for WMs which were not compositors, like fluxbox and blackbox, I started with xcompmgr, but it crashed every now and then. Then I found compton (now picom), and it has worked flawlessly for me ever since. BTW, lxqt integrates pretty well with picom. The article referenced says: "The share screen feature requires compositing.", and then it shows the particular case for xcompmgr, but that's not the only one. See: "".

edh commented on 2020-03-25 16:51 (UTC)

@je-vv Where did you find that picom helps? xcompmgr is officially recommended by zoom but I wasn't able to find a similar statement for picom.

je-vv commented on 2020-03-25 16:48 (UTC)

@edh and @hmenke, please add both X compositors, picom (compton) and xcompmgr. I've been using zoom with picom + fluxbox for quite a while without issues. Thanks !

the_10 commented on 2020-03-25 08:52 (UTC)

Login with Google Accounts is not working.

Seems this is a xdg issue with Chrome/Chromium. with Firefox it works

edh commented on 2020-03-25 08:34 (UTC)

@hmenke Will do that with the next release. Thanks!

hmenke commented on 2020-03-25 08:31 (UTC)

Could you please add xcompmgr to optdepends? With some window managers screen sharing needs extra compositing, otherwise it just shows a black screen.

bidskii commented on 2020-03-25 00:24 (UTC)

@matthias: I see the same thing.

@losbehamos and @edh: Can you add any insight to this problem?

matthias commented on 2020-03-25 00:22 (UTC)

@bidskii: unfortunatly not. If I run zoom from the console, then the last message is: "js: Failed to set referrer policy: The value 'strict-origin-when-cross-origin' is not one of 'no-referrer', 'no-referrer-when-downgrade', 'origin', 'origin-when-cross-origin', or 'unsafe-url'. The referrer policy has been left unchanged."

bidskii commented on 2020-03-24 23:17 (UTC)

@matthias did you figure out the SSO login?

matthias commented on 2020-03-24 17:28 (UTC) (edited on 2020-03-24 17:41 (UTC) by matthias)

@losbehamos: I installed zoom and qt5-webengine. But after entering id/password for corporate SSO, I always get an error message that the credentials are wrong. It used to work and still does on Windows. How did you get it to work?

sl13kp commented on 2020-03-24 10:49 (UTC)


edh commented on 2020-03-23 14:11 (UTC)


I will add that with the next release. Thanks!

losbehamos commented on 2020-03-23 12:17 (UTC)

For SSO Login I had to install qt5-webengine. @edh please add qt5-webengine as an optional dependency for SSO Login support.

je-vv commented on 2020-03-11 18:16 (UTC)

To me having it available through AUR is big win, 1st to get it upgraded when upgrading from AUR (not sure if zoom offers a pacman repo and maintains it), plus the big help of handling dependencies and Arch upgrades which upstream might not fix on time... I do believe there's a lot of value added by having the AUR package...

pcfreak30 commented on 2020-03-11 18:10 (UTC)

@edh, eh, well... I got the aur package as we are trained to use a package manager before going windows style. If only we could get the "official" version in the main repos, it would all be peachy.

edh commented on 2020-03-11 18:07 (UTC)


Sure, no worries. This was not meant as some kind of objection. What you say is absolutly true and made me wonder whether there is still a need for an AUR package a couple of times as well.

pcfreak30 commented on 2020-03-11 18:03 (UTC)

@edh, sorry then. I did not read all the comments and have been using the aur package. I was not aware and it didn't seem clear.

edh commented on 2020-03-11 18:01 (UTC)


Right, this is pretty obvious from the PKGBUILD itself and I think I discussed in in the comment section as well when zoom first introduced the Arch package.

pcfreak30 commented on 2020-03-11 17:56 (UTC)

Thought users of this package should be aware. Zoom is now building arch packages.

edh commented on 2020-02-27 21:03 (UTC)


This is not what is happening in the PKGBUILD! Please read up on how PKGBUILDs works and how makepkg processed them. The ArchWiki is a great source for information on both of those topics.

About your question: The PKGBUILD basically just recompresses the binary (the orig file) which is provided by upstream and adapts some variables. The output is the non-orig package. It once had a "proper" packaging function but by now it has descended into just a simple AUR wrapper for the upstream Arch package.

Kalinda commented on 2020-02-26 18:26 (UTC)

So I noticed this builds two packages, a regular zoom and a zoom with _orig at the end. What is the purpose the _orig package? Which one should be installed?


the_10 commented on 2020-02-26 07:16 (UTC) (edited on 2020-02-26 07:18 (UTC) by the_10)

Login with Google Accounts is not working. When clicking the "Login with Google" Button tons of messages like kde-open5: /opt/zoom/ version `Qt_5.14' not found (required by kde-open5) show up in the bash. xdg-open also does not fire up zoom

edh commented on 2020-02-18 08:52 (UTC)

@iTanguy I wrote a mail to the zoom support team about this. Thanks for the heads-up.

iTanguy commented on 2020-02-17 20:58 (UTC)

License file is missing from the Arch package; when "custom" is used, the packaging should include a copy of the license.

Note that apparently it's not in the archive I can download from their web site; but I don't know how to report to Zoom directly.

titaniumbones commented on 2020-02-05 19:54 (UTC) (edited on 2020-02-05 19:55 (UTC) by titaniumbones)

I'm still having trouble as of latest build running zoom under gnome-wayland. Not sure if this is a qt bug or a zoom bug, but on launch I get:

ZoomLauncher started.
Zoom not exist at current directory - /home/matt
Zoom path is: /opt/zoom
cmd line: 
CreateReportChannel bp_server_fd=4
$HOME = /home/matt 
export SSB_HOME=/home/matt/.zoom; export QSG_INFO=1; export LD_LIBRARY_PATH=/opt/zoom; export BREAKPAD_CLIENT_FD=3; /opt/zoom/zoom "" 
zoom started.
Client: Breakpad is using Client-Server Mode! client fd = 3
This application failed to start because it could not find or load the Qt platform plugin "wayland"
in "".

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

Reinstalling the application may fix this problem.
ZoomLauncher: new dump generated from pid 141263, path: /home/matt/.zoom/logs/bd17c6b4-726c-4021-c7abcca6-44a03ed3.dmp
$HOME = /home/matt 
sh: line 1: 141263 Aborted                 (core dumped) /opt/zoom/zoom ""
success to create child process,status is 34304.
zoom exited normally.
Something went wrong while running zoom,exit code is 134.
ZoomLauncher exit.

prepending QT_QPA_PLATFORM=wayland doesn't change the output, even though qt5-wayland is installed.

Thanks for any hints!

edh commented on 2020-02-04 05:08 (UTC)

@ambantis Sounds like a bug in zoom. Can you report this upstream?

ambantis commented on 2020-02-04 04:21 (UTC)

Got this warning when creating a local copy of the desktop file:

λ ~/ desktop-file-install --dir=/home/ambantis/.local/share/applications /usr/share/applications/Zoom.desktop
/home/ambantis/.local/share/applications/Zoom.desktop: error: (will be fatal in the future): value "Zoom.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path

Removing the extension in my local copy, it launches fine.

titaniumbones commented on 2020-01-21 22:47 (UTC)

@diogobaeder I'm having the same issue (no support for wayland, qt doesn't launch), did you find a fix?

alpar commented on 2020-01-14 10:23 (UTC)

I tried close to every version back to 3.0.301026.0930 This still crashes for me, the kernel log is :

[14220.207403] perf: interrupt took too long (2519 > 2500), lowering kernel.perf_event_max_sample_rate to 79200
[15846.906911] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
[15846.906915] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[15846.906918] Please file a _new_ bug report on against DRI -> DRM/Intel
[15846.906920] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[15846.906922] The GPU crash dump is required to analyze GPU hangs, so please always attach it.
[15846.906924] GPU crash dump saved to /sys/class/drm/card0/error
[15846.907937] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[15846.908744] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
[15846.909017] i915 0000:00:02.0: Resetting chip for hang on rcs0
[15846.911743] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
[15846.912554] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}

Silva commented on 2020-01-10 10:56 (UTC)

@projectgus: it also crashes for me, with the same problems you mentioned. Looked it up and zoom seems to crash the GPU.

[drm:gen8_reset_engines [i915]] ERROR rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001} Asynchronous wait on fence i915:xfwm4[1072]:6e584 timed out (hint:intel_atomic_commit_ready+0x0/0x50 [i915])

After throwing that the system itself tries to reset the GPU, but can't.

i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

Also 3.5.330166.1202-1 needs double of the resources which 3.0.317369.1110-1 is using, a bit weird.

je-vv commented on 2019-12-11 20:14 (UTC)

@projectgus, what I'm getting is the mouse not responding. Using LXQt + KWin. But X is not frozen, and the keybord keeps working fine, but it's uncomfortable not to be able to select or click on anything.

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):

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/ 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)


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)


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.

flops commented on 2019-09-19 17:14 (UTC)

Hi, could you please change pulseadio-alsa package directly to pulseaudio + alsa-plugins? pulseaduio-alsa is just an asound.conf file. And if you need a custom one and zoom, you doomed to resolve conflicts.

jklaise commented on 2019-08-14 13:56 (UTC)

Ditto @Maduvi @reptile, sometimes on sharing screen my whole system will freeze and I'll have to be kicked of the zoom call by someone else. This seems to happen when there are more people >3 on the call and not when there are fewer. I've had this issue since around version 2.4, I downgraded to 2.1 which seems to work better, but I thought it would be fixed by now - apparently not!

Maduvi commented on 2019-07-19 20:10 (UTC) (edited on 2019-07-29 14:51 (UTC) by Maduvi)

I am experiencing the same problem as @reptile:

"when I share the screen, sometimes it goes black, and I can see only the mouse pointer"

It also happens that I can't share a Whiteboard because the window is black as well. So I believe both things could be related. Maybe some Xorg or mesa driver configuration I have overlooked. Is anyone able to share a Whiteboard instance?

EDIT: fixed the issue installing and enabling compton. Now I can see a whiteboard instance and I hope Zoom will work just fine.

je-vv commented on 2019-07-10 01:07 (UTC) (edited on 2019-07-10 01:09 (UTC) by je-vv)

Note on Friday there's supposed to be fix: Sources about the security issue talk about MAC, not quite sure the issue is only a MAC one though (see all references in I agree with @edh, it's an upstream issue, not a package issue.

edh commented on 2019-07-09 16:34 (UTC) (edited on 2019-07-09 16:34 (UTC) by edh)

Just to clarify, this PKGBUILD is fetching the official package provided by zoom and merely modifies the dependency arrays.

alerque commented on 2019-07-09 12:46 (UTC) (edited on 2019-07-09 14:07 (UTC) by alerque)

Installers beware, this is a binary package and the upstream provider has recently been caught doing some very dodgy things. Use this package at your own risk.

Mading commented on 2019-06-25 16:32 (UTC)

works like a charm thanks!

edh commented on 2019-05-31 07:42 (UTC)


Pulseaudio should definitely be considered the default. This is also the case for the original package and therefore clearly intended this way by the authors of the software. Hence, I think I will leave the dependency as is for now.

I would suggest that you create a mock package for pulseaudio-also on you system which fulfills the dependency without introducing pulseaudio to you installation.

je-vv commented on 2019-05-31 04:54 (UTC) (edited on 2019-05-31 05:11 (UTC) by je-vv)

@edh, it is working fine with plane ALSA, so no need to install pulseaudio at all. I had a problem with multi devices. With just the internal audio and not external USB devices it works just fine, both, though the app test, and through a real conversation.

It means with pulseaudio one might require the pulseaudio-alsa plugin, but only if using pulseaudio. So I would leave as optional if using pulseaudio, given not everyone enables it (like me), but state that the optional dependency is for enabling audio with pulse. I'd really appreciate if you do that, so I don't forget to edit the PKGBUILD on any upgrade. For the testing I manually removed the dependency, so I could avoid having pulseaudio installed and therefore enabled.

Thanks a lot !

edh commented on 2019-05-27 06:43 (UTC) (edited on 2019-05-27 06:44 (UTC) by edh)

@je-vv Is there any other way to get sound without this dependency?

je-vv commented on 2019-05-27 01:10 (UTC)

pulseaudio-alsa should be just an optional dependency, since it's required only when pulse is present, and how it's now, pulse audio is forced to get zoom installed.

hkirsman commented on 2019-04-13 22:42 (UTC)

The issue was with latest mesa

Needed to do some magic to get the version updated because I had some patch version [19.0.1+really+18.3.5-1] which pamac didn't understand anymore. The whole story here:

The Flatpack version worked but it the video was a bit lagging so switching back to native. At least there's an alternative if something happens.

hkirsman commented on 2019-04-10 11:49 (UTC)

Works with Flatpack. Tx!

SanskritFritz commented on 2019-04-10 10:20 (UTC)

Since Zoom is distributed as binary with given dependencies, any change in Archlinux can render Zoom nonfuncional. Hence I would recommend using the Flatpack version which ships the libraries Zoom is depending on:

hkirsman commented on 2019-04-10 09:17 (UTC) (edited on 2019-04-10 09:18 (UTC) by hkirsman)

My Zoom stopped working after system update (I think Zoom was not updated). Could you say what could be wrong? This I get when executing on shell: libEGL warning: DRI2: failed to authenticate libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/dri) libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/dri) libEGL warning: DRI2: failed to authenticate libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/dri) libEGL warning: DRI2: failed to open swrast (search paths /usr/lib/dri) QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled

edit: how can you make code blocks here? :)

edh commented on 2019-01-21 17:36 (UTC)

@daenney Thanks for the hint. Done.

daenney commented on 2019-01-21 14:41 (UTC)

With 2.7.x the PKGBUILD can use a smaller list of dependencies as they now seem to bundle the parts of Qt required:

depends=('glib2' 'libxcb' 'libxfixes' 'libxrandr' 'fontconfig' 'mesa' 'libxi'
         'libsm' 'libxrender' 'libpulse' 'libxcomposite' 'libxslt' 'sqlite' 'dbus' 'ibus') 

mkingston commented on 2018-12-04 15:02 (UTC) (edited on 2018-12-04 15:07 (UTC) by mkingston)

Should've put this information into the comment when I flagged out of date.

New pkgver=2.6.146750.1204

I figure you should prob get the new sha512 yourself.

For any readers, a recent Zoom exploit:

ronw commented on 2018-12-04 14:47 (UTC)

Got an email from Zoom support this morning (2018-12-04) saying they fixed the certificate warnings that started with the previous update.

flutes commented on 2018-09-19 01:49 (UTC)

Hi, I've downloaded zoom via the aur but I'm having an issue when using makepkg -si:

error: failed retrieving file 're2-20180801-1-x86_64.pkg.tar.xz' from [every mirror] : The requested URL returned error: 404

Any help would be greatly appreciated :)

gerardo-junior commented on 2018-08-29 14:53 (UTC)

I can not use oauth, open the browser with the white screen

geripgeri commented on 2018-08-27 07:35 (UTC)

@reptile Thanks for the update!

reptile commented on 2018-08-17 07:51 (UTC)

@geripgeri @gunar Seems that the problem with freezing is gone now (at least for me). Now I have the other problem: when I share the screen, sometimes it goes black, and I can see only the mouse pointer. I have to kill and restart Zoom then. The interesting part is that it happens only in presence of certain user (and I don't know which one). Zoom Support confirmed that it's possible, and asked to make sure that all attendees use the latest version of Zoom... but, in my case, it's impossible :( Have to use other ways to share the screen

kalopsian commented on 2018-08-06 18:27 (UTC)

Had an issue with zoom dropping a core dump (as well as slack) - turned out it was the upgrade from glibc 27-3 to 28-1 which caused the issue. I rolled back glibc to the previous version and all is well. Here's what I did, might help someone:

gunar commented on 2018-07-26 19:07 (UTC) (edited on 2018-07-26 19:09 (UTC) by gunar)

@reptile same here. I also confirm that downgrading resolved the issue.

How to downgrade? (I just learned this myself)

yaourt -S zoom
> Edit PKGBUILD? [Y/n]

Then edit PKGBUILD to follow 03ca5cd. This means updating two lines, pkgver and sha512sums. Save, exit, proceed with the installation.

I also had to killall zoom before it worked

I would also make sure to enable notifications for this package if I were you (menu above: "Enable notifications") so you get notified when this is fixed.


geripgeri commented on 2018-07-18 09:52 (UTC)

@reptile Thanks!

reptile commented on 2018-07-18 09:31 (UTC)

@geripgeri I can only confirm that this problem is present not only for you, I get the same behavior. I have a request to Zoom Support regarding this, I'll let you know the outcome.

geripgeri commented on 2018-07-18 09:19 (UTC)

When I share my screen the whole application freezes, all the controls are unresponsive. This feature was working for me for a long time. There is no error message about this issue when I run it on the console.

I downgraded to version 2.1.103753.0521 (git commit 03ca5cd) and the screen sharing works again.

Do you Guys have any idea what went wrong? Is this an application bug or Arch related?

eMyller commented on 2018-07-12 01:17 (UTC) (edited on 2018-07-12 01:17 (UTC) by eMyller)

For those looking to fix DPI for Zoom: I just added it to the apps list at

To make it permanent, here's how:

  1. Copy /usr/share/applications/Zoom.desktop to your ~/.local/share/applications/
  2. At the Exec command, prepend env QT_SCALE_FACTOR=2.

reptile commented on 2018-04-10 17:48 (UTC)

@edh, thanks! Downgrading "mesa" fixed the problem

edh commented on 2018-04-10 17:26 (UTC) (edited on 2018-04-10 17:27 (UTC) by edh)

@reptile Zoom starts up fine in a clean container with an up-to-date system.

You might want to roll-back the entire update and see whether that helps. If it does, partially update each package one by one and see where things break down.

Blatant self-promotion: To facilitate the downgrade process you may want to use a small script like e.g. downgrade :D

reptile commented on 2018-04-10 15:07 (UTC) (edited on 2018-04-10 16:21 (UTC) by reptile)

After the latest system upgrade, zoom just fails to launch. The output says "zoom started.", but nothing happens. Downgrading zoom back doesn't help. It's something with other parts of the system, but I don't know what exactly, no errors in output... Maybe someone had similar issue?

anavarre commented on 2018-04-07 16:10 (UTC)

@danielbruce - Thank you, your workaround works great!

danielbruce commented on 2018-04-06 20:09 (UTC)

If you're still having seg fault issues, this fixed it for me: touch ~/.config/zoomus.conf.

agisga commented on 2018-04-06 02:45 (UTC) (edited on 2018-04-06 02:47 (UTC) by agisga)

@prosoitos I had the exact same problem with the same error message yesterday. After using git to checkout the previous version (the one from Feb 8) and reinstalling, zoom launches and seems to work fine (though I didn't make any calls yet). So I'm using the Feb 8 version now.

In addition to the error posted by prosoitos, using journalctl I can see the following records related to the zoom segfault:

Apr 05 00:29:18 T450s systemd-coredump[1262]: Process 1259 (zoom) of user 1000 dumped core.
Stack trace of thread 1259:
#0  0x00007f92160b5f11 __strlen_avx2 (
#1  0x00007f9215fadded vfprintf (
#2  0x00007f9215faed86 buffered_vfprintf (
#3  0x00007f9215fac16e vfprintf (
#4  0x00007f9215fb4904 fprintf (
#5  0x0000000000403183 _Z10getSettingPcRiRbRj (ZoomLauncher)
#6  0x000000000040362e _Z12getEnvStringPc (ZoomLauncher)
#7  0x0000000000403dc2 _Z9startZoomPcS_ (ZoomLauncher)
#8  0x0000000000402222 main (ZoomLauncher)
#9  0x00007f9215f7ff4a __libc_start_main (
#10 0x0000000000402312 _start (ZoomLauncher)
-- Subject: Process 1259 (zoom) dumped core

prosoitos commented on 2018-04-06 02:17 (UTC)

I could install without any problem, but zoom does not launch. I get this error:

ZoomLauncher started.
Zoom not exist at current directory - /home/marie
Zoom path is: /opt/zoom
cmd line: 
$HOME = /home/marie 
[1]    10173 segmentation fault (core dumped)  zoom

edh commented on 2018-03-06 19:10 (UTC)

@lujipeka Surely this is not an ideal solution and is due to the odd nature of the PKGBUILD but in the end the error boils down to a poor AUR package manager decision. The only recommendation I can give you is to either use a proper helper or build it from source.

lujipeka commented on 2018-03-06 18:14 (UTC)

I have this error when trying to install zoom on my computer loading packages... error: 'zoom-2.0.115900.1201_orig_x86_64.pkg.tar.xz': duplicate target

catalin.hritcu commented on 2018-02-13 18:13 (UTC)

Probably not related to packaging, but I'm getting quite frequent hangs. Every 20 minutes or so performance gets quickly terrible to the point that the application is completely unresponsive. If I don't kill it fast enough sometimes it even brought down my entire system. I'm wondering if anyone else has been experiencing this and whether there is any workaround.

edh commented on 2018-02-08 18:07 (UTC) (edited on 2018-02-08 18:19 (UTC) by edh)

@daurnimator Thanks, updated!

@paulodiovani It looks like qt5-webkit has been superseded by qt5-webengine and I removed the dependency for now. Please let me know whether this assessment is accurate and SSO login is still working for you.

daurnimator commented on 2018-02-08 00:37 (UTC)

Missing dependency on libxss

edh commented on 2018-01-30 18:44 (UTC)

@paulodiovani Thanks for the hint. I merely copied the dependency field from the official package and did not check for any additional ones.

paulodiovani commented on 2018-01-30 15:49 (UTC)

Zoom depends on qt5-webkit to display webpages (e.g. SSO Login)

pgmillon commented on 2018-01-24 11:26 (UTC)

@wfleming I did many changes to my drivers, switching from open to closed and at some point it ended up working. My issue was indeed not related to QT but rather to the drivers.

wfleming commented on 2018-01-24 00:53 (UTC) (edited on 2018-01-24 01:15 (UTC) by wfleming)

@pgmillon I ran into the same thing and also suspected the qt5 version change as the culprit, but I used downgrade to revert my qt5* packages to 5.9.3, and was still seeing the same error. Did you have any luck working around this issue?

EDIT: qt is almost certainly a red herring since it's not a dep of this package: mesa is the likely culprit since that's being used for OpenGL and was also updated recently. I also tried downgrading mesa to 17.3.3 & 17.3.1, and had no luck.

edh commented on 2018-01-23 18:52 (UTC) (edited on 2018-01-23 18:52 (UTC) by edh)


Unfortunately I am quite busy during the day and am therefore not available on IRC most of the time (always?).

Concerning you provided information: When troubleshooting such a task it is much more likely that something about your software setup led to the problem. I would recommend you to try building the package again preferably in a clean chroot or if this should be to cumbersome just by hand locally using the following command (assuming you have cower installed): cower -d zoom && cd zoom && makepkg -si.

As a workaround you may as well simply install the package from upstream directly using curl -O <> && pacman -U zoom_x86_64.pkg.tar.xz.

bin_bash commented on 2018-01-23 17:06 (UTC) (edited on 2018-01-23 17:17 (UTC) by bin_bash)

@edh, not as far as I'm aware. Here's what I know about this machine, please let me know if this information is useless and what I can provide to be more useful:

Machine: Lenovo Ideapad s400


Distro: Arch

WM: Openbox

DE: None

Sound: ALSA with PulseAudio

Kernel: Linux Baldur 4.9.74-1-lts #1 SMP Wed Jan 3 07:56:32 CET 2018 x86_64 GNU/Linux

Pacman: Pacman v5.0.2 - libalpm v10.0.2

Init: Systemd

Not sure what else would be useful, or if this even is. I'm also on irc under bin_bash if that's a method that may be useful for more in-depth trouble-shooting.


edh commented on 2018-01-22 19:07 (UTC)

@bin_bash Sorry but I can not reproduce your error. Is there something of note about your build environment?

bin_bash commented on 2018-01-22 18:41 (UTC)

Can't install at all, get the following error: error: 'zoom-2.0.115900.1201_orig_x86_64.pkg.tar.xz': duplicate target

pgmillon commented on 2018-01-09 17:48 (UTC)

Broken since my last update from qt 5.9 to qt 5.10:

Linux Client Version is 2.0.115900.1201 Using Qt version 5.10.0 in /usr/lib

edh commented on 2017-11-19 20:49 (UTC)

@jav209 Thanks for the feedback. I stripped down the list of dependencies to only include the ones zoom itself states are needed instead of relying on the output of `namcap`.

jav209 commented on 2017-11-19 16:58 (UTC)

It appears that at least qt5-webengine, qt5-svg, and gstreamer are not _necessary_ dependencies. I am short on space on /, so I tried installing without the libraries that are included with zoom (check out the .so-files in /opt/zoom), and found that at least these three can be removed without losing functionality. Zoom appears to run without pulseaudio-alsa, but not having it appears to mess up my audio config.

dminca commented on 2017-11-11 09:43 (UTC)

Works like a charm! Thank you very much! :)

luan commented on 2017-08-09 20:47 (UTC)

Latest version (2.0.98253.0707) I don't have keyboard input when someone shares their screen with me and gives me control. Downgrading one commit before that works. Anyone else with that?

TrevorBramble commented on 2017-07-10 23:34 (UTC)

@mbroemme Under Xmonad, all of the windows are perfectly movable, however they do not respond to any dismissal key combo I've ever heard of and never have "cancel" buttons, so I often end up shunting any number of accessory windows to another workspace until I can exit the whole program.

mbroemme commented on 2017-06-27 11:49 (UTC)

Is it normal that the Zoom windows have no decorations and cannot be moved at all under Fluxbox? Does anybody have the same issue than me? Other Qt5 applications work fine, however they use system libraries.

jdubs commented on 2017-05-23 18:56 (UTC)

In case anyone finds it helpful, I was having issues with screensharing. Namely, when I shared my screen, participants just saw green where my window should be. First, I upgraded my kernel from 4.7.6 to the latest 4.11.2. This caused the green to instead appear black to participants. This is essentially because of wayland. I had originally set xorg as the default, but this has been reset at some point (perhaps during the kernel upgrade or perhaps earlier). Switching to Xorg makes zoom work perfectly.

smfsh commented on 2017-04-27 15:09 (UTC)

Latest version, for me at least, kills the non-primary window from displaying anything. It just remains black so I'm unable to see what's being shared (or the primary speaker when no one is sharing.) I don't see anything super incriminating in the logs so I'm unsure what's causing it. Downgrading to the last available version seems to solve the problem.

edh commented on 2017-03-23 09:27 (UTC)

@festerman Thanks for the update. I changed the pkgver back to the current release. Please be sure to remove the remaining source in your SRCDEST if necessary.

festerman commented on 2017-03-23 09:13 (UTC)

@edh: Upstream updated now, acc. to Zoom support ...

edh commented on 2017-03-22 10:27 (UTC)

@FredBezies Their package file seams to be corrupted. I will roll back for now. Please be sure to file a bug on their website.

FredBezies commented on 2017-03-22 09:58 (UTC)

Busted ! ==> Extracting sources... -> Extracting zoom-2.0.87130.0317_orig_x86_64.pkg.tar.xz with bsdtar opt/zoom/ Lzma library error: No progress is possible bsdtar: Error exit delayed from previous errors. ==> ERROR: Failed to extract zoom-2.0.87130.0317_orig_x86_64.pkg.tar.xz Aborting...

ryanvade commented on 2017-03-17 02:52 (UTC)

The v4l2loopback kernel module appears to be required for Desktop (not application window) sharing.

ryanvade commented on 2017-03-13 14:34 (UTC)

@edh Screen capture has stopped working only with wayland (i.e. GNOME). Xorg works but generally crashes. I had those extra packages installed already and the new package has not fixed the issue. Most likely this is an upstream problem.

edh commented on 2017-03-12 09:29 (UTC)

@DCengineer I can not reproduce your problem. The packages I build all have 755 as permission settings for the listed directory. Furthermore I would recommend against changing the mode bits of those directories since 755 is used by probably all other packages. Please try building the package yourself without an AUR helper. Should this still not work build without cleaning up the pkg directory, change the permissions there and then repackage. The last recommendation is a little tricky but should work for sure.

DCengineer commented on 2017-03-12 01:12 (UTC)

I've been getting a series of permissions errors when I try installing the latest update. It says that my filesystem is using 755 and the package wants 775. Is it safe to change the permissions in the directories listed? /opt/ /usr/bin/ /usr/share/ /usr/share/doc/ /usr/share/mime/ /usr/share/mime/packages/ /usr/share/pixmaps /usr/share/applications/

edh commented on 2017-03-09 10:47 (UTC)

@Drew AFAIK there is no difference between the two packages. Therefore one should not be superior to the other. The PKGBUILD originated from a time when there was no Arch package available and has since been kept to ease installation (see the pinned comment). However I agree that it would be best to use the provided package from their website. Though this will undoubtedly make for a pretty odd PKGBUILD.

Drew commented on 2017-03-09 00:49 (UTC) (edited on 2017-03-09 00:50 (UTC) by Drew)

I don't see any advantage to downloading the deb version from their website, unpacking it, repacking it into pkg.tar.xz, and then installing that, when Zoom already provides a pkg.tar.xz version made for Arch at the very same website. If you really want a PKGBUILD up here, wouldn't it be better to at least use the Arch package as the source? I feel more comfortable downloading the correct version from their site.

mvdan commented on 2017-03-06 10:18 (UTC)

Zoom will lock up my X after 15-30m on a call and it will be impossible to recover from. Even if I manage to kill zoom, programs like Chromium still have terrible glitches and I need to reboot. Is anyone else experiencing this issue? For reference, this is on AwesomeWM. This has happened four times so far.

edh commented on 2017-03-02 19:20 (UTC)

@ryanvade I added a couple of additional dependencies. Please let me know whether that fixed the problem.

ryanvade commented on 2017-03-02 17:00 (UTC)

Screen sharing seems to be no longer working

edh commented on 2017-01-26 21:38 (UTC)

@mvdan Not exactly, gstreamer0.10 was removed from the dependency array a couple of days ago, but I just recently increased the pkgrel to force a rebuild for all users. I assumed that if the update would have caused problems for those users which rebuild the package themselves, they would have noted in the comments. Since that did not happen, I guess zoom works without this dependency.

mvdan commented on 2017-01-26 21:32 (UTC)

Ah, you just pushed that now :) Thanks!

edh commented on 2017-01-26 21:26 (UTC)

@mvdan Yes, I dropped the dependency for the reasons explained in my previous comment.

mvdan commented on 2017-01-26 21:16 (UTC)

@edh have the gstreamer0.10 deps been dropped? I can't see it. Thanks!

edh commented on 2017-01-23 19:55 (UTC)

@quest Thanks for the reminder! Though being referenced in the binaries it is not included in the official package. Therefore I assume it is not strictly required for zoom to work properly and I simply dropped it as well.

quest commented on 2017-01-23 18:16 (UTC)

Looks like gstreamer0.10 and gstreamer0.10-base have been pulled. =(

gableroux commented on 2017-01-04 16:41 (UTC)

I confirm this client also works with ringcentral meetings :)

HarlemSquirrel commented on 2016-12-21 03:26 (UTC)

@edh I was only trying to help.

edh commented on 2016-12-18 17:47 (UTC)

@HarlemSquirrel Flagging a package as out-of-date is sufficient. You do not need to post an additional comment.

HarlemSquirrel commented on 2016-12-18 17:30 (UTC)

I was able to install 2.0.75971.1216 by updating the following pkgver=2.0.75971.1216 md5sums_i686=('1327aa6cd13f883d5b2566794bac6d66') md5sums_x86_64=('3cadbc7c9369c002f91fedf04a87de8b')

rbellamy commented on 2016-08-31 21:53 (UTC)

Sorry flagged this as out of date because the client is claiming there is a newer version, and when I look at my `pacman -Qi zoom` it shows 2.0.57232.0713-2. However, clearly this package is using the most recent version, 2.0.63547.0830.

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.

chaparro commented on 2016-08-25 05:26 (UTC)

Has anyone tried using Not sure if this was just an oversight but it may help.

juantascon commented on 2016-08-12 16:17 (UTC)

a bit out of topic here but do you guys know if there's any way to join a conference via command line? all I found on the internet was docs for doing it trough the UI, zoom -h or zoom --help doesn't tell anything either

edh commented on 2016-08-10 16:07 (UTC) (edited on 2016-08-10 16:07 (UTC) by edh)

@tad Your argument seems reasonable. I altered the dependency array according to your suggestions but added a couple of qt5 dependencies and gstreamer.

tad commented on 2016-08-10 07:43 (UTC)

edh, check here: I ran through namcap with the dependencies listed and it works fine on qt5. In fact it's the only way to get HiDPI support.

edh commented on 2016-08-06 11:45 (UTC)

@tad Thanks for the hint about the static source link. I altered the PKGBUILD accordingly. However I am not so sure about the dependencies you listed. The current dependencies are directly taken from the upstream package with no modifications, therefore I expect that the developers in one or the other way rely on each of them.

tad commented on 2016-08-06 07:17 (UTC)

I took a moment to clean up some dependencies, as they have changed. qt4 is no longer needed, for example. depends=( 'glib2' 'gstreamer' 'libxcb' 'xcb-util-image' 'fontconfig' 'mesa' 'libxi' 'libsm' 'libxrender' 'libpulse' 'libxcomposite' 'libxslt' 'sqlite' 'xcb-util-keysyms' )

tad commented on 2016-08-06 06:51 (UTC) (edited on 2016-08-06 06:51 (UTC) by tad)

This works: source_i686=("{$pkgver}/zoom_${pkgver}_i386.deb") source_x86_64=("{$pkgver}/zoom_${pkgver}_amd64.deb")

edh commented on 2016-06-02 14:43 (UTC)

@bcc Thanks for flagging the package. Unfortunately the zoom release blog is not updated timely, plus they don't use static links for one release but prefer to break the existing link each time a new release is introduced.

bcc commented on 2016-06-02 12:01 (UTC)

curl: (22) The requested URL returned error: 403 Forbidden ==> ERROR: Failure while downloading Aborting... :: failed to verify zoom integrity FAIL: 1

edh commented on 2016-05-05 09:23 (UTC)

@cjobrien Thanks for the hint. I added a few deps which should resolve the reported issue.

cjobrien commented on 2016-05-04 19:11 (UTC)

Saw the following error with zoom 2.0.49177.0430-2: /opt/zoom/zoom: error while loading shared libraries: cannot open shared object file: No such file or directory success to create child process,status is 32512. zoom exited normally. some wrong happened when run zoom,exit code is 127. ZoomLauncher exit. Fixed by installing the xcb-util-keysyms package.

edh commented on 2016-05-02 18:24 (UTC)

Thanks @pmig for the shout out. I altered the dependency array accordingly in the hope it will help. I assume @topher1kenobe experienced the same problem. Previously merely libpulse was a dependency but apparently pulseaudio is needed. Sorry for the inconvenience.

pmig commented on 2016-05-02 14:51 (UTC) (edited on 2016-05-02 18:01 (UTC) by pmig)

Edit: I resolved this error by installing pulse audio! @edh I'm also not able to join or create a meeting. I see following output: Zoom path is: /opt/zoom cmd line: [CZPClientLogMgr::LogClientEnvironment] [MacAddr: ][client: Linux][OS: Manjaro Linux][Hardware: CPU Core:1.77531 G Memory size:15895MB CPU Brand:Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz][Req ID: ] Linux Client Version is 2.0.49177.0430 Graphics Card Info:: 00:02.0 VGA compatible controller: Intel Corporation Skylake Integrated Graphics (rev 06) PreMeetingUIMgr::closeWindow PreMeetingUIMgr::closeWindow, hide PT window CSBConfUI::OnConfStatusChanged cmd:59, ret:0 CSBConfUI::OnConfStatusChanged cmd:23, ret:0 CSBConfUI::OnConfStatusChanged cmd:27, ret:1 CSBConfUI::OnConfStatusChanged cmd:28, ret:1 CSBConfUI::OnConfStatusChanged cmd:25, ret:0 CSBConfUI::OnConfStatusChanged cmd:71, ret:0 CSBConfUI::OnConfStatusChanged cmd:79, ret:0 CSBConfUI::OnConfStatusChanged cmd:9, ret:1 CSBConfUI::OnConfStatusChanged cmd:59, ret:0 CSBConfUI::OnConfStatusChanged cmd:23, ret:0 CSBConfUI::OnConfStatusChanged cmd:27, ret:1 CSBConfUI::OnConfStatusChanged cmd:28, ret:1 CSBConfUI::OnConfStatusChanged cmd:25, ret:0 CSBConfUI::OnConfStatusChanged cmd:71, ret:0 CSBConfUI::OnConfStatusChanged cmd:79, ret:0 CSBConfUI::OnConfStatusChanged cmd:9, ret:1 CSBConfUI::OnConfStatusChanged cmd:73, ret:0 CSBConfUI::OnConfStatusChanged cmd:6, ret:0 CSBConfUI::OnConfStatusChanged cmd:8, ret:0 CSBConfUI::OnConfStatusChanged cmd:7, ret:0 zoom: pcm.c:2757: snd_pcm_area_copy: Assertion `src < dst || src >= dst + bytes' failed. sh: line 1: 6151 Aborted (core dumped) /opt/zoom/zoom "" success to create child process,status is 34304. zoom exited normally. some wrong happened when run zoom,exit code is 134. ZoomLauncher exit.

topher1kenobe commented on 2016-03-15 20:21 (UTC)

Zoom fires up for me just fine, but when I join a chat I see about 1/10 of a second of motion, and then the video freezes. It looks like it brings up a dialog box trying to ask a question about audio, but the contents are showing a distorted version of the video. After about 10 seconds it crashes. Here's the console output. CSBConfUI::OnConfStatusChanged cmd:8, ret:0 CSBConfUI::OnConfStatusChanged cmd:17, ret:0 CSBConfUI::OnConfStatusChanged cmd:5, ret:0 CSBConfUI::OnConfStatusChanged cmd:27, ret:0 CSBConfUI::OnConfStatusChanged cmd:43, ret:0 CSBConfUI::OnConfStatusChanged UI_CMD_SHARE_READYCSBConfUI::OnConfStatusChanged cmd:18, ret:0 sh: line 1: 26858 Illegal instruction (core dumped) /opt/zoom/zoom "" success to create child process,status is 33792. zoom exited normally. some wrong happened when run zoom,exit code is 132. ZoomLauncher exit.

edh commented on 2016-01-15 20:01 (UTC)

In case you did installed xcb-util-image manually (like grvrulz advised) please make sure it is installed as a dependency. If not change its properties accordingly (# pacman -D --asdeps xcb-util-image) otherwise you system will become unnecessarily cluttered with packages you may not need. @sonny Many thanks for your feedback. Unfortunately the debian dependencies are quite different and converting them is not always straight forward. Namcap is not that helpfull either. Anyway I hope I got all deps right by now :D

properlypurple commented on 2016-01-15 12:56 (UTC)

@sonny You need to install xcb-util-image and it'll work. @edh Please add this to deps.

sonny commented on 2016-01-14 11:15 (UTC)

/opt/zoom/zoom: error while loading shared libraries: cannot open shared object file: No such file or directory

sonny commented on 2016-01-10 15:02 (UTC)

@edh fixed thanks!

edh commented on 2016-01-10 14:47 (UTC)

@sonny Thanks for reporting the problem. It occured due to the wrong version of gstreamer being listed in the dependency array. It should work now. Please feel free to let me know in case it does not.

sonny commented on 2016-01-09 01:27 (UTC)

/opt/zoom/zoom: error while loading shared libraries: cannot open shared object file: No such file or directory success to create child process,status is 32512. zoom exited normally. some wrong happened when run zoom,exit code is 127. ZoomLauncher exit.

edh commented on 2016-01-08 13:14 (UTC)

Sorry for that! I did a sloppy job yesterday. The issues should be fixed now and the 64-bit version should work fine now.

vladev commented on 2016-01-08 08:00 (UTC) (edited on 2016-01-08 08:03 (UTC) by vladev)

With the latest version (1.1.37479.0107) it doesn't start, due to lacking dependency: Zoom not exist at current directory - /home/user Zoom path is: /opt/zoom cmd line: /opt/zoom/zoom: error while loading shared libraries: cannot open shared object file: No such file or directory success to create child process,status is 32512. zoom exited normally. some wrong happened when run zoom,exit code is 127. ZoomLauncher exit. There seems to be a lacking dependency in the PKGBUILD of xcb-util-image.

ronw commented on 2016-01-08 01:03 (UTC) (edited on 2016-01-08 01:05 (UTC) by ronw)

@edh Do you plan on switching to the 64-bit client at some point? Or does their 64-bit version also require the lib32 libs?

edh commented on 2015-12-09 18:27 (UTC)

It was reported that there should be a new version. However the download page still links to version 1.1.33228.1124 and the announcement blog for new releases was not updated either. Hence I will keep things as they are and will update the package as soon as there is a new official release.

edh commented on 2015-11-20 19:20 (UTC)

@imchairmanm Many thanks. I added it to my watchlist and should be notified more speedily. I wounder why I did not stumble over this page. Either way thanks again!

imchairmanm commented on 2015-11-20 18:56 (UTC)

@edh: Took a bit of searching, but this page seems to be updated regularly with their new releases. There doesn't seem to be any way to get to the previous versions, but at least they seem to be tracking the changes here:

edh commented on 2015-11-20 14:51 (UTC) (edited on 2015-11-20 14:57 (UTC) by edh)

@zdosa Thanks! Updated... @gabesullice The repository multilib has to be enabled for packages which depend on 32-bit versions of libraries (lib32-* packages). @all It would be great if someone would have found a page or something similiar on which the developers announce new releases. Until now I have neither found something similiar nor have I even seen an archive of old versions (since fetching the source from there would never reseult in an broken checksum).

zdosa commented on 2015-11-20 14:41 (UTC)

md5sum again 776642f5e82e22645189fe016515ade0 ZoomInstaller_i386.deb btw, thx for package

gabesullice commented on 2015-09-28 17:37 (UTC)

Took me a bit to realize I needed the multilib repository enabled, in case anyone else hits a snag and that might be the solution.

edh commented on 2015-09-22 17:15 (UTC)

@alaricljs Thanks! Updated...

alaricljs commented on 2015-09-22 16:05 (UTC)

New version: 0c7366e9555ea5f508f1a0f2a5279aa7 ZoomInstaller_i386.deb Just the md5 and everything is working as before.

morantron commented on 2015-09-10 09:31 (UTC)

Yaaay it works like a charm! Thanks guys! =]

edh commented on 2015-09-03 16:06 (UTC)

@morantron I added a few more dependencies which were needed for the debian package to work. I hope this fixes the sound problem as well. Please let me know whether everything is working as expected.

morantron commented on 2015-09-03 09:11 (UTC)

Sound does not work for me, any tips?

edh commented on 2015-09-01 20:22 (UTC)

@alaricljs Sounds reasonable! Props for finding that out. Thanks.

alaricljs commented on 2015-09-01 20:00 (UTC)

Adding that package alone is what made it possible for me to start using my account so while it's part assumption I think it's fairly certain.

edh commented on 2015-08-31 19:26 (UTC)

@alaricljs Thanks! I added lib32-openssl to the dependencies-array. However since I do not use the program myself I am unable to asses whether it is really needed or provided by the package itself.

alaricljs commented on 2015-08-31 19:09 (UTC)

Please add lib32-openssl to the dependencies, it is used for SSO against https.

edh commented on 2015-08-28 09:42 (UTC)

@sonny Actually lib32-libgl is the required dependency, hence lib32-nvidia-utils is the corresponding package for the nvidia guys (like me) but lib32-mesa-libgl should do the trick for everyone else. Thanks for the reminder, I have overlooked that at the previous commit.

sonny commented on 2015-08-28 08:43 (UTC)

@edh thanks; why is lib32-nvidia-utils a dependency? Should probably be optional.

edh commented on 2015-08-27 16:23 (UTC)

@sonny Thanks! I cleaned up the whole dependecies-array.

sonny commented on 2015-08-25 07:46 (UTC)

2 dependencies are missing; lib32-libxrender and lib32-sqlite thanks