chromium 111 and 112 have the wrong architecture in the user agent
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
chromium-browser (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Using chromium browser on ubuntu bionic (the apt version), the wrong user agent is present in chromium 111 and 112. When testing the arm64 build, the user agent is expected to contain the string aarch64 however it contains the string x86_64. I am not aware if i386 and armhf builds are also affected by this or not. This was not an issue in chromium 110 builds, they had the correct user agent. I am assuming this is likely an issue with chromium source and not packaging in particular.
On the other hand, using x86_64 fixes a bug that youtube has on aarch64 user agent, where it thinks it's a Hisense TV and limits max resolution to 480p since chromium 110+. playback debug info from youtube to show that:
```
{
"ns": "yt",
"el": "detailpage",
"cpn": "HFfQQ5-Ud1Xq31GM",
"ver": 2,
"cmt": "0",
"fmt": "247",
"fs": "0",
"rt": "3.724",
"euri": "",
"lact": 3,
"cl": "525275539",
"mos": 0,
"state": "49",
"volume": 100,
"cbrand": "hisense",
"cbr": "Chrome",
"cbrver": "110.0.0.0",
"c": "WEB",
"cver": "2.20230421.01.00",
"cplayer": "UNIPLAYER",
"cmodel": "65a67gevs",
"cos": "X11",
"cplatform": "TV",
"hl": "en_US",
"cr": "US",
"len": "41920.021",
"fexp": "23776346,
"feature": "g-high-rec",
"afmt": "251",
"muted": "0",
"docid": "HA7emw-FIjs",
"ei": "welFZNqxGPik0_
"plid": "AAX6C8oUWaU74VL5",
"referrer": "https:/
"sdetail": "p:/",
"sourceid": "y",
"of": "xjLV454MDgULLB
"vm": "CAQQARgBOjJBTE
"vct": "0.000",
"vd": "41920.021",
"vpl": "",
"vbu": "0.000-7.000",
"vpa": "0",
"vsk": "0",
"ven": "0",
"vpr": "1",
"vrs": "1",
"vns": "2",
"vec": "null",
"vemsg": "",
"vvol": "1",
"vdom": "1",
"vsrc": "1",
"vw": "693",
"vh": "390",
"lct": "0.000",
"lsk": false,
"lmf": false,
"lbw": "152435.812",
"lhd": "1.635",
"lst": "0.000",
"laa": "itag_251_
"lva": "itag_247_
"lar": "itag_251_
"lvr": "itag_247_
"laq": "220089",
"lvq": "214435",
"lab": "0.000-8.461",
"lvb": "0.000-7.000",
"ismb": 13290000,
"leader": 1,
"relative_
"optimal_format": "720p",
"user_qual": 720,
"release_
"debug_videoId": "HA7emw-FIjs",
"0sz": "false",
"op": "",
"yof": "false",
"dis": "",
"gpu": "ANGLE_
"debug_
"debug_date": "Sun Apr 23 2023 22:30:34 GMT-0400 (Eastern Daylight Time)"
}
```
Thanks for the bug report and sorry for the delay responding to this.
Is there an unwanted behavior resulting from this mismatch? You mention that the mismatch fixes Youtube playback so it wouldn't look worth "fixing" this?