[Bug 37594] New: World of Warcraft in-game browser does not work
https://bugs.winehq.org/show_bug.cgi?id=37594 Bug ID: 37594 Summary: World of Warcraft in-game browser does not work Product: Wine Version: 1.7.31 Hardware: x86 URL: https://eu.battle.net/en/ OS: Linux Status: NEW Keywords: download Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: adys.wh(a)gmail.com Distribution: ArchLinux Created attachment 50030 --> https://bugs.winehq.org/attachment.cgi?id=50030 Screenshot of browser The new in-game browser from 5.x has never worked. Screenshot attached. No relevant output. Can easily be tested with a trial account going in game menu -> Help -> Knowledge Base. -- 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=37594 Ker noa <blue-t(a)web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t(a)web.de --- Comment #1 from Ker noa <blue-t(a)web.de> --- still happens with 1.7.31 and WoW 6.0.3.19116 -- 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=37594 --- Comment #2 from Ker noa <blue-t(a)web.de> --- It seems connected to fixme:advapi:CreateRestrictedToken (0x2108, 0x0, 2, 0x3e6c10f0, 19, 0x1387b3e4, 5, 0x23e470, 0x23e330): stub fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x23e288,0,(nil),0x12d3b2e0,0x23e270,0x23e258) stub! -- 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=37594 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |focht(a)gmx.net --- Comment #3 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, --- quote --- Screenshot of browser --- quote --- An example how it's supposed to look like on Windows for comparison purpose is always useful. --- quote --- It seems connected to fixme:advapi:CreateRestrictedToken (0x2108, 0x0, 2, 0x3e6c10f0, 19, 0x1387b3e4, 5, 0x23e470, 0x23e330): stub fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x23e288,0,(nil),0x12d3b2e0,0x23e270,0x23e258) stub! --- quote --- I doubt that. The problem is more likely related to builtin FrameXML/LUA scripting. http://wowprogramming.com/utils/xmlbrowser/live/FrameXML/HelpFrame.lua http://wowprogramming.com/utils/xmlbrowser/live/FrameXML/HelpFrame.xml I don't feel the urge to dig deeper here. It looks rather boring. Some WoW addon developer might be of help (enable debugging/logging/diagnosis of FrameXML/LUA). 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=37594 --- Comment #4 from Jerome Leclanche <adys.wh(a)gmail.com> --- The Browser frame element is probably what doesn't work. A simple addon creating a Browser frame and loading a page could likely reproduce it. http://wowprogramming.com/docs/widgets/Browser -- 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=37594 --- Comment #5 from Jerome Leclanche <adys.wh(a)gmail.com> --- (In reply to Anastasius Focht from comment #3) Note that the Browser element is built in WoW's C code and is merely exposed in Lua. -- 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=37594 Michael Koch <m.koch(a)emkay443.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |m.koch(a)emkay443.de -- 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=37594 --- Comment #6 from Michael Koch <m.koch(a)emkay443.de> --- Wine 1.7.35, WoW 6.1 and still not working. -- 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=37594 John Porterfield <ycarus(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ycarus(a)gmail.com --- Comment #7 from John Porterfield <ycarus(a)gmail.com> --- Affects twitter login, clicking "Sign In" under the twitter login button results in a blank panel. -- 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=37594 Tobias Mädel <t.maedel(a)alfeld.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |t.maedel(a)alfeld.de -- 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=37594 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jacek(a)codeweavers.com --- Comment #8 from Jerome Leclanche <adys.wh(a)gmail.com> --- I think it's the same bug that affects the Heroes of the Storm in-game shop, which errors with "SSL connection error". CCing jacek. -- 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=37594 --- Comment #9 from Jerome Leclanche <adys.wh(a)gmail.com> --- I'm making that leap because the in-game shop in WoW doesn't work either. -- 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=37594 AsciiWolf <mail(a)asciiwolf.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mail(a)asciiwolf.com --- Comment #10 from AsciiWolf <mail(a)asciiwolf.com> --- Any news? -- 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=37594 winetest(a)luukku.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest(a)luukku.com --- Comment #11 from winetest(a)luukku.com --- Still valid wow 7.1 wine rc2.0.rc2. -- 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=37594 Andrew Wesie <awesie(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |awesie(a)gmail.com --- Comment #12 from Andrew Wesie <awesie(a)gmail.com> --- On Starcraft 1.18, the missing BuildSecurityDescriptorW implementation causes Battle.net features to be disabled. This is likely the same bug because the game lobby is implemented using an in-game browser. A quick patch to force BuildSecurityDescriptorW to return any valid security descriptor fixed the issue. I don't have a real patch right now though. -- 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=37594 Adrian Petrescu <apetresc(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |apetresc(a)gmail.com -- 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=37594 --- Comment #13 from Adrian Petrescu <apetresc(a)gmail.com> --- (In reply to Andrew Wesie from comment #12)
On Starcraft 1.18, the missing BuildSecurityDescriptorW implementation causes Battle.net features to be disabled. This is likely the same bug because the game lobby is implemented using an in-game browser.
A quick patch to force BuildSecurityDescriptorW to return any valid security descriptor fixed the issue. I don't have a real patch right now though.
Has anyone checked if Andrew's BuildSecurityDescriptorW stub also makes the WoW in-game browser work? -- 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=37594 --- Comment #14 from Andrew Wesie <awesie(a)gmail.com> --- Created attachment 58063 --> https://bugs.winehq.org/attachment.cgi?id=58063 Draft implementation of BuildSecurityDescriptorW I wrote an implementation for BuildSecurityDescriptorW that is hopefully correct. It at least fixes the StarCraft issues. It would be good to know if this fixes the in-game in WoW. -- 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=37594 Michal Hlavinka <mhlavink(a)redhat.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mhlavink(a)redhat.com -- 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=37594 --- Comment #15 from winetest(a)luukku.com --- (In reply to Andrew Wesie from comment #14)
Created attachment 58063 [details] Draft implementation of BuildSecurityDescriptorW
I wrote an implementation for BuildSecurityDescriptorW that is hopefully correct. It at least fixes the StarCraft issues. It would be good to know if this fixes the in-game in WoW.
Maybe bug 38265 is a dupe? I was about to try the patch but for me WOW is totally broken now. Tried fresh wineprefix both 32 and 64 bit prefix (free trial). Also battle.net seems to be broken too, but it works with wine-staging. -- 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=37594 --- Comment #16 from Andrew Wesie <awesie(a)gmail.com> --- Wine-Staging 2.8 has the BuildSecurityDescriptorW patch. Somebody who plays WoW should test if the latest wine-staging fixes this bug. -- 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=37594 PeterG <peter.g.anderson(a)live.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |peter.g.anderson(a)live.co.uk --- Comment #17 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to Andrew Wesie from comment #16)
Wine-Staging 2.8 has the BuildSecurityDescriptorW patch. Somebody who plays WoW should test if the latest wine-staging fixes this bug.
Tested and working well with wine-staging 2.8. Arch Linux 64-bit. No DLL overrides. Wine_Gecko installed. -- 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=37594 --- Comment #18 from winetest(a)luukku.com --- (In reply to PeterG from comment #17)
(In reply to Andrew Wesie from comment #16)
Wine-Staging 2.8 has the BuildSecurityDescriptorW patch. Somebody who plays WoW should test if the latest wine-staging fixes this bug.
Tested and working well with wine-staging 2.8. Arch Linux 64-bit. No DLL overrides. Wine_Gecko installed.
Can you tell if bug 38265 works now with wine-staging? -- 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=37594 --- Comment #19 from PeterG <peter.g.anderson(a)live.co.uk> --- (In reply to winetest from comment #18)
(In reply to PeterG from comment #17)
(In reply to Andrew Wesie from comment #16)
Wine-Staging 2.8 has the BuildSecurityDescriptorW patch. Somebody who plays WoW should test if the latest wine-staging fixes this bug.
Tested and working well with wine-staging 2.8. Arch Linux 64-bit. No DLL overrides. Wine_Gecko installed.
Can you tell if bug 38265 works now with wine-staging?
I can't tell for sure at the moment as I haven't had cause to raise a ticket recently. I will raise one and report back as soon as I get a response, but that could take a while. -- 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=37594 --- Comment #20 from PeterG <peter.g.anderson(a)live.co.uk> --- The in-game ticketing system now opens the battle.net login page correctly. I pasted the following update on the bug 38265 thread: "Tested with wine-staging 2.8, 64-bit WINEPREFIX. Browser functions including game-ticketing are now working correctly in-game." Suggest both 37594 and 38265 should be marked as STAGED. -- 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=37594 --- Comment #21 from winetest(a)luukku.com --- (In reply to Andrew Wesie from comment #16)
Wine-Staging 2.8 has the BuildSecurityDescriptorW patch. Somebody who plays WoW should test if the latest wine-staging fixes this bug.
(In reply to PeterG from comment #20)
The in-game ticketing system now opens the battle.net login page correctly. I pasted the following update on the bug 38265 thread:
"Tested with wine-staging 2.8, 64-bit WINEPREFIX. Browser functions including game-ticketing are now working correctly in-game."
Suggest both bug 37594 and bug 38265 should be marked as STAGED.
Looks promising to me. -- 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=37594 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |STAGED Summary|World of Warcraft in-game |World of Warcraft in-game |browser does not work |browser does not work | |(needs | |advapi32.BuildSecurityDescr | |iptorW() implementation) Component|-unknown |advapi32 CC| |z.figura12(a)gmail.com Staged patchset| |https://github.com/wine-sta | |ging/wine-staging/tree/mast | |er/patches/advapi32-BuildSe | |curityDescriptor --- Comment #22 from Zebediah Figura <z.figura12(a)gmail.com> --- Marking STAGED. -- 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=37594 Zebediah Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hark110(a)163.com --- Comment #23 from Zebediah Figura <z.figura12(a)gmail.com> --- *** Bug 38265 has been marked as a duplicate of this bug. *** -- 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=37594 Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |leslie_alistair(a)hotmail.com Resolution|--- |FIXED Fixed by SHA1| |b58577aa5491747cf8bc36a60fb | |71bcf82f0553f Status|STAGED |RESOLVED --- Comment #24 from Alistair Leslie-Hughes <leslie_alistair(a)hotmail.com> --- Fixed by https://source.winehq.org/git/wine.git/?a=commit;h=b58577aa5491747cf8bc36a60... -- 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=37594 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #25 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.7. -- 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=37594 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |3.0.x -- 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=37594 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.0.x |--- --- Comment #26 from Michael Stefaniuc <mstefani(a)winehq.org> --- Removing the 3.0.x milestone from bugs included in 3.0.2. -- 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 (1)
-
wine-bugs＠winehq.org