https://bugs.winehq.org/show_bug.cgi?id=51567
Bug ID: 51567 Summary: Battle.net app takes a long time to start Product: Wine Version: 6.12 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: pavel1r@gmail.com Distribution: ---
I'm using Fedora 33 (Mate) with wine installed from winehq fedora repo. Starting from wine 6.12, Battle.net application takes a lot of time to start (more than 5 minutes). When started, it does not render content. Sometimes, after several attepmts to reload, the content is rendered. The issue persists in 6.13 and 6.14 too. I tried to install in fresh prefix, but with 6.14, after more than 10 minutes in state "Updating Battle.net update Agent", I gave up. With 6.11, installation completed in about 1 minute. Attempt to run from fresh prefix with 6.14 exhibited the same behavior.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #1 from Pavel pavel1r@gmail.com --- Tried to install in a fresh prefix with newly released wine 6.15. Installation displays a language selection dialog, only radio boxes are displayed, without any text. On console, I see lots of messages 0100:fixme:dc:DeleteDC not deleting busy DC 0241FEB1 refcount 2 0100:fixme:dc:DeleteDC not deleting busy DC 0241FEB2 refcount 2
After that, several messages 0100:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash 0100:err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
And finally a message Assertion failed: entry_obj( entry )->selcount, file dlls/gdi32/gdiobj.c, line 512 And application crashes
https://bugs.winehq.org/show_bug.cgi?id=51567
jokeyrhyme@jokeyrhy.me changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jokeyrhyme@jokeyrhy.me
--- Comment #2 from jokeyrhyme@jokeyrhy.me --- I'm having similar issues
wine (but stable and staging) 6.13, 6.14, 6.15 starts Battle.net but it launches very slowly, and while eventually the login screen appears (after several minutes), I don't seem to be able to get any further than that (maybe it would work after 30 minutes, but I have not waited this long yet)
wine-staging still takes several minutes for things to happen, but seems slightly better than wine stable
Logged output includes:
[0829/064604.708:ERROR:dxva_video_decode_accelerator_win.cc(1320)] DXVAVDA fatal error: Could not load msmpeg2vdec.dll: Module not found. (0x7E) 0124:fixme:shcore:SetCurrentProcessExplicitAppUserModelID L"BlizzardEntertainment.Battlenet.beta": stub 0124:fixme:shell:CustomDestinationList_SetAppID 0x12254ba0 (L"BlizzardEntertainment.Battlenet.beta"): stub 0124:fixme:shell:CustomDestinationList_BeginList 0x12254ba0 (0x70e4cc {92ca9dcd-5622-4bba-a805-5e9f541bd8c9} 0x70e4d0): stub 0124:fixme:msg:ChangeWindowMessageFilterEx 000100B0 c04c 1 00000000 02cc:fixme:secur32:get_cipher_algid unknown algorithm 23 02cc:fixme:secur32:get_mac_algid unknown algorithm 200, cipher 23 0124:fixme:winsock:addrinfo_err_from_unix unhandled error 0 01b4:fixme:winsock:addrinfo_err_from_unix unhandled error 0 018c:fixme:netapi32:NetGetJoinInformation Semi-stub (null) 0E7BFB7C 0E7BFB78 023c:fixme:sync:NtSetInformationJobObject stub: 0x5ac 4 0x1a69f91c 4 0124:fixme:winsock:addrinfo_err_from_unix unhandled error 0 01b4:fixme:winsock:addrinfo_err_from_unix unhandled error 0 0304:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0304:fixme:cryptasn:CRYPT_GetBuiltinDecoder Unsupported decoder for lpszStructType 1.3.6.1.4.1.311.2.1.4 0304:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0070EE9C 1 C) semi-stub 0304:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0070ED1C 1 C) semi-stub 0304:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0070F0B4 1 C) semi-stub 0304:fixme:heap:RtlSetHeapInformation 00000000 1 00000000 0 stub 0304:fixme:msvcp:_Locinfo__Locinfo_ctor_cat_cstr (0070ECE4 1 C) semi-stub 0320:fixme:winsock:WSALookupServiceBeginW (09C3F604 0x00000ff0 09C3F640) Stub! [0829/064643.717:ERROR:network_change_notifier_win.cc(142)] WSALookupServiceBegin failed with: 0 0320:fixme:iphlpapi:NotifyAddrChange (Handle 0x9c3f780, overlapped 0x7da7a78): stub 0320:fixme:wlanapi:WlanEnumInterfaces (00000001, 00000000, 09C3F39C) semi-stub 0124:fixme:winsock:addrinfo_err_from_unix unhandled error 0 01b4:fixme:winsock:addrinfo_err_from_unix unhandled error 0 0124:fixme:winsock:addrinfo_err_from_unix unhandled error 0 01b4:fixme:winsock:addrinfo_err_from_unix unhandled error 0 01b4:fixme:winsock:addrinfo_err_from_unix unhandled error 0 00fc:fixme:win:FlashWindowEx 0032BC24 - semi-stub 0368:fixme:thread:QueryThreadCycleTime (FFFFFFFE,0032EE00): stub! 0350:fixme:file:ReplaceFileW Ignoring flags 2 0354:fixme:file:ReplaceFileW Ignoring flags 2 0368:fixme:dwrite:dwritefontface5_HasVariations 00C5C490: stub 034c:fixme:file:ReplaceFileW Ignoring flags 2 00fc:fixme:win:FlashWindowEx 0032B87C - semi-stub 0344:fixme:file:ReplaceFileW Ignoring flags 2 0354:fixme:file:ReplaceFileW Ignoring flags 2 0344:fixme:file:ReplaceFileW Ignoring flags 2 00fc:fixme:win:GetPointerDevices (0032BECC 00000000): partial stub 00fc:fixme:system:GetDisplayConfigBufferSizes (0x2 0032BECC 0032BEC8): semi-stub 00fc:fixme:system:QueryDisplayConfig (00000002 0032BECC 13DD1168 0032BEC8 13DD2F18 00000000): semi-stub 00fc:fixme:system:DisplayConfigGetDeviceInfo Unimplemented packet type: 11 00fc:fixme:win:GetPointerDevices (0032C71C 00000000): partial stub 00fc:fixme:system:GetDisplayConfigBufferSizes (0x2 0032C71C 0032C718): semi-stub 00fc:fixme:system:QueryDisplayConfig (00000002 0032C71C 13DD1168 0032C718 13D31CB8 00000000): semi-stub 00fc:fixme:system:DisplayConfigGetDeviceInfo Unimplemented packet type: 11 00fc:fixme:shell:CustomDestinationList_SetAppID 0x11bce570 (L"BlizzardEntertainment.Battlenet.beta"): stub 00fc:fixme:shell:CustomDestinationList_BeginList 0x11bce570 (0x32c320 {92ca9dcd-5622-4bba-a805-5e9f541bd8c9} 0x32c324): stub 00fc:fixme:win:FlashWindowEx 003296EC - semi-stub 00fc:fixme:win:FlashWindowEx 003296EC - semi-stub 00fc:fixme:win:GetPointerDevices (0032C71C 00000000): partial stub 00fc:fixme:system:GetDisplayConfigBufferSizes (0x2 0032C71C 0032C718): semi-stub 00fc:fixme:system:QueryDisplayConfig (00000002 0032C71C 188D8960 0032C718 13D31CB8 00000000): semi-stub 00fc:fixme:system:DisplayConfigGetDeviceInfo Unimplemented packet type: 11
I can confirm that wine 6.10 does not have this problem, I have not tested wine 6.11
https://bugs.winehq.org/show_bug.cgi?id=51567
bebing@email.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bebing@email.com
--- Comment #3 from bebing@email.com --- Just wanted to add that I am seeing this too. I went from 6.0 staging to 6.15 staging and started seeing it. 6.16 and 6.17 still have it. Luckily I am able to launch the games, and they are okay once started, it just takes a lot of patience to get them going. Using LFS.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #4 from bebing@email.com --- Also, can I stop winehq from displaying my email address? I checked out everything I could and could not find out how.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #5 from bebing@email.com --- test
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #6 from bebing@email.com --- Please change my display name, I sent a message to the administrator. Delete this account please if that's an easy way to do it. Thank you.
https://bugs.winehq.org/show_bug.cgi?id=51567
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #7 from Zebediah Figura z.figura12@gmail.com --- For what it's worth, your email address is only displayed for logged-in users.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #8 from bebing@email.com --- For you it displays a username instead of an email address.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #9 from bebing@email.com --- Oh, I guess you entered your full name. Nevermind.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #10 from bebing@email.com --- I'll try adding a full name.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #11 from CJ Bilco bebing@email.com --- Hey hey, success! Thank you! Sorry for the off-topic messages.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #12 from CJ Bilco bebing@email.com --- Still happening with 6.19-staging...
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #13 from CJ Bilco bebing@email.com --- Happens in wine-staging 6.20 as well.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #14 from Pavel pavel1r@gmail.com --- Updated fedora to 35 which comes with wine 6.21. Still same issue.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #15 from jokeyrhyme@jokeyrhy.me --- I think one of us is going to have to use compile `wine` a bunch of times and narrow down exactly which commit between 6.11 and 6.12 broke things
Should be possible to use `git bisect` to do this a minimum number of times
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #16 from Pavel pavel1r@gmail.com --- I'm trying to do so, but don't understand how to apply staging patches, as neither 6.11 nor 6.12 patches do not apply to commits in between. If someone has experience with this, some guidance will be helpful
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #17 from CJ Bilco bebing@email.com --- I compile from the source, so I don't know if that would make doing this easier or harder, but I am willing to try.
Another idea is to see if we have a common setup. Sometimes I have a fear it has to do with 32 bit libvulkan. I am able to compile 64 bit libvulkan, but not 32 bit libvulkan, so I take the 32 bit libvulkan from .deb files. But the only version I can use is a bit older. I am using libvulkan.so.1.0.39.
Also, I am have nvidia.
Thirdly, I get:
0150:err:kerberos:kerberos_LsaApInitializePackage no Kerberos support, expect problems
But I think I get that for other apps that work okay.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #18 from CJ Bilco bebing@email.com --- Oh it looks like you all are compiling from source. I thought everyone else was using package management. So nevermind my comment about that.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #19 from Pavel pavel1r@gmail.com --- (In reply to CJ Bilco from comment #18)
Oh it looks like you all are compiling from source. I thought everyone else was using package management. So nevermind my comment about that.
Normally, I'm using packaged version of wine. But to make some progress with this issue, I'm trying to build packages from source, to see which commit actually broke wine. I'm using Fedora (initially it was F33, now F35), with NVidia card. Also, using dxvk for DX11 emulation. My feeling is that issue somehow related to networking stuff and not graphics, I believe I see some http error messages when running with 6.12. But again, not sure if it is related.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #20 from CJ Bilco bebing@email.com --- I agree about the network being the likely culprit, good observation. That makes sense and fits the evidence.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #21 from CJ Bilco bebing@email.com --- https://www.winehq.org/announce/6.12
cutting and pasting seemingly relevant tidbits:
- More work towards WinSock PE conversion. - Beginnings of the NSI (Network Store Interface) implementation.
8606 No network-support in the game Joint Operations Typhoon Rising
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #22 from Pavel pavel1r@gmail.com --- (In reply to CJ Bilco from comment #21)
https://www.winehq.org/announce/6.12
cutting and pasting seemingly relevant tidbits:
- More work towards WinSock PE conversion.
- Beginnings of the NSI (Network Store Interface) implementation.
8606 No network-support in the game Joint Operations Typhoon Rising
Interesting. Actually there is one more complication. 6.12 had a regression affecting Battle.net. It was supposedly fixed in 6.13.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #23 from CJ Bilco bebing@email.com --- Also I noticed around the same time, that when I launch WoW directly the login sequence takes much longer, but is still solid. From like 3 seconds to like 15 to 30 seconds.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #24 from CJ Bilco bebing@email.com --- https://www.winehq.org/announce/6.13
51331 Battle.net client unusable, reports "The Battle.net Update Agent went to sleep. Attempting to wake it up..."
Is that it? Sorry I'm new to this type of sleuthing.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #25 from Pavel pavel1r@gmail.com --- (In reply to CJ Bilco from comment #24)
https://www.winehq.org/announce/6.13
51331 Battle.net client unusable, reports "The Battle.net Update Agent went to sleep. Attempting to wake it up..."
Is that it? Sorry I'm new to this type of sleuthing.
I think that's the bug. I also noticed slower login in WoW with latest wine versions.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #26 from CJ Bilco bebing@email.com --- Okay, so this looks promising as I think I would be able to add or subtract patches if I have this data. I will look at it further. Unfortunately I'm getting a bit confused.
Would I start with 6.11 and add something or start with 6.13 and remove something or something else or we might have to do multiple
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #27 from Pavel pavel1r@gmail.com --- (In reply to CJ Bilco from comment #26)
Okay, so this looks promising as I think I would be able to add or subtract patches if I have this data. I will look at it further. Unfortunately I'm getting a bit confused.
Would I start with 6.11 and add something or start with 6.13 and remove something or something else or we might have to do multiple
Currently, I got stuck with compilation because it requires staging patches which I only managed to apply to released versions. Didn't have time to look at them more closely.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #28 from CJ Bilco bebing@email.com --- Okay, so would I be able to do this compiling and testing on stable instead of staging? It sounds like the issue happens in stable, but the whole reason I went to staging is some things wouldn't work without it.
Well sometimes it's better just to dive in and try some stuff. So currently I am using wine-staging 6.19 because it seems to work better than 6.20 and on. So I think my first try will be start with wine-staging 6.19 as a base and see if I can back out a change or add a change that was removed from there.
Oh well, unfortunately I cannot do that today, but will start tinkering when I get a chance.
Any help or input is very much welcomed, I will just kinda be bumbling through it.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #29 from Pavel pavel1r@gmail.com --- I think staging required for WoW and other games to run, but Battle net should be working with stable. So, it should be possible to check it with stable version. What I'm usually doing, is to try and install Battle.Net in new prefix. The problem can be seen during installation.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #30 from Sveinar Søpler cybermax@dexter.no --- There was some bugs around 6.12'ish ref: https://bugs.winehq.org/show_bug.cgi?id=51319
This is closed as fixed with: https://source.winehq.org/git/wine.git/commitdiff/361435f6095f8c759979600b06...
Not 100% sure it is related tho.
I know that the Battle.net client does not really work if you have enabled "browser hardware acceleration" (default enabled) when using regular wine-staging. This can be disabled in the settings.
I tried with Ubuntu distro provided wine-staging-6.22 and after disabling the above, i did not seem to have any huge issues connecting, but going back and forth a bit i experienced a couple of hangs of "Battle.net.exe --updatepid=xxx" pinning one core to 100% leading me having to kill wineserver.
Normally a fresh prefix with battle.net seems to take around 5 seconds to start and show my games list and schtuff.
Probably not easy to pinpoint a problem if it works for some :)
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #31 from CJ Bilco bebing@email.com --- Sounds good. I will definitely remember to do a fresh prefix and a fresh install of battle-net. That has got me over humps in the past. I might give a first try with staging just because I still have the source folder I installed from. Even if I have manually do what the patches automatically would do. But if I am unable to easily do the adding or removing because of that I will quickly move to stable.
Yes! It doesn't seem like many people are having this issue! We would be getting more eyes on it if there were more people suffering with it.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #32 from Pavel pavel1r@gmail.com --- Yes, it looks like a different issue. For me, Battle net starts in few seconds in 6.11 and several minutes (if at all) in any later version.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #33 from CJ Bilco bebing@email.com --- Created attachment 71129 --> https://bugs.winehq.org/attachment.cgi?id=71129 dlls/ws2_32/tests/afd.c
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #34 from CJ Bilco bebing@email.com --- I took a stab I will detail below, but it didn't help.
1. wine-staging 6.19 as a starting point 2. https://bugs.winehq.org/show_bug.cgi?id=51331 3. https://source.winehq.org/git/wine.git/commitdiff/53e69130cce85bf59830c1f6f3... 4. my code matched the green + 5. so i commented those out and added the red - code 6. was tricky, many blocks of similar code so I was real careful 7. fresh build, built ok, installed 8. fresh prefix, fresh battle.net install 9. seemed to be going very slow 10. in a rush, so i aborted and cleaned process 11. tried with my existing prefix and still showed very slow behavior
It's possible I made a mistake but I don't think so Still not a waste of time, good practice and maybe will narrow things down
I went to attach the files I changed just in case someone wanted to look at them and it cancelled my whole post and I had to redo!
So am just going to post this and then add the rest of the files.
Happy Thanksgiving! Will pick up later...
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #35 from CJ Bilco bebing@email.com --- Created attachment 71130 --> https://bugs.winehq.org/attachment.cgi?id=71130 dlls/ws2_32/tests/sock.c
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #36 from CJ Bilco bebing@email.com --- Created attachment 71131 --> https://bugs.winehq.org/attachment.cgi?id=71131 server/sock.c
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #37 from CJ Bilco bebing@email.com --- oh yeah, also did winetricks dxvk
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #38 from CJ Bilco bebing@email.com --- If anyone wants to look at the changes(probably not), you can search for "bbb" in the files I upladed, I added "/*bbb*/" where I made the changes.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #39 from CJ Bilco bebing@email.com --- [1126/140740.373:ERROR:dxva_video_decode_accelerator_win.cc(1320)] DXVAVDA fatal error: Could not load msmpeg2vdec.dll: Module not found. (0x7E)
Maybe this has something to do with it? Disabling hardware acceleration doesn't help in my case, but maybe it still has something to do with it? I say this because when it was working okay, when the output belches out the vulkan info is when it would come up and start working normally. Now at that exact point I get the error message above. Just a desperate wild stab.
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #40 from CJ Bilco bebing@email.com --- Crap, I might have forgot to set it to Windows 10 when I tried that special build, oh well lol
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #41 from CJ Bilco bebing@email.com --- There is also another wine message board that might be helpful:
https://forum.winehq.org/viewforum.php?f=8
https://bugs.winehq.org/show_bug.cgi?id=51567
--- Comment #42 from CJ Bilco bebing@email.com --- Hopefully everyone moved on from this, but I was suffering for awhile because the games were working fine, it was just battle.net that was really slow. Well, I finally updated to 7.14 and battle.net is no longer slow. Now hopefully D2R will work without too much hassle.
https://bugs.winehq.org/show_bug.cgi?id=51567
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |performance
--- Comment #43 from Ken Sharp imwellcushtymelike@gmail.com --- Pavel, can you please confirm that the issue is fixed?
-
WineHQ Bugzilla