@juanignaciosl - In sway, you would use something like:
swaymsg output eDP-1 position 0 0
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 .. 19 20 21 22 23 24 25 26 27 28 29 .. 77 Next › Last »
@juanignaciosl - In sway, you would use something like:
swaymsg output eDP-1 position 0 0
@noctiluus: no solution for the black menu o far. @a172: how can I "have a screen at position 0,0"? I'm sorry, I don't know what that means. I thought that it might be related to the relative positions of my two displays, but I haven't found any arrangement that makes it works.
@daffydack - Make sure xwayland is installed. Even when running zoom natively in wayland, it is necessary for it to start up. I've seen this behavior in electron apps as well.
@juanignaciosl and @noctiluus - unfortunately, wonky menus are fairly common for qt applications (zoom is one) in wayland. A work around for them showing up in the wrong place is to make sure you have a screen at position 0,0. For the menu showing up, but the contents not being drawn, I have had luck with resizing the parent window, holding the mouse still for a few seconds over the button that opens the menu, and/or moving the mouse off of the menu and back on it. Some fiddling with those usually brings it up. It is very annoying, and just when I think I've figured out the correct incantation to make it work, it changes. Very annoying.
@juanignaciosl Do you know if there is a solution to the black menu error? I have that as well. From what I can tell, the menu is still operable, merely invisible. As when I scroll over it, it will populate a popup window. I've installed the upstream version, and it appears to have the same graphical error, as well.
@kriansa
Thanks for the link, I will degrade ibus
to an optional dependency with the next release.
@dmedinag
I believe gst-plugin-pipewire
is only an indirect dependency and not strictly required by zoom itself. Please correct me if I am wrong about this!
@edh: According to this thread, ibus
is only required for remote control. Would you be willing to turn ibus
into a optional dependency?
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)