flathub / us.zoom.Zoom

https://flathub.org/apps/details/us.zoom.Zoom
35 stars 44 forks source link

Gnome / Wayland - no screen sharing unless I enable D-Bus session bus #402

Open RafalSkolasinski opened 1 year ago

RafalSkolasinski commented 1 year ago

Noticed few days ago that sharing screen on Gnome+Wayland (Fedora 38) stopped working for me (I could not choose screen to share - only whiteboard). After a bit of playing around I noticed that I can restore option to screen share by adding permission to use D-Bus session bus in FlatSeal.

I believe screen sharing should work out of the box - and it did until recently - so possibly some default settings changed? Or is Fedora at fault here?

ozdreamern commented 1 year ago

Thanks for posting this. I experienced the same problem running Zoom flatpak 5.14.10.3738 under Pop_OS 22.04 (using vanilla gnome under Wayland), and appreciate the workaround.

(Zoom still freezes when I click "stop sharing", a problem which has been present for a few months, but at least I can share a screen when absolutely necessary.)

Originalme commented 12 months ago

I added the dbus option to my installation, and it still fails. It at least acts like it starts the share now, but never actually changes to the "share" view, and nobody can see anything on the meeting.

The good(?) news is this seems to affect the rpm version of the latest Zoom client, so it doesn't appear to be an issue with the flatpak itself.

mohssineAboutaj commented 11 months ago

same here with Ubuntu 23.04+Gnome 44.2

nedrichards commented 11 months ago

If this affects the main client is there a link to an upstream report/forum thread/etc?

Areiser commented 11 months ago

How can this affect the main client? It can be fixed using flatseal and providing the D-Bus session bus permission.

wenottingham commented 11 months ago

Ran into this today with Zoom 5.15.3.4839 from flathub + Fedora 38 (silverblue). Applying the session bus permission via flatseal did fix it for me.

RalfJung commented 11 months ago

It can be fixed using flatseal and providing the D-Bus session bus permission.

That's not a fix, it's a terrible work-around: this permission lets Zoom entirely escape the sandbox.

I'll have to figure out how to downgrade a flatpak...

RalfJung commented 11 months ago

This seems to be the latest version that still works:

sudo flatpak update --commit 1f688feb43683a36eb36b654db37e959ba873cf735ae72896a5259c38975c5bc us.zoom.Zoom

So this is a diff that brought the regression: https://github.com/flathub/us.zoom.Zoom/compare/018eae24...bc3683ce.

mliertzer commented 10 months ago

Going to Settings -> Share Screen -> Advanced and switching "Screen capture mode on Wayland" to "Pipewire Mode" fixes the issue for me without giving additional permissions. Only remaining issue: Annotating does not work with sharing over pipewire. However, that's also the case for the official package.

j-dominguez9 commented 10 months ago

Here on Fedora Sericea, not finding any fixes to the screen share crash, even with all the suggestions above.

RafalSkolasinski commented 10 months ago

Here on Fedora Sericea, not finding any fixes to the screen share crash, even with all the suggestions above.

This issue is not about crash but about not having option to even start screen sharing.

LyzardKing commented 8 months ago

The solution seems to be to set "Screen capture mode on Wayland" setting from "Auto Mode" to "Pipewire More" in the advanced screen sharing settings. #412

cgevans commented 6 months ago

I'd note that alternatively, adding org.gnome.* to Session bus / Owns in flatseal appears to make Zoom recognize pipewire screen sharing in Gnome (on Fedora 39) even with screen capture mode set to Auto.

RalfJung commented 6 months ago

That grants access to tons of endpoints though. Is that safe from a sandboxing perspective?

cgevans commented 6 months ago

Probably not. I'd hope that something narrower under org.gnome might be able to be found that would still work.

takluyver commented 6 months ago

If someone wants to figure out a narrower rule for that, you could watch the D-Bus communications with a tool like Bustle while running Zoom with the broader D-Bus permissions allowed. That should show what it talks to - it might then be necessary to experiment a bit to work out what it needs to talk to.

(This issue is solved well enough for me by setting the screen capture mode to Pipewire)

vanheck commented 6 months ago

Think that could be the same trouble as https://github.com/flathub/us.zoom.Zoom/issues/412#issuecomment-1878331339