Screen Share is broken on wayland

Forum|Forum|1 year ago
October 3, 2024
2 replies
0 views

Hi Zoom Folks,

So this was working but has broken again in the past month or so. It was working fine at some point before 6.2.3.2056. Sorry for not being exact but this also coincided with a hardware error on my old laptop (since replaced).

The issue that I'm seeing is reported here but for the record it seem like zoom is now trying to use

(/usr/libexec/xdg-desktop-portal:297866): xdg-desktop-portal-WARNING **: 22:51:56.438: A backend call failed: No such interface “org.freedesktop.impl.portal.RemoteDesktop” on object at path /org/freedesktop/portal/desktop
XDP: remote desktop session owned by ':1.549' closed

** (/usr/libexec/xdg-desktop-portal:297866): WARNING **: 22:51:56.438: Failed to close session implementation: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/freedesktop/portal/desktop/session/1_549/zoomcast

I've tried also using GNOME under wayland but still get the same behaviour.

Cheers

Steve

Screen sharing

Best answer by kats_UMN

After a lot of trial and error, I downloaded an old version:

https://zoom.us/client/6.0.12.5501/zoom_amd64.deb

and installed it:

sudo apt upgrade ./zoom_amd64.deb

Apt was smart enough to do the downgrade instead of "upgrade". And it all works again!

K

kats_UMN

Newcomer

My screen sharing is broken too. I can't click anything when sharing. I am also running Zoom 6.2.3.2056 running Ubuntu 64-bit. I tried every possible way to share, and everyone results in my mouse only working on the zoom application, not on any of the rest of my desktop.

K

kats_UMNAnswer

Newcomer

After a lot of trial and error, I downloaded an old version:

https://zoom.us/client/6.0.12.5501/zoom_amd64.deb

and installed it:

sudo apt upgrade ./zoom_amd64.deb

Apt was smart enough to do the downgrade instead of "upgrade". And it all works again!

S

SteveF_NZAuthor

Newcomer

Bingo! Cheers!

MGSR

Community Manager

Hello community members!

I'm sorry for the inconvenience and the late response.

Our technical team has acknowledged this issue and is actively working on a solution.

We do not have an estimated time when it will be fixed, but we will update you on this thread once we have the information.

For now, thank you for your patience and understanding.