Screen sharing not working

[Gabor-B]

Describe the bug
Screen sharing does not work on an Ubuntu 24.04 system (Lenovo T14 Gen1 Intel laptop). Screen sharing was working correctly until approx 2 weeks ago (mid Oct).
Starting screen sharing with the Mozilla test page does work. https://mozilla.github.io/webrtc-landing/gum_test.html

To Reproduce
Steps to reproduce the behavior:

1. Start Teams, start a meeting
2. Click on 'Share'->'Screen, window or Tab'
3. See error (screenshot)

Expected behavior
Screen sharing does work correcly

Screenshots

Desktop (please complete the following information):

• OS: Ubuntu 24.04.1 LTS
• Installation package snap
• Version: teams-for-linux 1.11.1 691 latest/stable ismaelmartinez -

Debug
see attached files

Additional context

teams_console.log
teams.microsoft.com-1730185135219.log

[Paulorg95]

I have the same problem, any solution?

[Andrew-Cha]

Same issue - annoying.

[MarkJaroski]

I have this too, and am trying everything I can think of to debug it, but so far I haven't collected any useful data.

[MarkJaroski]

I decided to check the webrtc demo page, and got this result. This is in the electron instance launched by teams-for-linux. I got here by running this in the console:

location = 'https://mozilla.github.io/webrtc-landing/gum_test.html'

Then I clicked "Screen Capture".

[oneilonline]

I decided to check the webrtc demo page, and got this result. This is in the electron instance launched by teams-for-linux. I got here by running this in the console:

location = 'https://mozilla.github.io/webrtc-landing/gum_test.html'

Then I clicked "Screen Capture".

How do you get to the teams-for-linux console?

[MarkJaroski]

How do you get to the teams-for-linux console?

In the system-tray menu there's a debug item. That opens the dev tools.

[MarkJaroski]

I tried running from source and sharing works fine there. So I guess this has to do with the snap sandbox.

[MarkJaroski]

I tried reinstalling the snap with --classic, but it didn't help.

[IsmaelMartinez]

snap installations sometimes are a pain and can have this side effects. I would recommend using one of the many other packaging systems we provide.

[MarkJaroski]

snap installations sometimes are a pain and can have this side effects. I would recommend using one of the many other packaging systems we provide.

I tried the .deb first, but it doesn't seem to be compatible with the locally installed ffmpeg.so.

So far I'm having the best luck with npm run start. But I haven't worked out where to put the config.json file.

[Gabor-B]

Wasnt aware that a deb package is available too. Then ill ditch the snap version, deb seems to work.
MS should cut politics and maintain their own linux version though..

[MarkJaroski]

MS should cut politics and maintain their own linux version though..

They did for a long while, but they weren't nearly as responsive as @IsmaelMartinez.

[Gabor-B]

Yes, they 'did', exactly

[IsmaelMartinez]

If you do npm run run start --logConfig={} it should print where is trying to read the config file from. Otherwise you can edit the config values in the config folder

[MarkJaroski]

FWIW, it turns out that my issue with the debian package was #1426.

I spent a little time working on an apparmor policy for it, but then just ran it with --no-sandbox.

🤷