https://bugs.winehq.org/show_bug.cgi?id=52681
Bug ID: 52681 Summary: Google Chrome Stopped working after 7.2 Product: Wine-staging Version: 7.4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ndk+whq@esperanca.biz CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Hi!
I have been using Google Chrome Portable for some time now.
It was working with some options (--no-sandbox) right until wine-staging-7.3. It stopped starting after 7.3. The installation process from portableapps is smooth, it just does not want to start (no 'usual' black screen, just fails starting).
I have tried to use old wine directory, new wine directory, installed corefonts as someone suggested in some of the bugs, etc. I also have tried to use wine-staging-7.4 with no luck.
After I downgraded back to 7.2 - chrome started working again with --no-sandbox.
The system: the latest Gentoo x64. Video card: AMD Radeon 480 (amdgpu Xorg driver).
Command: WINEPREFIX=/path/to/wine wine /path/to/chrome --no-sandbox
Expected Behavior (works until wine-staging-7.3): Chrome starts and is usable
Actual Behavior (wine-staging-7.3; wine-staging-7.4): Chrome fails to start.
Let me know if there are any debug info is needed (preferrably which options to enable for WINEDEBUG).
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #1 from ndk+whq@esperanca.biz --- To add more details: I have tried to use existing Portable Chrome install as well as the most recent one. The behavior is the same. It seems that there was a retrogression between 7.2 and 7.3.
https://bugs.winehq.org/show_bug.cgi?id=52681
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://portableapps.com/ap | |ps/internet/google_chrome_p | |ortable Keywords| |download, regression Severity|critical |normal
--- Comment #2 from Austin English austinenglish@gmail.com --- It would be helpful if you could run a regression test, see: https://wiki.winehq.org/Regression_Testing https://wiki.winehq.org/Wine-Staging#Regressions_between_Staging_versions
https://bugs.winehq.org/show_bug.cgi?id=52681
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.shadow4@web.de
--- Comment #3 from Fabian Maurer dark.shadow4@web.de --- Just tested "GoogleChromePortable_99.0.4844.74_online.paf.exe". Starts fine with wine-staging-7.4 and wine-7.4, both using "--no-sandbox".
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #4 from ndk+whq@esperanca.biz --- The bug still exists in wine-staging-7.10.
I finally had some time to do regression testing.
I ran git bisect on the repository. I found out the commit at which chrome stops working: https://gitlab.winehq.org/wine/wine/-/commit/7b233f3032e4850b0f387faef4aae5e...
After git bisect, I did manually checked out the previous commit - it worked. Then checked out the commit above - chrome stops working.
Hopefully, it helps.
Let me know if any additional information is required.
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #5 from ndk+whq@esperanca.biz --- To add more details:
I ran git bisect on versions between wine-7.2 and wine-7.3. I checked out wine from the wine repo: https://source.winehq.org/git/wine.git
I also changed the video card meanwhile (now I have 3070 Ti), so video drivers aren't likely to have any influence.
My system is AMD Ryzen 5900x.
https://bugs.winehq.org/show_bug.cgi?id=52681
ndk+whq@esperanca.biz changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Gentoo Version|7.4 |7.3 Regression SHA1| |7b233f3032e4850b0f387faef4a | |ae5ed6d5175de
https://bugs.winehq.org/show_bug.cgi?id=52681
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Product|Wine-staging |Wine CC|leslie_alistair@hotmail.com | Component|-unknown |-unknown
--- Comment #6 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Based off Regression commit, moving to wine
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- It starts fine here with GoogleChromePortable_103.0.5060.134_Repack_online.paf.exe.
Could you please get a WINEDEBUG=module log?
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #8 from ndk+whq@esperanca.biz --- Created attachment 72824 --> https://bugs.winehq.org/attachment.cgi?id=72824 Wine-staging 7.10 log
This is the log for wine-staging 7.10
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #9 from ndk+whq@esperanca.biz --- Log added. I used latest wine installed (wine-staging-7.10) to make a log.
Let me know if you need that a log for that specific commit.
https://bugs.winehq.org/show_bug.cgi?id=52681
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|7b233f3032e4850b0f387faef4a | |ae5ed6d5175de |
--- Comment #10 from Alexandre Julliard julliard@winehq.org --- Thanks for the log!
It looks like it's assuming that system dlls are loaded at the same address in all processes. The referenced commit is not the real cause of the problem, it's a side effect of the address space layout being different because we are no longer loading all the api-* dlls.
It works fine with Mingw builds, so you should install mingw-w64 and rebuild. For non-Mingw builds it's probably a WONTFIX.
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #11 from ndk+whq@esperanca.biz --- I can confirm that after recompiling on Gentoo with 'mingw' flag it started working.
Thank you!
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #12 from ndk+whq@esperanca.biz --- I do have a question though. If there are fundamental issues with non mingw builds, should it be a hard prerequisite for compiling wine?
It seems like it's still an optional dependency.
https://bugs.winehq.org/show_bug.cgi?id=52681
--- Comment #13 from Alexandre Julliard julliard@winehq.org --- It may become a requirement at some point, yes.
https://bugs.winehq.org/show_bug.cgi?id=52681
Alan alan1010035@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alan1010035@gmail.com
--- Comment #14 from Alan alan1010035@gmail.com --- please consider closing if issue is fixed
https://bugs.winehq.org/show_bug.cgi?id=52681
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Google Chrome Stopped |Google Chrome Stopped |working after 7.2 |working after 7.2 in non-PE | |build
https://bugs.winehq.org/show_bug.cgi?id=52681
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED
--- Comment #15 from Alexandre Julliard julliard@winehq.org --- Marking as WONTFIX for the non-PE build case, since the PE build works fine.
https://bugs.winehq.org/show_bug.cgi?id=52681
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #16 from Gijs Vermeulen gijsvrm@gmail.com --- Closing WONTFIX.