The message suggesting posting in the AUR package also says at its very end:
Again, the logs can give us hints on this
So I guess perhaps they're looking for a GDB back trace with symbols instead?
There's also the flag --appLogLevels
and I would set it to debug
, that could be very helpful, but who knows... Besides --disableGPU
how about --disableAutogain
?
The suggestion to ask here doesn't seem useful, at least in my mind, since the issue reported also indicates the same happens on chromium, not sure if tested, which is sort of the same thing, electron is sort of chromium in disguise. Wondering if firefox fails the same... But if it fails in chromium, I don't see how electron would prevent such failure. Perhaps some flags...
BTW, I know indicating work for me doesn't help, but just so you know, I called my phone from teams-for-linux with no issue, and I also joined a meeting with it with no issues. The office laptop I use has camera. I use the stereo jack plug for headset (mic + audio). I use wayland though. The flags I use:
--closeAppOnCross --disableAutogain --ozone-platform-hint=auto --enable-features=WebRTCPipeWireCapturer --enable-features=WaylandWindowDecorations
I disable auto gain in an attempt to prevent teams-for-linux to change the audio volume when closing, but it insists on doing it...
Pinned Comments
pschichtel commented on 2024-04-30 20:18 (UTC) (edited on 2024-04-30 20:19 (UTC) by pschichtel)
Before marking the package out of date, please first check that the new version is not a pre-release. I'm tracking releases, not pre-releases.
jijojosephk commented on 2024-02-05 02:42 (UTC)
Talk to community members here:
https://matrix.to/#/#teams-for-linux_community:gitter.im