This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I'm writing to report an issue with screen sharing in Microsoft Teams after updating Microsoft Edge to version 131.0.2903.48 (Official build) (64-bit) this morning (18/11/2024).
The Problem:
When attempting to share my screen in Microsoft Teams through the Edge browser, I can only share the browser window itself. Sharing the entire screen or specific applications is not possible.
Additionally, clicking "Share Screen" causes my camera to turn off with an error message stating "Your video isn't working. We couldn't access your camera."
This issue occurs in both the Microsoft Teams web app within Edge and the standalone Teams desktop application (if available on your platform).
Troubleshooting Attempts:
I have verified that screen sharing works flawlessly in Google Chrome on the same system.
A colleague using Ubuntu 24.04 is experiencing the same problem, suggesting the issue is not specific to Ubuntu 22.04.
Possible Cause:
This issue may be related to the recent Edge update or potential compatibility issues with Ubuntu.
Request:
I would appreciate it if you could investigate this issue and provide a possible solution or workaround. Additionally, please consider escalating this issue to the appropriate team if necessary.
Displaying your screen content to others during a Teams meeting or call for collaboration
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
After raising a support ticket with Microsoft, I was told the following.
Same problem here. When trying to share the following error is seen in the syslog:
2024-11-22T15:08:02.617889+01:00 gjthinkpad gnome-shell[3129]: Object .MetaWindowActorX11 (0x61e1972801c0), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.#012== Stack trace for context 0x61e19609ede0 ==#012#0 7ffdd6c5ac00 b resource:///org/gnome/shell/ui/environment.js:134 (d5684a7f240 @ 15)#012#1 7ffdd6c5ad00 b self-hosted:203 (d5684a97b50 @ 245)#012#2 7ffdd6c5ade0 b resource:///org/gnome/shell/ui/environment.js:134 (d5684a7f100 @ 484)#012#3 7ffdd6c5aeb0 b resource:///org/gnome/shell/ui/environment.js:287 (d5684a7f880 @ 19)#012#4 61e19618b350 i resource:///org/gnome/shell/ui/windowManager.js:1502 (14146a3ea290 @ 724)#012#5 61e19618b2a8 i self-hosted:1461 (28cd323cd6f0 @ 30)#012#6 7ffdd6c5b780 b self-hosted:852 (28cd323cdbf0 @ 15)#012#7 61e19618b218 i resource:///org/gnome/shell/ui/init.js:21 (d5684a70bf0 @ 48)
I confirm also on arch the new release does not solve the issue.
I am just using Firefox for the time being and probably stick to it since it seems to be working just fine
Thanks, I can confirm same on Fedora 41
For time being, I locked working Edge version, so it would not update to non working one. I hope @Microsoft will fix that soon, as this is not solution.
medacant@starship:~$ sudo dnf versionlock add microsoft-edge-stable
Updating and loading repositories:
Repositories loaded.
Adding versionlock on "microsoft-edge-stable = 130.0.2849.80-1".
medacant@starship:~$ sudo dnf versionlock list
Package name: microsoft-edge-stable
evr = 130.0.2849.80-1
medacant@starship:~$ rpm -qa |grep edge
microsoft-edge-stable-130.0.2849.80-1.x86_64
Couple of minutes back a new release was made available for Microsoft Edge with version 131.0.2903.63-1, but the issue still exists!!!!