Teams turns to idle status too often

[Julien76]

Hi,

I am using Teams-for-Linux on NixOS and with Hyprland, I have set the following config in .config/teams-for-linux/config.json:

{
  "appActiveCheckInterval": 6000,
  "appIdleTimeout": 6000,
  "appIdleTimeoutCheckInterval": 6000,
  "awayOnSystemIdle": false,
  "optInTeamsV2": true
}

With the following setting, I would expect the status not to go idle before 6000s (1.6h) but the app goes to idle after few minutes.

If I launch the app via the terminal, I see that the config is properly read but there is an error with the GetActive call, is that what cause the issue of going idle or am I missing something here?

teams-for-linux --appLogLevels debug --enableDesktopNotificationsHack --enable-features=UseOzonePlatform --ozone-platform=wayland

Terminal output:

[DEBUG] GetSystemIdleState => IdleTimeout: 6000s, IdleTimeoutPollInterval: 6000s, ActiveCheckPollInterval: 6000s, IdleTime: 0s, IdleState: 'active'
[146791:0626/111658.832904:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.UnknownMethod: Unknown method GetActive or interface org.freedesktop.ScreenSaver.

[Julien76]

I made some tests having teams opened next to another window.

I have the mouse cursor in the teams app, my status is available.

When I move the mouse away from the teams app, I set a stopwatch counter. After exactly 5min (300s), teams turn to idle (yellow badge) regardless if I am active or not on my pc. My system is set to be idle after 500s so I don't think it is related to my system settings, as I can constantly replicate the 300s mark at which teams goes idle.

[Julien76]

I made more tests by setting appIdleTimeout to 100s either in the config.json or via passing as an argument when launching teams via the terminal. Teams only go idle after 300s thus not respecting the 100s.

[Julien76]

I created an issue for that as I believe it's a bug:
#1320