Closed The-Compiler closed 3 years ago
joakim-tjernlund
commented
3 years ago This hints that some Control should be possible: https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-conferencing/give-control-doesn%E2%80%99t-work-sharescreen
jijojosephk
commented
3 years ago @jijojosephk , OK that was not totally unexpected. I know MS teams is sensitive to removing/adding audio(headsets). Is this better here? Can you plugin USB HS(or bluetooth) after Teams has started ?
I have not faced any issues with audio. Communications with such interfaces varies between OS I've seen issues with official teams application as well. Probably it's there. My headphone is always connected :)
jijojosephk
commented
3 years ago This hints that some Control should be possible: https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-conferencing/give-control-doesn%E2%80%99t-work-sharescreen
Thanks for sharing. I'll have a look at this if it's possible in Chromium engine through Electron we'll definitely handle it.
jijojosephk
commented
3 years ago This hints that some Control should be possible: https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-conferencing/give-control-doesn%E2%80%99t-work-sharescreen
I could not make it work on browser. But the official client works well in this case. It shows a red boarder on the screen and also a tool bar with stop sharing and things like that.
neokore
commented
3 years ago I've tested it with a custom AUR build in Manjaro and it works great, great job from @jijojosephk!
neokore
commented
3 years ago This hints that some Control should be possible: https://docs.microsoft.com/en-us/microsoftteams/troubleshoot/teams-conferencing/give-control-doesn%E2%80%99t-work-sharescreen
I could not make it work on browser. But the official client works well in this case. It shows a red boarder on the screen and also a tool bar with stop sharing and things like that.
AFAIK, this feature is not available on browser. The text where they talk about browsers is just to provide an easy way to check GPU acceleration for their electron instance.
joakim-tjernlund
commented
3 years ago Anyone tested with pipewire? I know there is an issue with MS Teams and pipewire.
neokore
commented
3 years ago Anyone tested with pipewire? I know there is an issue with MS Teams and pipewire.
In my case I'm using PipeWire 0.3.30 on Manjaro with no issues at all. Webcam, screen sharing and audio is OK. Just the already known annoying focus bug from PipeWire, but nothing else.
jijojosephk
commented
3 years ago Anyone tested with pipewire? I know there is an issue with MS Teams and pipewire.
In my case I'm using PipeWire 0.3.30 on Manjaro with no issues at all. Webcam, screen sharing and audio is OK. Just the already known annoying focus bug from PipeWire, but nothing else.
I haven't used PipeWire. Is the focus bug you're talking about is on screenshare preview?
neokore
commented
3 years ago I haven't used PipeWire. Is the focus bug you're talking about is on screenshare preview?
Yes, when I select sharing screen, all the windows focuses very fast (to get a preview of each window I guess) and Teams is left unfocused "at the back of the desktop", so you have to focus it again using alt+Tab or your task bar. It's a bit annoying but it is not a blocking bug and I think it is not related to this project. A possible workaround could be trying to refocus the Teams window after the preview generation, but I'm not sure if this is feasible.
jijojosephk
commented
3 years ago I haven't used PipeWire. Is the focus bug you're talking about is on screenshare preview?
Yes, when I select sharing screen, all the windows focuses very fast (to get a preview of each window I guess) and Teams is left unfocused "at the back of the desktop", so you have to focus it again using alt+Tab or your task bar. It's a bit annoying but it is not a blocking bug and I think it is not related to this project. A possible workaround could be trying to refocus the Teams window after the preview generation, but I'm not sure if this is feasible.
I see. I had created a new issue in electron repo here a few days ago. I'll try to find some workarounds. Thank you. @IsmaelMartinez I'd add this as an issue here. So, we'll keep track of it.
jijojosephk
commented
3 years ago @IsmaelMartinez @skyghis @neokore Focus issue is handled at #440 and has a workaround for now. This is how it looks. All other windows run panicky and teams window just stands there solid. :smile:
danilkhromov
commented
3 years ago Anyone tested with pipewire? I know there is an issue with MS Teams and pipewire.
In my case I'm using PipeWire 0.3.30 on Manjaro with no issues at all. Webcam, screen sharing and audio is OK. Just the already known annoying focus bug from PipeWire, but nothing else.
Is there any specific setup needed in order to make pipewire screen sharing work? I really want to use wayland session but not able to screen share is a no go.
alfsch
commented
3 years ago I've tested the 4K Resolution with 4K main screen and it works :-D What I also noticed was that when I select 2K resolution in teams only a black window is shown to the other user. With FHD all is ok.
jijojosephk
commented
3 years ago I've tested the 4K Resolution with 4K main screen and it works :-D What I also noticed was that when I select 2K resolution in teams only a black window is shown to the other user. With FHD all is ok.
4K genuinely improves quality over FHD or somewhat similar? Was recipient using 4K? Really curious to know the outcome :smile: . Well, 2K is less popular and is wide screen. Both 2K and FHD has the same height only width changes. May be the aspect ratio is causing some troubles for 2K.
alfsch
commented
3 years ago @jijojosephk we saw no difference between 4k and FHD on the other side. But we're really happy to have window's sharing back :+1:
jijojosephk
commented
3 years ago @alfsch, 2K and 4K were experimental. I guess Teams web app along with WebRTC and/or teams APIs interfere with quality. May be it's not supported at the moment. But when the future comes, we're ready :smile: Glad that I could be a help to this group.
DrasLorus
commented
3 years ago Ok! I have customized the AUR PKGBUILD to build directly from the git clone of the develop branch (available as teams-for-linux-git on the AUR). I have tested and everything works on my machine (using pipewire and pipewire-pulse). However, I have no 2K / 4K screen to test.
I have also tested on Wayland (with sway) and screen-sharing don't work, neither on XWayland nor in pure Wayland (using teams-for-linux --enable-features=UseOzonePlatform --ozone-platform=wayland). But It is expected and (I think) unrelated to this issue, wayland window management being very different than X11's (e.g. windows are more isolated, specific APIs needed...).
Funny point: no loose of focus under Wayland. :smiley: So Wayland is unaffected or its associated bugs/incompatibilities compensate or conflict with what causes the focus lost.
Everything else than screen-sharing seems to work well.
jijojosephk
commented
3 years ago @DrasLorus The focus issue is handled here #440 It's a workaround though. It would keep the teams window active though you see some strange things happen behind the window.
simonvanderveldt
commented
3 years ago 1.0.8 worked for me with sharing screens (4K display, shared at 1080p, didn't try the higher options since there's not really any point). Thanks for the fix!
IsmaelMartinez
commented
3 years ago closed as 1.0.8 its out. Thanks a lot @jijojosephk for the resolution and everyone else for testing this.
Describe the bug It looks like screen sharing stopped working recently. It worked fine last week, this week it stopped working. Perhaps something changed on the Teams website in an incompatible way?
To Reproduce Try sharing the screen in a meeting. After clicking "Desktop/Window", nothing happens.
Desktop (please complete the following information):
teams-for-linuxin the Archlinux AURAdditional context Developer console:
Full log: