[Bug]: Teams doesn't connect on Start-Up; won't minimise to tray

[cement-head]

Can you reproduce this bug in the PWA?

No

Describe the bug

The latest DEB build/update won't sign-in at start-up, or resume from suspend

What package are you using?

deb

Version

1.12.6

Reproduction steps

1. Teams-For-Linux won't sign-in at start-up, or at resume (from suspend)
2. Issue seems to be be a hang with connecting to the NETWORK
3. Manually XKILL Teams-For-Linux and restarting resolves the issue; maybe a race consition of TEAMs starting too early before the OS (pop-os/Ubuntu) network sub-system is ready?
...

Expected Behavior

1.
2.
3.
...

Debug

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

Additional context

No response

[JasonRaveling]

I am possibly experiencing the same issue on 1.12.6 and 1.12.7 of the AppImage. @cement-head, could you please provide the output of teams-for-linux --webDebug --logConfig='{}' for the dev to understand what is going on.

Here is mine in case @cement-head and I are experiencing the same issue. If it turns out to be different, I'll open a separate issue. Side note, I did use "Quit (Clear Storage)" last time I closed the app.

# /teams-for-linux-1.12.7.AppImage --no-sandbox --webDebug --logConfig='{}'

No config file found, using default values
all good with appLogLevels you aren't using them
Initialising logger with config: "{}"
11:52:04.341 › File logging at /home/SOMEUSER/.config/teams-for-linux/logs/main.log with level silly
11:52:04.343 › Console logging enabled with level silly
11:52:04.343 › Logger initialised
11:52:04.343 › configPath: /home/SOMEUSER/.config/teams-for-linux
11:52:04.344 › configFile: {}
11:52:05.201 › processArgs: [
 '/tmp/.mount_teams-v4luld/teams-for-linux',
 '--no-sandbox',
 '--webDebug',
 '--logConfig={}'
]
11:52:05.202 › testing RegExp processArgs false
11:52:05.202 › testing RegExp processArgs false
11:52:05.202 › testing RegExp processArgs false
11:52:05.202 › testing RegExp processArgs false
11:52:05.203 › Waiting for network...
11:52:05.203 › Testing network using net.request() for https://teams.microsoft.com
11:52:05.204 › Spellchecker is disabled!
11:52:05.484 › Network test successful with method https
11:52:05.484 › Loading initial URL...

It seems to just hang out forever on that last line.

[IsmaelMartinez]

Just to confirm, you aren't having this issue in the website (going to https://teams.microsoft.com).

Can you try without the --no-sandbox? That will not allow the app to link with the website. It is unfortunately needed in order to be able to improve the functionality ms provides.

[IsmaelMartinez]

@cement-head , can you provide some logs? without them this just becomes a guess work. Thanks

[IsmaelMartinez]

I would guess apparmour profile missing. See #1426 (comment)

[JasonRaveling]

Just to confirm, you aren't having this issue in the website (going to https://teams.microsoft.com/).

I can log in at teams.microsoft.com. That is what I'm having to do for now. I'm on Ubuntu LTS. I just tried the suggestion at #1426 (comment) and now I no longer need to do use the --no-sandbox flag. Unfortunately, I still hang on Loading initial URL.... Here is the output now.

# ./teams-for-linux-1.12.7.AppImage --webDebug --logConfig={}
No config file found, using default values
all good with appLogLevels you aren't using them
Initialising logger with config: "{}"
08:26:44.187 › File logging at /home/SOMEUSER/.config/teams-for-linux/logs/main.log with level silly
08:26:44.188 › Console logging enabled with level silly
08:26:44.188 › Logger initialised
08:26:44.188 › configPath: /home/SOMEUSER/.config/teams-for-linux
08:26:44.188 › configFile: {}
08:26:44.955 › processArgs: [
  '/tmp/.mount_teams-pkO5f7/teams-for-linux',
  '--webDebug',
  '--logConfig={}'
]
08:26:44.956 › testing RegExp processArgs false
08:26:44.957 › testing RegExp processArgs false
08:26:44.957 › testing RegExp processArgs false
08:26:44.957 › Waiting for network...
08:26:44.957 › Testing network using net.request() for https://teams.microsoft.com
08:26:44.959 › Spellchecker is disabled!
08:26:45.282 › Network test successful with method https
08:26:45.282 › Loading initial URL...

On the note of versions, here is the debugging output from 1.12.6, which also hangs with the same experience but slightly different output.

./teams-for-linux-1.12.6.AppImage --webDebug --logConfig={}
No config file found, using default values
all good with appLogLevels you aren't using them
Initialising logger with config: "{}"
08:29:12.444 › File logging at /home/SOMEUSER/.config/teams-for-linux/logs/main.log with level silly
08:29:12.446 › Console logging enabled with level silly
08:29:12.446 › Logger initialised
08:29:12.446 › configPath: /home/SOMEUSER/.config/teams-for-linux
08:29:12.446 › configFile: {}
08:29:13.203 › processArgs: [
  '/tmp/.mount_teams-ZxjhEh/teams-for-linux',
  '--webDebug',
  '--logConfig={}'
]
08:29:13.204 › testing RegExp processArgs false
08:29:13.204 › testing RegExp processArgs false
08:29:13.204 › testing RegExp processArgs false
08:29:13.205 › Waiting for network...
08:29:13.205 › Testing network using net.request() for https://teams.microsoft.com
08:29:13.206 › Spellchecker is disabled!
08:29:13.497 › Network test successful with method https

[IsmaelMartinez]

@JasonRaveling , did you do the 'close and clear cache' ? The other option I would suggest is re-installing but remembering to remove the whole /home/SOMEUSER/.config/teams-for-linux/ folder (the clear cache option only removes some files).

Microsoft is deprecating the v1 version that you are using, so maybe is related to that and you should be going to https://teams.microsoft.com/v2 . Does it redirect you to this 'v2' url when you go to via the browser?

[JasonRaveling]

Thanks for the suggestion, @IsmaelMartinez. Unfortunately, I am still getting similar output. I did rm -rf ~/.config/teams-for-linux then I launched the AppImage and it still hangs at "Loading initial URL...". In case it is helpful, I am on Ubuntu 24.04.1 LTS, with kernel 6.8.0-52-generic (64bit) on KDE Plasma 5.27.11.

# ./teams-for-linux-1.12.7.AppImage --webDebug --logConfig='{}'
No config file found, using default values
all good with appLogLevels you aren't using them
Initialising logger with config: "{}"
08:22:03.363 › File logging at /home/SOMEUSER/.config/teams-for-linux/logs/main.log with level silly
08:22:03.365 › Console logging enabled with level silly
08:22:03.365 › Logger initialised
08:22:03.365 › configPath: /home/SOMEUSER/.config/teams-for-linux
08:22:03.365 › configFile: {}
08:22:04.177 › processArgs: [
  '/tmp/.mount_teams-SqbLNn/teams-for-linux',
  '--webDebug',
  '--logConfig={}'
]
08:22:04.178 › testing RegExp processArgs false
08:22:04.179 › testing RegExp processArgs false
08:22:04.179 › testing RegExp processArgs false
08:22:04.179 › Waiting for network...
08:22:04.180 › Testing network using net.request() for https://teams.microsoft.com
08:22:04.181 › Spellchecker is disabled!
08:22:04.596 › Network test successful with method https
08:22:04.597 › Loading initial URL...

[IsmaelMartinez]

@JasonRaveling , are you able to check what happens with deb? I am getting confused as the initial issue mentions 'deb' but I can see you using AppImage. Just to rule out if it is an AppImage issue for you.

[JasonRaveling]

I was curious about that as well, @IsmaelMartinez, but ran out of time yesterday. I deleted ~/.config/teams-for-linux and updated the path in /etc/apparmor.d/teams-for-linux to the location in /opt. Sorry to say, I just tried and got the same exact output/problem with the .deb.

[JasonRaveling]

I just figured out the issue. It has something to do with GPU. I was testing VSCode out recently and noticed similar behavior. Both teams-for-linux and VSCode were starting but just sitting there with a blank window. A suggestion with VSCode is to pass --disable-gpu. When I passed the --disable-gpu flag when starting teams-for-linux, it works. So the following got it running. I have an nvidia GeForce RTX 3050 Ti Mobile.

./teams-for-linux-1.12.7.AppImage --disable-gpu

This makes me wonder if it was an update to Ubuntu or the nvidia drivers. I'm not sure if there is anything you can do. At least this narrows it down.

[IsmaelMartinez]

Great! Glad you found a solution and thanks for sharing how you fix it!