teams-for-linux icon indicating copy to clipboard operation
teams-for-linux copied to clipboard

Failure to reconnect after suspend (permanent black window)

Open raul-klg opened this issue 1 year ago • 1 comments

Describe the bug

I run and use the application normally. Sometimes I close laptop lid and I go elsewhere. Laptop suspends to ram. When I open the laptop lid teams-for-linux reconnects correctly, but sometimes (like this time) it does not reconnect.

To Reproduce Steps to reproduce the behavior:

  1. Run application
  2. Wait for connection and load.
  3. Suspend to ram
  4. Open and reconnect in a different network (mobile data or other WLAN)
  5. See error

Expected behavior After wake up from suspend to ram, the application should reconnect normally.

Screenshots

t4l_waiting_for_network

Desktop (please complete the following information):

  • OS: Debian bookwork
  • Installation package targz (tweaked for correct integration with plasma desktop)
  • Version 1.9.1

Debug

12:11:28.963 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
12:13:03.167 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:03.172 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:04.183 › Network test failed with method https
12:13:04.184 › Waiting for network...
12:13:04.185 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:04.187 › Network test failed with method https
12:13:04.188 › Waiting for network...
12:13:04.188 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:05.196 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:05.198 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:06.210 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:06.213 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:07.221 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:07.222 › Testing network using net.request() for https://teams.microsoft.com/v2/
12:13:07.425 › Network test successful with method https
12:13:07.431 › Network test successful with method https
<RED>12:13:09.495 › assignOnDidFailLoadEventHandler : {} - -21 - 
12:13:09.527 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'locked'
<Problem arises>
12:13:19.534 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
12:13:29.536 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'
12:13:39.538 › GetSystemIdleState => IdleTimeout: 300s, IdleTimeoutPollInterval: 10s, ActiveCheckPollInterval: 2s, IdleTime: 0s, IdleState: 'active'

Additional context

It looks like the following line, in red, as an error I assume:

12:13:09.495 › assignOnDidFailLoadEventHandler : {} - -21 - 

may point out the problem

Thanks for your continuous effort on this application.

raul-klg avatar Aug 26 '24 10:08 raul-klg