https://bugs.winehq.org/show_bug.cgi?id=43901
Bug ID: 43901 Summary: battle.net login screen broken UI elements Product: Wine Version: 2.18 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: aaahaaap@gmail.com Distribution: ---
Created attachment 59527 --> https://bugs.winehq.org/attachment.cgi?id=59527 screenshot battle.net login screen with broken UI elements
When starting battle.net after a clean install on wine-staging 2.18 with wine configured to Windows 7 the login screen shows the regular username and password fields but these don't work (i.e. putting you username and password in them and submitting results in a message that no username or password was entered) and additional unstyled fields and buttons are shown below the regular username and password fields. These unstyled fields do work. See attached screenshot of the login screen.
Steps to reproduce: - Create a new 32 bits wine prefix - Download battle.net installer (https://www.battle.net/download/getInstallerForGame?os=win&locale=enUS&a... from https://eu.battle.net/account/download/index.xml?show=bnetapp#bnetapp) and install it - When the install is finished the login window is shown with the above mentioned issues
This doesn't happen when setting Wine to Windows XP. But since Blizzard has stopped supporting Windows XP (and other Windows versions up/until 2008R2) and their games don't even run on it anymore one has to switch to Windows 7 or newer.
https://bugs.winehq.org/show_bug.cgi?id=43901
PeterG peter.g.anderson@live.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson@live.co.uk
--- Comment #1 from PeterG peter.g.anderson@live.co.uk --- The status of this bug should be changed to STAGED. This bug is fixed in wine-staging 2.18.
https://bugs.winehq.org/show_bug.cgi?id=43901
--- Comment #2 from aaahaaap@gmail.com --- (In reply to PeterG from comment #1)
The status of this bug should be changed to STAGED. This bug is fixed in wine-staging 2.18.
I experienced this bug with wine staging 2.18, so unless there's something one needs to do to make it work it's not actually fixed in wine staging 2.18.
https://bugs.winehq.org/show_bug.cgi?id=43901
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #3 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Possible duplicate of bug 43349.
The workaround that works for me is to open the battle.net login window once in XP mode before switching to win7 mode and login.
No need to login in XP mode, just opening the login window is enough.
You can check how I do it in this video: https://www.youtube.com/watch?v=oGigh0UGpn0
I think the issue is with CEF not working in win7 mode and not saving a cookie. It does save the cookie in XP mode though, and its expiration time is a few hours so it's still valid when restarting in win7 mode.
https://bugs.winehq.org/show_bug.cgi?id=43901
tokktokk fdsfgs@krutt.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fdsfgs@krutt.org
https://bugs.winehq.org/show_bug.cgi?id=43901
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Olivier F. R. Dierick from comment #3)
I think the issue is with CEF not working in win7 mode and not saving a cookie. It does save the cookie in XP mode though, and its expiration time is a few hours so it's still valid when restarting in win7 mode.
I think this was pretty much spot on. Also fixed by the same staging patchset as bug 42000.
*** This bug has been marked as a duplicate of bug 42000 ***
https://bugs.winehq.org/show_bug.cgi?id=43901
Zel Uneec zculek@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zculek@gmail.com
--- Comment #5 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=43901
André H. nerv@dawncrow.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv@dawncrow.de Status|RESOLVED |CLOSED
--- Comment #6 from André H. nerv@dawncrow.de --- closing dup