Package Details: zoom 2.0.123200.0405-1

Git Clone URL: https://aur.archlinux.org/zoom.git (read-only)
Package Base: zoom
Description: Video Conferencing and Web Conferencing Service
Upstream URL: https://zoom.us/
Keywords: call conference meeting video
Licenses: custom
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 83
Popularity: 4.349017
First Submitted: 2015-08-15 13:18
Last Updated: 2018-04-08 14:32

Pinned Comments

edh commented on 2016-08-26 11:03

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

reptile commented on 2018-04-10 17:48

@edh, thanks! Downgrading "mesa" fixed the problem

edh commented on 2018-04-10 17:26

@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

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

@danielbruce - Thank you, your workaround works great!

danielbruce commented on 2018-04-06 20:09

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

@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 (libc.so.6)
#1  0x00007f9215fadded vfprintf (libc.so.6)
#2  0x00007f9215faed86 buffered_vfprintf (libc.so.6)
#3  0x00007f9215fac16e vfprintf (libc.so.6)
#4  0x00007f9215fb4904 fprintf (libc.so.6)
#5  0x0000000000403183 _Z10getSettingPcRiRbRj (ZoomLauncher)
#6  0x000000000040362e _Z12getEnvStringPc (ZoomLauncher)
#7  0x0000000000403dc2 _Z9startZoomPcS_ (ZoomLauncher)
#8  0x0000000000402222 main (ZoomLauncher)
#9  0x00007f9215f7ff4a __libc_start_main (libc.so.6)
#10 0x0000000000402312 _start (ZoomLauncher)
-- Subject: Process 1259 (zoom) dumped core

prosoitos commented on 2018-04-06 02:17

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

@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

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

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.

All comments