You are not logged in.

#1 2025-05-27 21:48:03

clearmartin
Member
Registered: 2015-04-07
Posts: 5

Unable to share screen in web Teams on KDE Plasma Wayland

Since a few weeks back I'm unable to share my screen in Teams running in Chromium (tried X11 and Wayland mode) in Wayland Plasma.

When try to share a screen (in Teams) in X11 chromium it just triggers a KDE icon bouncing cursor, but nothing else happens. In Wayland Chromium it triggers an immediate crash of Chromium.

In Firefox (Wayland) Teams web app at least prints out a message that video is not working.

I've tested in all above mentioned browser versions that screen-sharing is working just fine through (gUM Test Page). So it is a teams-specific problem.

Is it just me or it really stopped working after some update? Does anybody know of  a workaround? I didn't try Gnome since I'd like to stick with Plasma.

Offline

#2 2025-05-28 11:45:10

Avenger
Member
Registered: 2005-11-11
Posts: 66

Re: Unable to share screen in web Teams on KDE Plasma Wayland

I have the exact same issue.

I was able to get screen share to work using the Microsoft edge stable browser from AUR.

I've got some other unrelated issues with that browser though, so it's not optimal.

I see there's another thread relating the issue to the Plasma Integration plugin:
https://bbs.archlinux.org/viewtopic.php?id=305299

I was able to fix the issue in Chromium by removing the plugin.

Last edited by Avenger (2025-05-28 11:49:02)

Offline

#3 2025-05-28 11:49:11

tokko
Member
Registered: 2025-05-28
Posts: 1

Re: Unable to share screen in web Teams on KDE Plasma Wayland

I have the same issue. Screen sharing fails with Teams, but it works with Google meet. I have tested Firefox and Chromium. I first noticed issue back in 14th of May.

I' using latest nvidia provided drivers 570.153.02-1, KDE plasma desktop on Wayland.

System logs from firefox unit is a single line

'loop->recurse > 0' failed at ../pipewire/src/pipewire/thread-loop.c:425 pw_thread_loop_wait()

The errors from browser console right after the issue are:

callingAgents: calling-stack [JS.TsCalling.MediaAgent] ffffffff: MA/DeviceManager/MediaStreamManager could not start media stream: 4, total streams: 2, error: AbortError: The fetching process for the media resource was aborted by the user agent at the user's request. <anonymous code>:1:145535
callingAgents: calling-stack [JS.TsCalling.MediaAgent] ffffffff: MA/DeviceManager getMediaStream() error: AbortError: The fetching process for the media resource was aborted by the user agent at the user's request. <anonymous code>:1:145535
ErrorStateProvider: Reported error for scenario unhandled_rejection_error: 20 <anonymous code>:1:145535
ErrorStateProvider: showOops: false, errors: [errorCode:20;filename:;lineno:undefined;colno:undefined] <anonymous code>:1:145535
ErrorStateProvider: extractedError:  {"name":"AbortError","message":"The fetching process for the media resource was aborted by the user agent at the user's request.","stack":[]} <anonymous code>:1:145535
ErrorStateProvider: stack:  <empty string> 

Offline

Board footer

Powered by FluxBB