-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Screen share doesn't work since last update (1.7.3) #1313
Comments
Same problem here. Is there a workaround? Will a rollback to 1.7.2 help? Update: I did a rollback to last version available on Flathub, which seems v1.5.0. Sharing is now working again with this version. |
Same on Ubuntu 5.14.0-1051-oem |
I tried 1.7.2 and then I fixed the build for 1.7.0 and 1.7.1 locally to create the arch package -> none of them worked here. |
Same issue for me with Linux Mint 21.3, also the app is crashing sometimes in the background. This didn't happen with previous release so there must be a recent change triggering this. |
howto allow it in sandbox ? |
on Fedora 40 (Xorg + Nvidia driver ... nvidia/535.179, 6.9.5-200.fc40.x86_64, x86_64)
|
+1 ... same here, Slackware64-15.0, X11 & GNOME 46. 😒 Reverting back to 1.6.1 allows sharing again. |
+1 ... Same Here. Arch Linux. Using teams-for-linux 1.7.3 from the AUR |
Also, with 1.6.1, screen share is working, with 1.7.[1..3] not |
I don't know if anyone else is having trouble receiving incoming calls because the message 'calling...' appears, and after answering, nothing happens. The latest release is a disaster; did anyone even test it beforehand? |
this is another issue I guess. Please separate one issue from another. I realized this sharing problem already on the pre-release but was not able to file an issue/look into the details --> this is Open Source. Everybody is encouraged to support and test pre-releases. I had no issues so far with accepting calls. |
Can confirm screen share is broken in 1.7.3 The new Teams version came from snap today. Since then, no screen or window can be selected for sharing. Client is Ubuntu 22.04 with x11 (since screen share isn't working on wayland as well, but that is another issue). |
I have the same problem I clicked on share but noting anithing happning. I back to 1.6.1 version |
Same here with Teams v1.7.3 on Debian 12 X11 i3wm. |
The same issue on Debian 12 X11 KDE and Debian testing X11 KDE, reverting to 1.6.1 resolves issue. |
Same here. I am using Ubuntu 22.04.4 LTS. |
By the way, screen sharing is only broken under x11. It’s working perfectly fine when under wayland. |
Thanks for reporting. I will put back 1.7.3 as pre-release and go back to 1.6.1 as the latest. I did thought it has been tested as a pre-release enough, but obviously it wasn't. I suspect the issue is around the refactoring on this area ![]() Around this file https://github.com/IsmaelMartinez/teams-for-linux/pull/1291/files#diff-33922750afb4f00fe72934ba21d348e07c9eda191fddcdf19954f3b1efa36b8d but I don't know when I will have time to have a look at it. If you got a problem with 1.6.1, that would be another issue. Apologies for the issue! Refactoring sometimes do create problems. |
I think I see what the issue is. We are no longer calling assignSelectSourceHandler. So line 72 should be: ipcMain.on('select-source', this.assignSelectSourceHandler()); EDIT: I have opened #1315 with a fix. |
…uce" to fix screen sharing
Sorry if not related, but this morning my v1.7.something got "updated" to 1.6.1 by snap. It was intentional to solve this problem? BTW, yesterday screen share was working nicely (I have to login Ubuntu in Xorg instead of Wayland to make it work) |
Confirming fix works on Debian 12 X11 KDE :) |
Aye, I did revert the snap latest to 1.6.1 as 1.7.3 was broken. Once 1.7.4 is out, I will
Thanks for the fix! I left a couple of small changes needed. Basically increase release number etc. Thanks again! |
…uce" to fix screen sharing
…uce" to fix screen sharing
This should be fixed in https://github.com/IsmaelMartinez/teams-for-linux/releases/tag/v1.7.4 |
Really appreciate this, the inofficial teams-for-linux is still light years better than the horrible Teams PWA from Microsoft. |
@camspiers is who deserves the credit! (and the community of contributors that keeps this alive). He did found the problem and put a PR for it. A true legend ;) |
Thank you both @camspiers & @IsmaelMartinez! |
@camspiers & @IsmaelMartinez |
Flatpack should be already out. But they can take a few/many hours. Their way of releasing stuff to people is "unique" |
Understood. Thx for your time and the information. |
confirmed it was released yesterday. It should probably be out tomorrow flathub/com.github.IsmaelMartinez.teams_for_linux#117 |
Describe the bug
I am not able to do screen share anymore during the video call.
I am using Linux Mint Cinnamon (with X11 and Xorg), as it was for all previous versions.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It is supposed to have list of screens/applicaitons where you can select one to share
Desktop (please complete the following information):
Debug
[32623:0624/090904.070133:ERROR:CONSOLE(1)] "Request Autofill.enable failed. {"code":-32601,"message":"'Autofill.enable' wasn't found"}", source: devtools://devtools/bundled/core/protocol_client/protocol_client.js (1)
[DEBUG] Badge count set to '1'
[DEBUG] GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
[DEBUG] Badge count set to '1'
[DEBUG] GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
[DEBUG] Badge count set to '1'
[32623:0624/090917.474849:ERROR:CONSOLE(1)] "Request Target.setAutoAttach failed. {"code":-32601,"message":"'Target.setAutoAttach' wasn't found"}", source: devtools://devtools/bundled/core/protocol_client/protocol_client.js (1)
[32623:0624/090917.692479:ERROR:CONSOLE(1)] "Request Target.setAutoAttach failed. {"code":-32601,"message":"'Target.setAutoAttach' wasn't found"}", source: devtools://devtools/bundled/core/protocol_client/protocol_client.js (1)
[DEBUG] GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
[DEBUG] GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
The text was updated successfully, but these errors were encountered: