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?
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: | 669 |
Popularity: | 7.40 |
First Submitted: | 2015-08-15 13:18 (UTC) |
Last Updated: | 2024-10-28 11:11 (UTC) |
« First ‹ Previous 1 .. 26 27 28 29 30 31 32 33 34 35 36 .. 77 Next › Last »
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?
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.
@GreenAvocado thanks for your help. Making the sandbox binary SUID seems to have fixed it:
$ sudo chmod u+s /opt/zoom/cef/chrome-sandbox
@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.
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.
@bigcajun826 5.10 seems to have a problem with blurring the background. The camera was working fine after I turned the blur off.
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
...
I never have any screen sharing problem on KDE x11
@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.
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.
Pinned Comments
arash-m commented on 2024-09-15 15:56 (UTC)
Tested 6.2.0-1. Sharing works for me, but it still crashes after stopping. The workaround for me is still downgrading pipewire and libpipewire to 1.0.7 before meetings.
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:qt5-webengine
installed, and theebeddedBrowserForSSOLogin
line doesn't exist in my configzoomus.conf
. SSO login works just fine (issues with Firefox containers aside).pipewire-pulse
.system.audio.type
defaulted toalsa
for me (or I changed it without realizing it). I probably could have installedpipewire-alsa
and 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)