[Bug 54296] New: Google Chrome (for Windows) crashes on start
https://bugs.winehq.org/show_bug.cgi?id=54296 Bug ID: 54296 Summary: Google Chrome (for Windows) crashes on start Product: Wine Version: 7.22 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: kohen.d(a)gmail.com Distribution: --- Created attachment 73864 --> https://bugs.winehq.org/attachment.cgi?id=73864 log of an attempted launch Since version 106, Google Chrome stopped running on Wine, it seems. Someone else mentioned it in the forum: https://forum.winehq.org/viewtopic.php?t=37086 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 Brendan Shanks <bshanks(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bshanks(a)codeweavers.com --- Comment #1 from Brendan Shanks <bshanks(a)codeweavers.com> --- This is a dupe of bug 53835. It's been fixed in upstream Chromium, and Chrome 110 should be working. I also got it merged back to Chrome 109, but the current stable build does not have the fix, I'm hoping the next 109 update should have it. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 --- Comment #2 from Brendan Shanks <bshanks(a)codeweavers.com> --- The latest stable release of Chrome on Windows (109.0.5414.119/.120, released yesterday) should now have the fix. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 Louis Lenders <xerox.xerox2000x(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xerox.xerox2000x(a)gmail.com --- Comment #3 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (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 Same holds for googlechrome version 110* Any idea what's needed next? Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 --- Comment #4 from Louis Lenders <xerox.xerox2000x(a)gmail.com> --- (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"? Regards ' -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 --- Comment #5 from Brendan Shanks <bshanks(a)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=chromium (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 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 --- Comment #6 from Louis Lenders <xerox.xerox2000x(a)gmail.com> ---
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
Hi Brendan, I just tested, and this patch https://bugs.winehq.org/attachment.cgi?id=73615 from bugreport https://bugs.winehq.org/show_bug.cgi?id=53981 is the only patch needed to get a working chrome.exe without the --no-sandbox option (which was also possible several months ago before trouble began) With that patch it starts fine and I can browse sites (Version 109.0.5414.120 (Official Build) (64-bit)). Any chance someone could pick the patch up to get it merged? Thanks and regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 Fabian Maurer <dark.shadow4(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4(a)web.de --- Comment #7 from Fabian Maurer <dark.shadow4(a)web.de> --- Any news on this? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 --- Comment #8 from Fabian Maurer <dark.shadow4(a)web.de> --- Chromium seems to work fine for me, google chrome seems to have some issues. Could be related to 0488:err:combase:RoGetActivationFactory Failed to find library for L"Windows.UI.ViewManagement.InputPane" If you have issues, can you please tell me the exact program you're trying? Also, make sure to run chrome/ium from inside the WINEPREFIX, do not run it from outside. It does NOT like that, could result in this kind of error. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54296 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=54296 KRosUser <kyle.kcsoftwares@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kyle.kcsoftwares@gmail.com --- Comment #9 from KRosUser <kyle.kcsoftwares@gmail.com> --- Any recent test on Wine 11.7 or later ? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (2)
-
WineHQ Bugzilla -
WineHQ Bugzilla