| 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: | 646 |
| Popularity: | 8.70 |
| First Submitted: | 2015-08-15 13:18 (UTC) |
| Last Updated: | 2024-04-19 23:28 (UTC) |
qt5 may no longer be an "optional" dependency. I tried installing Zoom yesterday with this AUR and got a crash on startup. Logs showed this error:
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Using version 5.16.2-1 I can not escape from minimized video. When attempting to do this, the animation back to full screen plays but is just a black window. The minimized video controls reappear at their previous location.
Setting enableMiniWindow to false in ~/.config/zoomus.conf is a work around that allows you to minimize zoom, but it does not address the fact that the mini window is broken.
@tsangares the mini window shouldn't appear at all if you disable it with the config setting. You do need to restart zoom for it to take effect though, perhaps you didn't restart it?
@mcw @Dacid01 @ chrisjbillington. I also get:
Window manager warning: Invalid WM_TRANSIENT_FOR window
And I am disabling it using enableMiniWindow to false in ~/.config/zoomus.conf as chris said. But still broken af. But I am running 5.15.12-1 so I will update and let you all know if its still an issue.
@David01 you can disable the mini window altogether by setting enableMiniWindow to false in ~/.config/zoomus.conf
@mcw @chrisjbillington regarding Does anyone else have an issue with Zoom getting stuck in a minimized state?
I reproduce the exact same behaviour. Are there any workarounds other than downgrading programs? Shall we report this to the relevant program's repositories? Many thanks.
@winslow: thanks for suggesting where to look, it was the sandbox, because I'm on linux-hardened, I had to install bubblewrap-suid. I ran sudo chmod 4775 /opt/zoom/cef/chrome-sandbox and the issue was fixed
@seqfault can you provide the file ~/.zoom/logs/zoom_stdout_stderr.log ?
@winslow your fix doesn't help
@seqfault I have a temporarily solution to Zoom's compatibility issue with PipeWire on ArchWiki, but they decided to remove it due to it being a dirty patch. You can check that page's edit history. I've tested it and it seems like Zoom is fully functional after the patch, the poll prompt is a bit dull but I think it's an irrelevant issue
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)