Microsoft Teams 1.5.00.10453 (64-bit) randomly crashes or freezes every few minutes on Linux with Wayland compositor

Question

question

82844327 asked May 4, '22 John-0478 commented May 12, '22

Microsoft Teams 1.5.00.10453 (64-bit) randomly crashes or freezes every few minutes on Linux with Wayland compositor

I currently use Microsoft Teams Insiders version 1.5.00.10453 on an up-to-date Arch Linux system running a Wayland-based compositor.

The application either freezes (cannot interact with any UI elements anymore) or crashes every 30 minutes on average. It doesn't seem to happen at specific events (like whenever there's an incoming call) but just at random times. Usually, I work on another workspace and when switching to the workspace where Teams is located I find it frozen or not at all (crashed).

The same happens with the "normal" (i.e., non-Insiders) build of Teams of the same version.

I've used previous Teams releases without crashes/freezes until I had to switch over to the flatpak package for some time because of https://techcommunity.microsoft.com/t5/microsoft-teams/teams-for-linux-suddenly-broken-for-others-using-newer-distros/m-p/3178388. Since that issue has been solved in the new Teams release, I'm back to the native Teams package.

I've tried deleting all Microsoft data in ~/.var/Microsoft/, ~/.config/Microsoft/, ~/.config/Microsoft Teams*/ and starting from a clean state but that didn't change anything. I've disabled GPU hardware accelleration and restarted, but again that didn't have a positive effect on the crashes or freezes.

I do have a good dozen crash reports in ~/.config/Microsoft/Microsoft Teams - Insiders/Crash Reports/, all *.dmp binary files. However, it doesn't seem to be a core dump file format recognized by gdb. How do I analyze such a dump?

And is this the right place to report bugs anyhow?

office-teams-windows-itpro office-teams-linux-itpro

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JimmyYang-MSFT · May 05 at 06:36 AM

Hi @TassiloHorn-1694

Does anyone else have the same problem in your organization?

Based on my experience, To collect logs for Linux:

Click on the Microsoft Teams icon in your system tray, and select Get Logs.
The files will be available in ~/.config/Microsoft/Microsoft Teams/logs.txt.

0 ·

Answer 1 · 2022-05-05T07:34:24.17Z

82844327 answered May 5, '22 82844327 published May 5, '22

@JimmyYang-MSFT Thanks, there is indeed a "Collect support files" entry which I haven't seen before because I usually go without a tray which seems to generate a folder ~/Downloads/MSTeams Diagnostics Log<DateTime>/. I'll do that after the next crash/freeze. There's also a ~/.config/Microsoft/Microsoft Teams/logs.txt now which I think hasn't been there before. What should I do with those logs then? Should I upload them somewhere? Do they contain confidential information (so I'd rather not upload them somewhere publicly accessible)?

Wrt. to colleagues: I'm the only one using Linux here. It seems my chaps running windows don't have that issue but I'm not sure they are using the latest release.

Oh, next crash happened just now. ~/.config/Microsoft/Microsoft Teams/logs.txt ends with these log entries which indicate no error AFAICT:

Thu May 05 2022 09:10:35 GMT+0200 (Central European Summer Time) <8243> -- event -- eventpdclevel: 1, profileType: null, status: success, scenario: ac48570e-b37c-43c4-8d52-c77c9aec4b30, scenarioName: toast_endtoend_tracking_desktopclient, name: toast_endtoend_tracking_desktopclient, step: PurpleNotificationService:linuxNotificationShown, sequence: 8, delta: 6, scenarioDelta: 6, elapsed: 7375935, stepDelta: 5, Scenario.Mode: 1, AppInfo.Language: en-US, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 20892072, freeMemory: 656400384, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 0.97, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: maximized, UserInfo.TimeZone: +02:00, vdiMode: 0, Scenario.Name: toast_endtoend_tracking_desktopclient, Scenario.Step: PurpleNotificationService:linuxNotificationShown, Scenario.Status: success,
Thu May 05 2022 09:10:35 GMT+0200 (Central European Summer Time) <8243> -- event -- eventpdclevel: 1, notificationId: ef6ae29a-e126-4b6c-aaae-99f170a10208, profileType: null, notificationStyle: purple_built_in, status: success, scenario: ac48570e-b37c-43c4-8d52-c77c9aec4b30, scenarioName: toast_endtoend_tracking_desktopclient, name: toast_endtoend_tracking_desktopclient, step: stop, sequence: 9, delta: 6, scenarioDelta: 6, elapsed: 7375935, stepDelta: 0, Scenario.Mode: 1, AppInfo.Language: en-US, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 20923584, freeMemory: 656400384, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 0.97, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: maximized, UserInfo.TimeZone: +02:00, vdiMode: 0, Scenario.Name: toast_endtoend_tracking_desktopclient, Scenario.Step: stop, Scenario.Status: success,
Thu May 05 2022 09:10:36 GMT+0200 (Central European Summer Time) <8243> -- event -- eventpdclevel: 2, flashOnBadgeUpdateEventData: , status: success, scenario: 423d903f-8fdd-42ad-b8f4-15b933a279d6, scenarioName: desktop_flash_taskbar_icon, name: desktop_flash_taskbar_icon, step: start, sequence: 0, delta: 0, scenarioDelta: 0, elapsed: 7376171, stepDelta: 0, Scenario.Mode: 1, AppInfo.Language: en-US, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 20987828, freeMemory: 653950976, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 0.97, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: maximized, UserInfo.TimeZone: +02:00, vdiMode: 0, Scenario.Name: desktop_flash_taskbar_icon, Scenario.Step: start, Scenario.Status: success,
Thu May 05 2022 09:10:36 GMT+0200 (Central European Summer Time) <8243> -- info -- badge count from web: 1 window id: undefined
Thu May 05 2022 09:10:36 GMT+0200 (Central European Summer Time) <8243> -- info -- browser window id from ips: undefined
Thu May 05 2022 09:10:36 GMT+0200 (Central European Summer Time) <8243> -- info -- StatusIndicatorStateService: emit status indicator state change from Unknown to NewActivity
Thu May 05 2022 09:10:36 GMT+0200 (Central European Summer Time) <8243> -- info -- StatusIndicatorStateService: Added NewActivity (current state: Unknown -> NewActivity)
Thu May 05 2022 09:10:36 GMT+0200 (Central European Summer Time) <8243> -- event -- eventpdclevel: 2, flashOnBadgeUpdateEventData: eRD;, status: success, scenario: 423d903f-8fdd-42ad-b8f4-15b933a279d6, scenarioName: desktop_flash_taskbar_icon, name: desktop_flash_taskbar_icon, step: stop, sequence: 1, delta: 4, scenarioDelta: 4, elapsed: 7376175, stepDelta: 4, Scenario.Mode: 1, AppInfo.Language: en-US, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 21028836, freeMemory: 654987264, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 0.97, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: maximized, UserInfo.TimeZone: +02:00, vdiMode: 0, Scenario.Name: desktop_flash_taskbar_icon, Scenario.Step: stop, Scenario.Status: success,
Thu May 05 2022 09:10:42 GMT+0200 (Central European Summer Time) <8243> -- info -- Blur main window
Thu May 05 2022 09:10:42 GMT+0200 (Central European Summer Time) <8243> -- info -- Is foreground set to false
Thu May 05 2022 09:10:42 GMT+0200 (Central European Summer Time) <8243> -- event -- eventpdclevel: 2, duration: 60.88600015640259, name: desktop_foreground_duration, AppInfo.Language: en-US, complianceEnvironmentType: 0, isDataCategorizationEnabled: true, userpdclevel: 0, processMemory: 21099964, freeMemory: 713932800, clientType: desktop, AppInfo.ClientType: desktop, batterylevel: 0.97, pluggedin: true, Window.Focus: foreground, windowIsVisible: true, Window.Status: maximized, UserInfo.TimeZone: +02:00, vdiMode: 0,
Thu May 05 2022 09:10:43 GMT+0200 (Central European Summer Time) <8243> -- info -- Focusing main window
Thu May 05 2022 09:10:43 GMT+0200 (Central European Summer Time) <8243> -- info -- Is foreground set to true

If I filter the logs of today for lines with -- error -- in them, I have those (after having at least 8 crashes within the last hour):

2424:Thu May 05 2022 07:07:40 GMT+0200 (Central European Summer Time) <8243> -- error -- getInstallOrUpdateTime failed
2486:Thu May 05 2022 07:07:40 GMT+0200 (Central European Summer Time) <8243> -- error -- Error occurred while saving env_config.json
2615:Thu May 05 2022 07:07:43 GMT+0200 (Central European Summer Time) <8243> -- error -- Error saving cookie
2775:Thu May 05 2022 07:07:45 GMT+0200 (Central European Summer Time) <8243> -- error -- Error saving cookie
2806:Thu May 05 2022 07:07:47 GMT+0200 (Central European Summer Time) <8243> -- error -- video app whitelist is empty
2927:Thu May 05 2022 07:07:51 GMT+0200 (Central European Summer Time) <8243> -- error -- Cannot instantiate ControlInjector: Message: not available
3018:Thu May 05 2022 07:17:40 GMT+0200 (Central European Summer Time) <8243> -- error -- Authentication: Auth incomplete after 10 minutes of no response from url https://teams.microsoft.com
4184:Thu May 05 2022 09:16:10 GMT+0200 (Central European Summer Time) <36590> -- error -- getInstallOrUpdateTime failed
4246:Thu May 05 2022 09:16:10 GMT+0200 (Central European Summer Time) <36590> -- error -- Error occurred while saving env_config.json
4375:Thu May 05 2022 09:16:13 GMT+0200 (Central European Summer Time) <36590> -- error -- Error saving cookie
4568:Thu May 05 2022 09:16:16 GMT+0200 (Central European Summer Time) <36590> -- error -- Error saving cookie
4599:Thu May 05 2022 09:16:17 GMT+0200 (Central European Summer Time) <36590> -- error -- video app whitelist is empty
4718:Thu May 05 2022 09:16:22 GMT+0200 (Central European Summer Time) <36590> -- error -- Cannot instantiate ControlInjector: Message: not available
5002:Thu May 05 2022 09:19:07 GMT+0200 (Central European Summer Time) <37407> -- error -- getInstallOrUpdateTime failed
5064:Thu May 05 2022 09:19:08 GMT+0200 (Central European Summer Time) <37407> -- error -- Error occurred while saving env_config.json
5193:Thu May 05 2022 09:19:10 GMT+0200 (Central European Summer Time) <37407> -- error -- Error saving cookie
5229:Thu May 05 2022 09:19:12 GMT+0200 (Central European Summer Time) <37407> -- error -- video app whitelist is empty
5337:Thu May 05 2022 09:19:18 GMT+0200 (Central European Summer Time) <37407> -- error -- Cannot instantiate ControlInjector: Message: not available
5642:Thu May 05 2022 09:24:25 GMT+0200 (Central European Summer Time) <39103> -- error -- getInstallOrUpdateTime failed
5704:Thu May 05 2022 09:24:26 GMT+0200 (Central European Summer Time) <39103> -- error -- Error occurred while saving env_config.json
5833:Thu May 05 2022 09:24:28 GMT+0200 (Central European Summer Time) <39103> -- error -- Error saving cookie
5869:Thu May 05 2022 09:24:30 GMT+0200 (Central European Summer Time) <39103> -- error -- video app whitelist is empty
5985:Thu May 05 2022 09:24:35 GMT+0200 (Central European Summer Time) <39103> -- error -- Cannot instantiate ControlInjector: Message: not available
6260:Thu May 05 2022 09:25:37 GMT+0200 (Central European Summer Time) <39548> -- error -- getInstallOrUpdateTime failed
6322:Thu May 05 2022 09:25:37 GMT+0200 (Central European Summer Time) <39548> -- error -- Error occurred while saving env_config.json
6451:Thu May 05 2022 09:25:40 GMT+0200 (Central European Summer Time) <39548> -- error -- Error saving cookie
6487:Thu May 05 2022 09:25:41 GMT+0200 (Central European Summer Time) <39548> -- error -- video app whitelist is empty
6611:Thu May 05 2022 09:25:46 GMT+0200 (Central European Summer Time) <39548> -- error -- Cannot instantiate ControlInjector: Message: not available
6860:Thu May 05 2022 09:26:22 GMT+0200 (Central European Summer Time) <39924> -- error -- getInstallOrUpdateTime failed
6922:Thu May 05 2022 09:26:22 GMT+0200 (Central European Summer Time) <39924> -- error -- Error occurred while saving env_config.json
7051:Thu May 05 2022 09:26:25 GMT+0200 (Central European Summer Time) <39924> -- error -- Error saving cookie
7087:Thu May 05 2022 09:26:26 GMT+0200 (Central European Summer Time) <39924> -- error -- video app whitelist is empty
7193:Thu May 05 2022 09:26:31 GMT+0200 (Central European Summer Time) <39924> -- error -- Cannot instantiate ControlInjector: Message: not available
7462:Thu May 05 2022 09:28:11 GMT+0200 (Central European Summer Time) <40442> -- error -- getInstallOrUpdateTime failed
7524:Thu May 05 2022 09:28:11 GMT+0200 (Central European Summer Time) <40442> -- error -- Error occurred while saving env_config.json
7653:Thu May 05 2022 09:28:13 GMT+0200 (Central European Summer Time) <40442> -- error -- Error saving cookie
7689:Thu May 05 2022 09:28:15 GMT+0200 (Central European Summer Time) <40442> -- error -- video app whitelist is empty
7795:Thu May 05 2022 09:28:20 GMT+0200 (Central European Summer Time) <40442> -- error -- Cannot instantiate ControlInjector: Message: not available

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 2 · 2022-05-06T15:49:23.53Z

John-0478 answered May 6, '22 John-0478 commented May 12, '22

On Ubuntu 20.04.4 LTS, Gnome 3.36.8, MS Teams same version as poster.

Fine in large meets but crashes on one to one meets.

Nothing telling within dmesg.

Hardware:
00:02.0 VGA compatible controller: Intel Corporation Device 9bc8 (rev 03)

Nothing besides an id under:

/home/$USER/.config/Microsoft/Microsoft Teams/Crash Reports

Only a brief teams-startup.log under:

/home/$USER/.config/Microsoft/Microsoft Teams/logs

Short of outputting an strace on Teams any ideas?

thanks

John

· 6

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

82844327 · May 09 at 09:26 AM

FWIW, it somehow became much more stable on Friday and today I haven't encountered a single crash since I've started it 5 hours ago...

0 ·

JimmyYang-MSFT 82844327 · May 11 at 10:01 AM

@TassiloHorn-1694

Do you mean this problem has been fixed by itself?

1 ·

82844327 JimmyYang-MSFT · May 11 at 10:38 AM

Yes, it seems like the issue has been fixed somehow although I have no clue how. At least, I didn't update the teams app. So maybe some backend update...

0 ·

Show more comments

John-0478 · May 12 at 10:05 AM

I've switched to using Wifi (previously using a LAN connection) and the Mate desktop, with the hope of isolating the problem.

Problem still persisting on my end, might be related to the above two adjustments.

0 ·

John-0478 John-0478 · May 12 at 12:38 PM

Still got the same issue.

Looks like a local issue on my end:

dmesg:

PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)

Will be good to know if the issue is persisting for other users.

0 ·

Answer 3 · 2022-05-09T09:39:36.72Z

John-0478 answered May 9, '22 82844327 commented May 11, '22

Thanks TassiloHorn-1694 they might have updated something on the backend...?

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

82844327 · May 11 at 10:33 AM

It seem so. I didn't have a crash or freeze in the last few days.

0 ·

question