https://bugs.winehq.org/show_bug.cgi?id=42000
Bug ID: 42000 Summary: Battle.net: invisible window elements with Win7+ mode Product: Wine Version: 1.9.23 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs@winehq.org Reporter: thesource@mail.ru Distribution: ---
Created attachment 56428 --> https://bugs.winehq.org/attachment.cgi?id=56428 wine output on battle.net (Win7 mode)
When OS is set to something higher than Win XP, many elements of Battle.net main windows and dialogs are invisible: authenticator code input dialog is completely blank, online content on the main windows is not displayed. This is different than https://bugs.winehq.org/show_bug.cgi?id=38845 disabling d3dcompiler_46 does not help.
https://bugs.winehq.org/show_bug.cgi?id=42000
Luke Bratch luke@bratch.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |luke@bratch.co.uk
https://bugs.winehq.org/show_bug.cgi?id=42000
Michael Cronenworth mike@cchtml.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mike@cchtml.com
https://bugs.winehq.org/show_bug.cgi?id=42000
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-d3d |-unknown
https://bugs.winehq.org/show_bug.cgi?id=42000
wine-devel@hurrikhan.eu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine-devel@hurrikhan.eu
--- Comment #1 from wine-devel@hurrikhan.eu --- I have the exact same issue. I switched from "Windows 7" to "Windows XP" and now I can see the buttons and captchas. (Diablo III)
wine-staging 2.0
https://bugs.winehq.org/show_bug.cgi?id=42000
Robert Andersson roband@pobox.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |roband@pobox.com
--- Comment #2 from Robert Andersson roband@pobox.com --- Same problem here. Using wine-staging 2.2.
https://bugs.winehq.org/show_bug.cgi?id=42000
Ker noa blue-t@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t@web.de
--- Comment #3 from Ker noa blue-t@web.de --- Possible duplicate of bug 38845
https://bugs.winehq.org/show_bug.cgi?id=42000
wow_on_wine winehq@5csecurity.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winehq@5csecurity.com
--- Comment #4 from wow_on_wine winehq@5csecurity.com --- This is NOT a duplicate of #38845 as the O.P. has stated. I can confirm this bug and have tried everything mentioned in #38845.
There is an option in battle.net loader settings called "Use browser hardware acceleration when available". If this option is enabled then some of the UI elements are missing (most importantly the "Login") button. If this option is disabled however the buttons show up in very ugly fashion underneath the username/password textboxes.
One thing i did notice is that while in 'ugly' mode there is also an error printed to the battle net app itself (not the console) which reads, "Your browser's cookies are disabled. Please reenable cookies to continue.". I doubt that browser cookies would stop UI elements from drawing, (as they are being drawn along with the error message) but it may lead to what is. Who knows.
I will re-enable console logging and take screenshots to attach to this bug.
I'd also like to mention that Blizzard has stated they will stop supporting WindowsXP in the near future and so the "downgrade to winXP mode" is not a viable option at such time. Although I doubt that "not supporting" = "not working" but as new features are implemented thats when problems may arise.
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #5 from wow_on_wine winehq@5csecurity.com --- Created attachment 57500 --> https://bugs.winehq.org/attachment.cgi?id=57500 WINEDEBUG="" logfile
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #6 from wow_on_wine winehq@5csecurity.com --- Created attachment 57501 --> https://bugs.winehq.org/attachment.cgi?id=57501 the option window
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #7 from wow_on_wine winehq@5csecurity.com --- Created attachment 57502 --> https://bugs.winehq.org/attachment.cgi?id=57502 acceleration enabled
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #8 from wow_on_wine winehq@5csecurity.com --- Created attachment 57503 --> https://bugs.winehq.org/attachment.cgi?id=57503 acceleration disabled
https://bugs.winehq.org/show_bug.cgi?id=42000
David Philippi david@torangan.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |david@torangan.de
https://bugs.winehq.org/show_bug.cgi?id=42000
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #9 from winetest@luukku.com --- (In reply to wow_on_wine from comment #8)
Created attachment 57503 [details] acceleration disabled
I get exactly this looking battle.net with wine-staging 2.8 all defaults.
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #10 from winetest@luukku.com --- (In reply to winetest from comment #9)
(In reply to wow_on_wine from comment #8)
Created attachment 57503 [details] acceleration disabled
I get exactly this looking battle.net with wine-staging 2.8 all defaults.
winetricks -q ie8 is a workaround for this bug. with 32bit prefix, ie8 installed via winetricks and using wine-staging 2.8 I don't see this issue anymore.
https://bugs.winehq.org/show_bug.cgi?id=42000
Michael Westwind earthworm@freegeek.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |earthworm@freegeek.org
https://bugs.winehq.org/show_bug.cgi?id=42000
Jacek Caban jacek@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek@codeweavers.com
--- Comment #11 from Jacek Caban jacek@codeweavers.com --- Please attach mshtml,ieframe,urlmon,wininet,tid,seh logs.
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #12 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to winetest from comment #10)
(In reply to winetest from comment #9)
(In reply to wow_on_wine from comment #8)
Created attachment 57503 [details] acceleration disabled
I get exactly this looking battle.net with wine-staging 2.8 all defaults.
winetricks -q ie8 is a workaround for this bug. with 32bit prefix, ie8 installed via winetricks and using wine-staging 2.8 I don't see this issue anymore.
You sure it doesn't workaround the bug simply because it resets the Windows version to XP?
https://bugs.winehq.org/show_bug.cgi?id=42000
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #13 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- I can confirm the issue. Also happening in Vista mode.
If I login in XP mode, then close the app, switch to win7 mode and try to connect again, the issue does not happen.
This means to me that the issue relates to the CEF browser used by the app interface having issue with wine in win7 mode. When in XP mode the browser does work and saves its cookies and cache. When returning to win7 mode, the browser finds the recently saved cookies and cache and it functions properly. After some time the issue is back in win7 mode. Something to do with expired cache or cookies, I guess.
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #14 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Created attachment 58788 --> https://bugs.winehq.org/attachment.cgi?id=58788 WINEDEBUG=+mshtml,+ieframe,+urlmon,+wininet,+tid,+seh terminal output
(In reply to Jacek Caban from comment #11)
Please attach mshtml,ieframe,urlmon,wininet,tid,seh logs.
https://bugs.winehq.org/show_bug.cgi?id=42000
Amosar maxi.cass11@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maxi.cass11@gmail.com
--- Comment #15 from Amosar maxi.cass11@gmail.com --- Created attachment 59278 --> https://bugs.winehq.org/attachment.cgi?id=59278 terminalOutput 2.17-staging
Problem always present on 2.17-staging
https://bugs.winehq.org/show_bug.cgi?id=42000
PeterG peter.g.anderson@live.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson@live.co.uk
--- Comment #16 from PeterG peter.g.anderson@live.co.uk --- Blizzard are completely removing support for XP and state that the Blizzard app will no longer run unless you upgrade to Win 7 +
Therefore the XP temporary workaround will possibly cease to function in October 2017.
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #17 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to PeterG from comment #16)
Blizzard are completely removing support for XP and state that the Blizzard app will no longer run unless you upgrade to Win 7 +
Therefore the XP temporary workaround will possibly cease to function in October 2017.
Since Wine 2.17 (or 2.15...2.16 I can't remember) the Blizzard app does work in win7 mode for me.
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #18 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Olivier F. R. Dierick from comment #17)
Since Wine 2.17 (or 2.15...2.16 I can't remember) the Blizzard app does work in win7 mode for me.
Ignore that, I was talking about bug 43349.
This bug is still present with Wine 2.18.
https://bugs.winehq.org/show_bug.cgi?id=42000
Sebastiaan sebastiaanlokhorst@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastiaanlokhorst@gmail.co | |m
--- Comment #19 from Sebastiaan sebastiaanlokhorst@gmail.com --- This is fixed for me in 2.18-staging
https://bugs.winehq.org/show_bug.cgi?id=42000
--- Comment #20 from PeterG peter.g.anderson@live.co.uk --- (In reply to Sebastiaan from comment #19)
This is fixed for me in 2.18-staging
Indeed it is. Suggest that this bug be marked as STAGED now.
https://bugs.winehq.org/show_bug.cgi?id=42000
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=42000
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |STAGED Ever confirmed|0 |1 Staged patchset| |https://github.com/wine-com | |pholio/wine-staging/tree/ma | |ster/patches/crypt32-ECDSA_ | |Cert_Chains Component|-unknown |crypt32
https://bugs.winehq.org/show_bug.cgi?id=42000
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aaahaaap@gmail.com
--- Comment #21 from Matteo Bruni matteo.mystral@gmail.com --- *** Bug 43901 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=42000
Zel Uneec zculek@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zculek@gmail.com
--- Comment #22 from Zel Uneec zculek@gmail.com --- This issue/bug is still present for me when using Windows 7 mode, both in 2.18-staging and 2.20-staging. Tried a fresh installs too, but the issue persists.
Is there something additional that needs to be done for CEF browser to properly work?
https://bugs.winehq.org/show_bug.cgi?id=42000
Amosar maxi.cass11@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #59278|0 |1 is obsolete| |
--- Comment #23 from Amosar maxi.cass11@gmail.com --- Created attachment 60374 --> https://bugs.winehq.org/attachment.cgi?id=60374 Terminal output with wine 3.0 and WINEDEBUG=+mshtml,+ieframe,+urlmon,+wininet,+tid,+seh
I always have this issue in wine 3.0
https://bugs.winehq.org/show_bug.cgi?id=42000
Adam Bolte abolte@systemsaviour.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abolte@systemsaviour.com
--- Comment #24 from Adam Bolte abolte@systemsaviour.com --- Confirming this is still an issue in Wine 3.2 unless the crypt32-ECDSA_Cert_Chains patch set (as well as the bcrypt-Improvements patch set dependency) from wine-staging are also applied.
Tested using my https://github.com/boltronics/wine/commits/wine-3.2-origin repository branch as the patches from staging no longer cleanly apply.
Note that these same two patches also get Origin working (hence the branch name), thus permitting a huge number of games to become available to Wine for testing once applied. I would certainly recommend some focus and priority be given to making these patches available in the main Wine master branch if they are not already.
https://bugs.winehq.org/show_bug.cgi?id=42000
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE CC| |z.figura12@gmail.com Status|STAGED |RESOLVED
--- Comment #25 from Zebediah Figura z.figura12@gmail.com --- Marking duplicate.
*** This bug has been marked as a duplicate of bug 35902 ***
https://bugs.winehq.org/show_bug.cgi?id=42000
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #26 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Duplicates
https://bugs.winehq.org/show_bug.cgi?id=42000
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katoflip@protonmail.com
--- Comment #27 from Anastasius Focht focht@gmx.net --- *** Bug 44627 has been marked as a duplicate of this bug. ***
-
wine-bugs＠winehq.org