https://bugs.winehq.org/show_bug.cgi?id=54296
--- Comment #5 from Brendan Shanks bshanks@codeweavers.com --- (In reply to Louis Lenders from comment #3)
(In reply to Brendan Shanks from comment #2)
The latest stable release of Chrome on Windows (109.0.5414.119/.120, released yesterday) should now have the fix.
Hi Brendan,
I still cannot get chrome.exe to start (chromium 109.0.5414.120)
Interestingly chrome now seems to somehow check if it is ran in wine (?)
grep -r wine_get_version * grep: 109.0.5414.120/Installer/chrome.7z: binary file matches grep: 109.0.5414.120/chrome.dll: binary file matches
Interesting, in the source those mentions are pretty harmless though (and the check in cpuinfo is out-of-date, I may fix that upstream). https://source.chromium.org/search?q=wine_get_version&sq=&ss=chromiu...
(In reply to Louis Lenders from comment #4)
(In reply to Louis Lenders from comment #3)
Small update: It starts fine with "chrome.exe --no-sandbox"
So we're back to old behaviour, right? Any idea how to get this running without "--no-sandbox"?
I honestly don't know when Chrome's sandbox last worked, but there are some bugs filed for various pieces: https://bugs.winehq.org/show_bug.cgi?id=45647 https://bugs.winehq.org/show_bug.cgi?id=53981 https://bugs.winehq.org/show_bug.cgi?id=53983