Recording never captures the screen share

[azekeil]

Describe the bug On Fedora 40 with Wayland. Recording a meeting works as expected, with the exception that only the users' webcams are shown, never the shared content. This occurs whether I start recording then share the screen, or share the screen then start recording. I always share a window as I have a 4k screen. Users on the call can see my screen share fine.

To Reproduce Steps to reproduce the behavior: As above

Expected behavior Screen Recording captures screen share

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Fedora 40
• Installation package: rpm
• Version: 1.11.1

Debug When possible, please run the application from the terminal using --webDebug and try to reproduce the error.

The provide in this section the output from both the terminal and the browser debug console.

teams-for-linux --webDebug --logConfig='{}'

IMPORTANT: Ensure that you mask any sensitive information before posting the output.

Additional context Add any other context about the problem here.

[IsmaelMartinez]

Hi @azekeil, thanks for reporting.

Can you check if this also happens when using the browser version? It could be also related to wayland (some users do report issues with wayland and screen sharing).

Also, if you can provide some logs as the template suggest, it might help identify the issue.

[jijojosephk]

When you say recording, are you referring to the recording feature in the teams? Probably it can't record 4K.

[azekeil]

Hi, apologies I haven't had time to try to capture this on my work machine, plus I have security concerns about uploading the log files which is giving me pause there.

When I select sharing, it offers me (from memory) HD, FHD, 2K and 4K as options. I usually select 2K for recording a window (note I'm recording a window, not my whole screen) as I usually have my window slightly larger than 1/4 of the screen.

And yes, I am then talking about the teams recording feature.

[IsmaelMartinez]

Without the logs is a bit more of a guess work, that can take much longer, but lets try to see where we get to.

A few things you can try are:

• to do the screen share in the browser version and see what results you get.
• using an older version of the app. In the releases section you can see the changes. My initial suspicions tend to do with electron upgrades, that is the framework we use. Try:
• • 1.11.3 got the latest version of electron (33), it might be worth checking it in case is related to some changes in between.
• • 1.10.3 is an older version (30) that was pretty stable

Otherwise, check in the logs and search the close issues for parts of those logs.

If you identify anything in the logs that is concerning to be public, do please let me know.

There is a section on what we use for logs that should hopefully explain how all that area works. Do let me know if you got any questions about it.

Thanks in advance and let me know how you get on.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue was closed because it has been stalled for 5 days with no activity.