| Git Clone URL: | https://aur.archlinux.org/zoom.git (read-only, click to copy) |
|---|---|
| Package Base: | zoom |
| Description: | Video Conferencing and Web Conferencing Service |
| Upstream URL: | https://zoom.us/ |
| Keywords: | call conference meeting video |
| Licenses: | LicenseRef-zoom |
| Submitter: | edh |
| Maintainer: | edh |
| Last Packager: | edh |
| Votes: | 650 |
| Popularity: | 10.34 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2024-06-01 16:23 (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?
For those looking to fix DPI for Zoom: I just added it to the apps list at https://wiki.archlinux.org/index.php/HiDPI#Zoom.
To make it permanent, here's how:
/usr/share/applications/Zoom.desktop to your ~/.local/share/applications/Exec command, prepend env QT_SCALE_FACTOR=2.@edh, thanks! Downgrading "mesa" fixed the problem
@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
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?
@danielbruce - Thank you, your workaround works great!
If you're still having seg fault issues, this fixed it for me:
touch ~/.config/zoomus.conf.
@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
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
@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.
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.confupdates:qt5-webengineinstalled, and theebeddedBrowserForSSOLoginline doesn't exist in my configzoomus.conf. SSO login works just fine (issues with Firefox containers aside).pipewire-pulse.system.audio.typedefaulted toalsafor me (or I changed it without realizing it). I probably could have installedpipewire-alsaand fixed my issues, but I setsystem.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)