Closed Zsar closed 2 months ago
Have you tried using the config option called sometimes like 'closeAppOnCross' (or something like that). By default it minimises the app, not terminates it, but that flag should terminate the app
offtopic, but those:
GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
are clogging the log, can these be removed?
@joakim-tjernlund , you can change the config level to be higher than debug, as those are debug messages they should disappear in principle.
See https://github.com/IsmaelMartinez/teams-for-linux/blob/develop/app/config/README.md
Closing as closeAppOnCross should fix the original question. Please report back with more information if that is not what the question was about.
@joakim-tjernlund , you can change the config level to be higher than debug, as those are debug messages they should disappear in principle.
See https://github.com/IsmaelMartinez/teams-for-linux/blob/develop/app/config/README.md
I was thinking not to see these ever, they just clog up the log anyway. A compromise would be to only log those if they changed.
The default log level is 'silly' ...
Describe the bug When the application is started on a command line via
teams-for-linux
, it starts polling in the form of16:36:11.324 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
.When the application is closed, it never stops polling, nor does it return control to the command prompt.
To Reproduce Steps to reproduce the behavior:
$ teams-for-linux
=> polling starts, the GUI opens, Teams can be used normallyExpected behavior The application terminates shortly after being closed. As normal for applications.
Screenshots The second line is emitted when closing the application. It repeats at the end after terminating the application forcefully with Ctrl+C, but none of the other lines associated with termination are present before that moment.
Desktop (please complete the following information):
Debug (Abbreviated step 3 to just one test call. Apparently it can be completely omitted.)
Additional context fresh first-time installation, no restarts