| Summary: | Chromium browser; outgoing voice does not work with Teams | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Markus Robert Keßler <mandrake> |
| Component: | RPM Packages | Assignee: | christian barranco <chb0> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | chb0 |
| Version: | 9 | Keywords: | FOR_ERRATA9 |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | chromium-browser-stable-119.0.6045.159-1.mga9.tainted.src.rpm | CVE: | |
| Status comment: | |||
Thank you for the report, and the workaround you found. The current M9 version chromium-browser-stable-119.0.6045.159 is the only one so far. Can you post the actual 'user agent' being sent that Teams dislikes? CC:
(none) =>
lewyssmith I think this must be reported to MS @Markus Did you try fake user agent to one of current goggle chrome? Good point! Can you name one, and I test it tomorrow :-) Hi,
I wrote a server-app, see here:
http://dipl-ing-kessler.de/show_my_browserstring.shtml
and when invoked from the most recent MGA9-Chromium-Browser, it says:
User Agent information sent from your browser:
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36
It looks to me that M$ do not check routines, methods etc. and their capabilities, instead they adjust Teams' behaviour according to the user-agent-string...
My user agent extension suggest this Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.5786.212 Safari/537.36 and to fake a MS version Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36 (In reply to Lewis Smith from comment #1) > The current M9 version chromium-browser-stable-119.0.6045.159 is the only > one so far. I was wildly wrong, just noticed these earlier M9 versions: chromium-browser-stable-116.0.5845.96-1 chromium-browser-stable-116.0.5845.140-1 chromium-browser-stable-117.0.5938.132-1 chromium-browser-stable-118.0.5993.70-1 chromium-browser-stable-118.0.5993.117-1 @Markus 1. Please say what exact version you are using: $ rpm -q chromium-browser-stable 2. You could try downgrading to an earlier version to test at what point the problem arose. Starting with the oldest (M9 issued). I think, for example: # urpmi --downgrade chromium-browser-stable-116.0.5845.96-1.mga9 [but am never sure exactly how to end the package-ID] Try one for Edge linux also Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1788.0 @Lewis: 1. $ rpm -q chromium-browser-stable chromium-browser-stable-119.0.6045.159-1.mga9.tainted 2. From http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/x86_64/media/tainted/updates/ I can remember having used from 118.* up to the most recent. Well, next I'll try to fake google and edge tomorrow and let you know about the outcome Tested each with chromium-browser-stable-119.0.6045.159-1.mga9.tainted To be on the safe side, reproduced: chromium-browser --user-agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.128 Safari/537.36" servername ==> works down-/upstream Then: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.5786.212 Safari/537.36" ==> outgoing voice doesn't work "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36" ==> first got asked for "xdg open" and if wanting to "continue in this browser" ==> outgoing voice doesn't work "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edg/114.0.1788.0" ==> outgoing voice doesn't work Thank you for your careful experiments. Quite clear, just the first list works. This is very like katnatek's suggestion comment 7, and others of yours. Markus (works): Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.128 Safari/537.36 ~~~~~~~~~~~~~~~~~~~~ katnatek (does not work; I put the 'e' in Edge): Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36 Edge/114.0.1788.0 ~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~ And Markus's nearest thing which did not work for outgoing voice was: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.5786.212 Safari/537.36 —-------------------- where it looks that only the Chrome *version* differs! I do not have this to play with, and do not want it. Can someone say how (or whether) a user can define this within Chrome settings; or does it need the command-line launch as at the start of the previous comment? CC'ing squidf who nurses the package. CC:
(none) =>
chb0 Hi. Just made a test, creating a Teams invitation using my professional account. Well, everything works out of the box for me (video and sound, 2-way street). My user agent is: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Don't know what to say more here... Thanks for that, Christian. Just like Chrome/89.0.4389.128 which works for Markus; where Chrome/116.0.5786.212 did not, quite. Over to Markus to try that, please: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 Where does the exact user agent come from, get defined? (In reply to Lewis Smith from comment #12) > Thanks for that, Christian. > Just like Chrome/89.0.4389.128 which works for Markus; where > Chrome/116.0.5786.212 did not, quite. > > Over to Markus to try that, please: > Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) > Chrome/119.0.0.0 Safari/537.36 > > Where does the exact user agent come from, get defined? It is hard-coded during the build. @christian barranco: Are you using a proxy server between your machine and teams server or can you access teams server directly? Me and my colleagues are forced to go through vpn *AND* (company-internal) proxy to access teams. Otherwise teams server refuses to accept the connection. Maybe there is some content-filtering done, somehow. Thanks! Hi. Direct internet connection worked for me. No need of proxy. Thanks, Christian! The funny thing is, I tried the same on Ubuntu 23.10 this afternoon (chromium browser 119, connected via openconnect and same proxy) and there it worked. Wireshark was no help because every video/audio block is TLS-encrypted, so I saw nothing helpful. In Mageia, when I switched the microphone off in pavucontrol, then teams complained about it. Hence, teams "sees" the microphone but the signal is not routed to teams server. Really weird. Thanks anyway! I am lost about whether you get our version 119.0.6045.159 to work with its built-in user agent (comment 11): "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36" or only with your working example in comment 9: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.128 Safari/537.36" servername (In reply to Markus Robert Keßler from comment #16) > The funny thing is, I tried the same on Ubuntu 23.10 this afternoon > (chromium browser 119, connected via openconnect and same proxy) and there > it worked. Can you give the user-agent it sends? Summary:
Chromium browser not supported by Teams =>
Chromium browser; outgoing voice does not work with Teams Hi Markus. It would be interesting to know which user agent was sent by Ubuntu. Because, even if it seems to play a role, my feeling is the root cause is somewhere else. Thanks Hi, user agent sent from ubuntu: "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36" Thanks Forgot to mention: I tried in Mageia and in Ubuntu both openconnect vpn with and without vpn split to exclude side effects originating from different routes set (In reply to Markus Robert Keßler from comment #19) > user agent sent from ubuntu: > "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) > Chrome/119.0.0.0 Safari/537.36" This is identical to our 'out-of-the box', comment 11. Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 both of which - Ubuntu [c16] & Mageia [c11] - work correctly. Markus started "Any version of chromium browser out of MGA9 is not supported by Micro$oft Teams when used "out of the box"" Comment 11 shows this is not true. So one has to agree with comment 18: "my feeling is the root cause is somewhere else". But where? Sound has been turbulent for Mageia 9, between PulseAudio & Pipewire & Wireplumber. (In reply to Lewis Smith from comment #21) > (In reply to Markus Robert Keßler from comment #19) > > user agent sent from ubuntu: > > "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) > > Chrome/119.0.0.0 Safari/537.36" > This is identical to our 'out-of-the box', comment 11. > Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) > Chrome/119.0.0.0 Safari/537.36 > both of which - Ubuntu [c16] & Mageia [c11] - work correctly. > > Markus started "Any version of chromium browser out of MGA9 is not supported > by Micro$oft Teams when used "out of the box"" > Comment 11 shows this is not true. > So one has to agree with comment 18: > "my feeling is the root cause is somewhere else". > But where? Sound has been turbulent for Mageia 9, between PulseAudio & > Pipewire & Wireplumber. Interesting observation. Let us build on that. I am using Pipewire with Wireplumber. Markus, what about you? If not, would you mind give it a try with Pipewire? For a seamless configuration change (even back and forth), I recommend to use pa-switcher package from MGA repo. Hi, I just installed "task-pipewire" and repeated the test. I saw every microphone (headset, studio microphone, internal mic.) multiple times, but whatever I had selected, it did not work. Instead, Teams told me "your microphone is not working". So, meanwhile I switched back to ALSA / Pulse. (In reply to Markus Robert Keßler from comment #23) > Hi, > I just installed "task-pipewire" and repeated the test. > I saw every microphone (headset, studio microphone, internal mic.) multiple > times, but whatever I had selected, it did not work. Instead, Teams told me > "your microphone is not working". > So, meanwhile I switched back to ALSA / Pulse. That is not enough, you must switch to use pipewire, use the sound wizard in MCC to make the change Re-installed pipewire together with wireplumber, configured in mcc. All the same in Teams. Only difference was that after installing pipewire, my Sandberg USB microphone was no longer accessible. That was also the reason why I've thrown pipewire off the system in Ubuntu, too... Is there anyone else watching this bug who messes with M$ Teams using a microphone and could try this? @christian Would it be easy for you to replace the latest Chromium 119.0.6045.159-1 that you tried successfully comment 11 with one of the earlier versions listed in comment 6? That would test the idea that the version in the user agent has a bearing - assuming the other elements are the same. (In reply to Lewis Smith from comment #26) > Is there anyone else watching this bug who messes with M$ Teams using a > microphone and could try this? > > @christian > Would it be easy for you to replace the latest Chromium 119.0.6045.159-1 > that you tried successfully comment 11 with one of the earlier versions > listed in comment 6? That would test the idea that the version in the user > agent has a bearing - assuming the other elements are the same. Is it to try on my own or to make it available to Markus? Which version do you want me to try? Is it to find one not working with my configuraton? Markus can install any of them. The only versionID that worked for Markus was 89.0.4389.128, comments 0 & 9. I realise now that 116.0.5845.96 looks like what was released with M9, so where - Markus - did you get the older one? Just for yourself Christian, pick any earlier version. I guess they all have the same user agent except for the chromium version. I do not want to put you out, but it seemed from comment 11 that you have things set up for Teams, and simply trying a different browser version would be simple. Apologies if this is not so. @Markus: Another point too obvious: can you try a different browser? @Lewis: Yes, I did. In firefox it worked, so this was my "fallback solution", though firefox does not support audio settings like chromium-based browsers. Firefox instead relies on std-settings from pavucontrol, and (if I remember correctly) there are some other limitations, too. So, I was glad having found a workaround for chromium (In reply to Lewis Smith from comment #28) > Markus can install any of them. The only versionID that worked for Markus > was > 89.0.4389.128, comments 0 & 9. I realise now that 116.0.5845.96 looks like > what was released with M9, so where - Markus - did you get the older one? > > Just for yourself Christian, pick any earlier version. I guess they all have > the same user agent except for the chromium version. I do not want to put > you out, but it seemed from comment 11 that you have things set up for > Teams, and simply trying a different browser version would be simple. > Apologies if this is not so. > > @Markus: > Another point too obvious: can you try a different browser? Hi Lewis. It works for me. So, using a version which worked for Markus would not help, according to me. I would need a version which does not work, IMHO. What I can do is to try behind a vpn. I don't have a proxy in addition to it though. Hi Markus. Sorry if it is a basic thing you have done already. What about the proxy settings in Chromium Settings>System>Open your computer proxy's setting. Is Detect automatically or Use system settings selected? @christian: I do this by setting one certain proxy by its IP as an environment variable on commandline prior to invoking chromium. This also works for outlook, office etc. chromium-browser is a script wrapper, will be interesting to see if ubuntu includes an option that mageia not (In reply to christian barranco from comment #30) > Hi Lewis. It works for me. So, using a version which worked for Markus would > not help, according to me. I would need a version which does not work, IMHO. Markus says: "Any version of chromium browser out of MGA9 is not supported by Micro$oft Teams, when used "out of the box"". So you could try any one of the earlier Mageia 9 versions shown in comment 6. Just one, to confirm that the exact Chromium version posted in the user agent is not the issue. I would do it if I could. (In reply to Markus Robert Keßler from comment #14) > Me and my colleagues are forced to go through vpn *AND* (company-internal) > proxy to access teams. Otherwise teams server refuses to accept the > connection. (In reply to Markus Robert Keßler from comment #32) > I do this by setting one certain proxy by its IP as an environment variable > on commandline prior to invoking chromium. > This also works for outlook, office etc. Markus, are you able to try this problem with a [more] direct link? to test whether it is due to VPN or Proxy. I note "Otherwise teams server refuses to accept the connection", so maybe it is not possible. @Lewis: What exactly do you mean by "[more] direct link", please? Thanks If possible, connecting to Teams without going through the VPN &/or proxy. I have no idea how one does connect, so cannot be more useful. (In reply to Lewis Smith from comment #34) > (In reply to christian barranco from comment #30) > > Hi Lewis. It works for me. So, using a version which worked for Markus would > > not help, according to me. I would need a version which does not work, IMHO. > Markus says: > "Any version of chromium browser out of MGA9 is not supported by Micro$oft > Teams, when used "out of the box"". > So you could try any one of the earlier Mageia 9 versions shown in comment > 6. Just one, to confirm that the exact Chromium version posted in the user > agent is not the issue. I would do it if I could. Hi. I will try with Chromium 116 this weekend. (In reply to Lewis Smith from comment #34) > (In reply to christian barranco from comment #30) > > Hi Lewis. It works for me. So, using a version which worked for Markus would > > not help, according to me. I would need a version which does not work, IMHO. > Markus says: > "Any version of chromium browser out of MGA9 is not supported by Micro$oft > Teams, when used "out of the box"". > So you could try any one of the earlier Mageia 9 versions shown in comment > 6. Just one, to confirm that the exact Chromium version posted in the user > agent is not the issue. I would do it if I could. Hi. Just tested with chromium-browser-stable-116.0.5845.140-1 user agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36 => Teams works with direct connection to internet I then connected via a VPN, => Teams still works So, it remains the proxy effect ? Thanks again Christian. This rather rules out the Chromium version in the user agent being the cause; although right from the beginning that was the only factor that seemed to matter. @Markus What user agent are you actually using to get round the outgoing voice problem? What you gave in comment 0 ? So are you continuing to launch Chromium with that command? I see nothing more we can do other than put this obscure case in Errata. Keywords:
(none) =>
FOR_ERRATA9 > What user agent are you actually using to get
> round the outgoing voice problem?
> What you gave in comment 0 ?
Yes. I perform many meetings per week, and meanwhile I have the right command line ready to use in my bash_history, so I can just invoke it to run Teams :-)
(In reply to Markus Robert Keßler from comment #16) > Thanks, Christian! > The funny thing is, I tried the same on Ubuntu 23.10 this afternoon > (chromium browser 119, connected via openconnect and same proxy) and there > it worked. > Hi. I thought Ubuntu was not building Chromium anymore, but was using the Snap version. Am I wrong? Which version did you use on Ubuntu? Thanks! Yes, in Ubuntu chromium browser is installed as snap. Don't know why they do this but it works (In reply to christian barranco from comment #42) > (In reply to Markus Robert Keßler from comment #16) > > The funny thing is, I tried the same on Ubuntu 23.10 this afternoon > > (chromium browser 119, connected via openconnect and same proxy) and there > > it worked. > Hi. I thought Ubuntu was not building Chromium anymore, but was using the > Snap version. > Am I wrong? Which version did you use on Ubuntu? The answer above: v119 (but not any finer). BTW Markus' link in comment 4 is very good: "User Agent information sent from your browser". Assigning at last to Christian rather than BugSquad. Do not sweat any more about it, you have tried all you can. It is unlikely to be the browser, but some other system configuration - perhaps sound; noting, however, that Firefox works in the same setup. I will note the obscure fault in Errata. Changing to Unconfirmed because no-one else can reproduce the problem. Status:
NEW =>
UNCONFIRMED Did you update your widevine plugin? Perhaps you have an old version of widevine and just work with that user agent? @katnatek: Don't have "widevine" installed, and cannot find it in the repo either. Sorry Hi @katnatek To check if widevine is installed: ls ~/.config/chromium/WidevineCdm Could you also edit /usr/lib64/chromium/chromium-wrapper un remove --disable-features=AudioServiceOutOfProcess There is no guarantee it will work but it is worth a try. Thanks (In reply to christian barranco from comment #47) > Hi @katnatek > > To check if widevine is installed: > ls ~/.config/chromium/WidevineCdm > > Could you also edit /usr/lib64/chromium/chromium-wrapper un remove > --disable-features=AudioServiceOutOfProcess > > There is no guarantee it will work but it is worth a try. > > Thanks I see on some sites suggest that, I'm not use chromium too much just trying to help Also see suggestions to tweak a flag, but I understand that in current version is no longer necessary Hi. Sorry @katnatek. https://bugs.mageia.org/show_bug.cgi?id=32549#c47 was for @Markus @Markus, could you test the wrapper modification? Thanks Hi, tested the modification, though mine is in /usr/lib64/chromium-browser/chromium-wrapper instead of /usr/lib64/chromium/chromium-wrapper but anyway, same outcome. Outgoing voice only when sending useragent string from "description". Hi Markus Would you be able to test chromium-120, currently under tainted/updates_testing? Thanks Without testing and without being able to replicate, I have no other option than closing. Resolution:
(none) =>
WONTFIX |
Any version of chromium browser out of MGA9 is not supported by Micro$oft Teams, when using "out of the box". Everything works, except outgoing voice info is not accepted server-side. Meaning that others hear nothing, the meeting can only be joined "read-only". When setting the user agent option by hand to an older version, then everything works. Example: chromium-browser --user-agent="Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.128 Safari/537.36" servername So, the user agent string that is sent, either contains elements not accepted, or there is something missing in the string, that teams-server demands. The browser itself seems ok.