-
Success! I can finally - selectively - screen share with a #flatpak-sandboxed #Zoom client (I certainly don't run that thing without a sandbox) running in a #KDE #Plasma session under #Wayland. There are two main parts required: 1. Set enableWaylandShare=true in (1/4)Permalink On twitter.com
♻️ 1 Retweets ❤️ 5 Favorites Mood +5 🙂
-
.var/app/us.zoom.Zoom/config/zoomus.conf (Zoom helpfully mentions that when started under Wayland already in newer versions) 2. Set environment variables to make the Zoom client believe it runs under #Gnome instead of #KDE (why, Zoom devs, why): flatpak (2/4)Permalink On twitter.com
-
--env=XDG_SESSION_DESKTOP=gnome-wayland --env=GDMSESSION=gnome-wayland --env=XDG_CURRENT_DESKTOP=GNOME run us.zoom.Zoom I set those 3 variables through #flatseal instead of starting through a shell(script) every time, and this seems to do the trick. Starting (3/4)Permalink On twitter.com
-
Zoom through krunner, opening a new meeting, and clicking "Share Screen" and selecting "Use system capture" pops up the portal - as it should! (4/4)Permalink On twitter.com
-
PS: I spent far too long yesterday in a loop of trying exactly those steps and the Zoom client silently closing every time I tried to start it. Moving most of my existing files/dirs from .local/share and .config out of the way made it start again. (1/3)On twitter.com
-
I am in the process of trying to figure our which specific config broke starting #Zoom under #Wayland when all other applications works normally (and Zoom started under #X11 without an issue), but it is ... tiresome to have something just silently fail without any (2/3)Permalink On twitter.com
-
indication of an error. And yes, I have been logging out and in again far too many times in the last 24h... (3/3)Permalink On twitter.com