zeroconf: yay is not your package manager, pacman is. pacman is not responsible for building packages, that's what makepkg and its friends are for. it would be more accurate to state this is a problem with Zoom, since the "build" very simply repackages upstream's archive. neither pacman nor makepkg have much say in how the binaries are produced in this case.
that being said: i too have been running into issues with Zoom dumping core as soon as it started, which seemed to be related to the bundled libcef.so. building in a clean chroot and wiping out ~/.zoom/ finally produced console output that indicated /opt/zoom/cef/chrome-sandbox was not setuid, and after "sudo chmod 4755 /opt/zoom/cef/chrome-sandbox" it began loading normally. is there anything in your omitted console output or your journal that might indicate a similar problem?
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: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)