[Bug 36101] New: Wow Hangs at login screen when coming from battle.net launcher (only with gxapi Opengl)
https://bugs.winehq.org/show_bug.cgi?id=36101
Bug ID: 36101 Summary: Wow Hangs at login screen when coming from battle.net launcher (only with gxapi Opengl) Product: Wine Version: 1.7.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: devoid42@gmail.com
When using the battle.net app launcher, starting Wow hangs on the initial "connecting" dialog. I tested this with a fresh wine-prefix, the only wow configuration change was the setting of openGL mode(the preferred wine gfx api).
This hang presented itself both via setting opengl via Config.wtf or via the commandline option -opengl via the battle.net settings for game settings and adding it as an additional commandline option.
All tests done with: wine-1.7.17 Nvidia Linux-x86_64 319.32
https://bugs.winehq.org/show_bug.cgi?id=36101
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |minor
http://bugs.winehq.org/show_bug.cgi?id=36101
Kaz hunterkaz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hunterkaz@gmail.com
--- Comment #1 from Kaz hunterkaz@gmail.com --- I am having the same issue. I can open the battle.net launcher to connect to the game or run the game client directly, with or without the -opengl flag.
My troubleshooting has consisted of:
- Fresh install of the launcher and game client in a fresh wine prefix. - Copied install of a working client from a Windows machine into a fresh wine prefix.
It doesn't matter where I open the client from, I still have the same issue. I believe its network related, but I'm not sure whats missing. The client opens, but when it attempts to connect to the world server, the conneciton dies.
Using: nvidia-340.24-3 wine-1.7.23-1 linux-3.15.8-1
https://bugs.winehq.org/show_bug.cgi?id=36101
odielag@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |odielag@gmail.com
--- Comment #2 from odielag@gmail.com --- This bug is valid for me.
OS: Opensuse 13.1 x64 wine: 1.7.25 (one click install from opensuse.org) graphics card: radeon hd7850. (Proprietary drivers installed from one click suse.org.) Wow: 5.4 retail as of September 05 2014
Before I set the gxapi opengl setting in config.wtf of wow to force opengl the game would run natively from the launcher. The fps was about 30fps on low graphics settings.
Once I set opengl... instead of after pressing Play in the launcher and getting a game client with connecting and getting connected with characters showing... it stalled at "connecting" in the game client. When I pressed some sort of cancel button the only button and field that showed in the game client was "quit."
If I run the Wow-64.exe program directly instead of using the launcher the game client comes up asking for a login/pass and the client fully works.
https://bugs.winehq.org/show_bug.cgi?id=36101
John john123@openmailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |john123@openmailbox.org
--- Comment #3 from John john123@openmailbox.org --- This bug is also valid for me as of 12 Sep 2014, and is still ongoing.
OS: Linux Mint 17 64-bit KDE Wine: 1.6.2 (and then tried 1.7.26, bug still present) Gfx: GTX 750 Ti on nvidia-331
The WoW client will not connect to Blizzard servers when launched from the Battle.Net application, but will speedily connect when launched independently of the Battle.Net application.
To troubleshoot this, I've:
1- tried running 32-bit and 64-bit versions of Wow through Battle.Net, as well as openGL arguments - to no avail. 2- tried running under Win 7, Win Vista, Win XP options within Wine config - to no avail. 2- tried running traceroutes to the relevant Blizzard servers (a list can be found here: https://us.battle.net/support/en/article/performing-a-traceroute), and there are no issues connecting to different server clusters. 3- power cycled home network, flushed DNS, and disable LM firewall, and then tried launching WoW through Battle.Net - to no avail. 4- contacted Blizzard support and removed the 'Starter Edition' from my Battle.Net account as some forums report that having the starter edition alongside a fully paid one may cause issues in some setups.
Curiously, this Bug appeared right after the latest Battle.Net update - which I cannot find release notes for - so I would be interested to know if anybody thinks that update could be triggering this Bug?
https://bugs.winehq.org/show_bug.cgi?id=36101
--- Comment #4 from John john123@openmailbox.org --- **UPDATE**
I may have stumbled upon a workaround for this issue.
As of a few minutes ago, this Bug no longer presents itself, i.e. the WoW client will connect when launched via Battle.net.
I did two things that may have worked:
1- I contacted Blizzard and removed the 'starter edition' from my Battle.Net account, and 2- changed the Windows Version to 'Windows 8' in Wine config. From that point on it worked, even when I reverted back to Windows 7 (original setting).
Not sure which, if any, of these steps helped.
I have **just** tested this in both 1.7.26 and then reverted wine back to 1.6.2 the Bug cannot be reproduced.
https://bugs.winehq.org/show_bug.cgi?id=36101
--- Comment #5 from John john123@openmailbox.org --- PS - should this be listed under or linked to the Battle.net App for future reference? Since it seems more like an issue between the interaction of WoW and Battle.net. Just a thought.
https://bugs.winehq.org/show_bug.cgi?id=36101
Jean Balbaev trojan_google@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |trojan_google@yahoo.com
--- Comment #6 from Jean Balbaev trojan_google@yahoo.com --- Can confirm this bug. Appeared after the latest Battle.net App update. Sadly, removing Starter Edition didn't make sense.
https://bugs.winehq.org/show_bug.cgi?id=36101
Andrew Mitchell ajmitch@ubuntu.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ajmitch@ubuntu.com
https://bugs.winehq.org/show_bug.cgi?id=36101
Horia fakemoth@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fakemoth@gmail.com
--- Comment #7 from Horia fakemoth@gmail.com --- Why is this bug still UNCONFIRMED when everyone confirms it?!
Well here it is again, I too confirm that I have this issue, openSUSE 13.1 x86_64, Wine 1.7.28
The only way you can launch the game is if you change something in the display tab.
https://bugs.winehq.org/show_bug.cgi?id=36101
clm@martindroessler.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |clm@martindroessler.de
--- Comment #8 from clm@martindroessler.de --- I agree with Horia. Also having this problem with wine 1.7.28 on Kubuntu.
https://bugs.winehq.org/show_bug.cgi?id=36101
--- Comment #9 from Horia fakemoth@gmail.com --- It runs only with D3D, and very low fps; for me OpenGL does not work anymore. Can you guys confirm that?
https://bugs.winehq.org/show_bug.cgi?id=36101
Jens otaku.no.anime@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |otaku.no.anime@gmail.com
--- Comment #10 from Jens otaku.no.anime@gmail.com --- The hanging only happens, if you use the battle.net Launcher and start in opengl mode. Sometimes opengl setting is not used. You may have to force it providing -opengl to the arguments available in battle.net settings.
As a workaround you can use opengl mode starting the wow64.exe directly like in the earlier days. Then there you have to input your credentials again. And then use the battle.net launcher only for updating the client. This works for me.
(wine 1.7.17)
https://bugs.winehq.org/show_bug.cgi?id=36101
Simon simon_hyll@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |simon_hyll@hotmail.com
--- Comment #11 from Simon simon_hyll@hotmail.com --- Everyone who complains about performance or OpenGL mode, look at the following:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=30545&...
Follow the installation instructions there and your game should work a million times better.
Make sure that you set processorAffinityMask correctly, 255 for 8 cores, 15 for quad core, 7 for tri, 3 for dual.
Also make sure to use the start script.
https://bugs.winehq.org/show_bug.cgi?id=36101
--- Comment #12 from Horia fakemoth@gmail.com --- Tried it right now. This doesn't do anything - the behaviour is still the same. The game just doesn't work anymore with OpenGL.
And this doesn't seem to me as a " Importance: P2 minor" bug. I just quitted playing WoW because of this. Directly or through the launcher with -opengl or without doesn't make any difference. Nor the Wine version.
On openSUSE 13.1 and 13.2, nVidia or AMD proprietary drivers no one plays this anymore. Not on a big resolution and decent conditions anyway.
https://bugs.winehq.org/show_bug.cgi?id=36101
--- Comment #13 from Horia fakemoth@gmail.com --- And why is it still UNCONFIRMED? Do you need Thraal to comment on this one to believe us?
lol
https://bugs.winehq.org/show_bug.cgi?id=36101
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1
--- Comment #14 from Austin English austinenglish@gmail.com --- Confirming.
https://bugs.winehq.org/show_bug.cgi?id=36101
Catryna M prosepenia@openmailbox.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |prosepenia@openmailbox.org
--- Comment #15 from Catryna M prosepenia@openmailbox.org --- (In reply to Simon from comment #11)
Everyone who complains about performance or OpenGL mode, look at the following:
https://appdb.winehq.org/objectManager. php?sClass=version&iId=30545&iTestingId=87166
Follow the installation instructions there and your game should work a million times better.
Make sure that you set processorAffinityMask correctly, 255 for 8 cores, 15 for quad core, 7 for tri, 3 for dual.
Also make sure to use the start script.
The problem with using a startup script and avoiding the Battlenet startup app is that you won't get any updates.
https://bugs.winehq.org/show_bug.cgi?id=36101
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 --- I run WoW using OpenGL and the workaround for this problem is simple. When the screen shows the 'Connecting' dialog, press [RETURN] twice and it should get to the character screen.
https://bugs.winehq.org/show_bug.cgi?id=36101
ste ste.elendil@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ste.elendil@gmail.com
--- Comment #17 from ste ste.elendil@gmail.com --- If I have correctly understood the problem reported by devoid42, I suggest you read this thread:
http://us.battle.net/wow/en/forum/topic/20742995286?page=1
in particular the solution proposed by Store on page 11.
On page 1, the moderator writes:
"This seems to be the issue affecting the majority of users that have posted reports. We have identified that the cause of this issue is in secur32.dll.so, a wine library that implements encryption on the network stack for Windows applications. secure32.dll.so directs gnutls (the Linux library which actually implements the behavior) to perform an SSLv3 handshake with the server by default. This was acceptable behavior in prior versions of WoW but 6.2.4 removed tolerance for this behavior, resulting in the client being abruptly dropped by the server, which now requires TLS (a newer encryption paradigm) only."
I downloaded the source of wine-1.9.6 and I have patched the file
schannel_gnutls.c
as proposed by Store
I made a bakup of /usr/local/lib/wine/secur32.dll.so
then: ./configure make sudo make install
The problem for me is solved in this way. Perhaps the Store code could be evaluated by Wine developers.
greetings ste
https://bugs.winehq.org/show_bug.cgi?id=36101
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #18 from winetest@luukku.com --- (In reply to ste from comment #17)
If I have correctly understood the problem reported by devoid42, I suggest you read this thread:
There is 26 pages of discussion. But the page one has been updated and it indicates that this issue has been fixed in recent wine versions.
So is this problem solved? The original bug report was made back 2014.
https://bugs.winehq.org/show_bug.cgi?id=36101
--- Comment #19 from PeterG peter.g.anderson@live.co.uk --- (In reply to winetest from comment #18)
(In reply to ste from comment #17)
If I have correctly understood the problem reported by devoid42, I suggest you read this thread:
There is 26 pages of discussion. But the page one has been updated and it indicates that this issue has been fixed in recent wine versions.
So is this problem solved? The original bug report was made back 2014.
Yes, this should be marked as solved. It hasn't been a problem for a while and it is worth noting that WoW no longer supports OpenGL mode anyway.
https://bugs.winehq.org/show_bug.cgi?id=36101
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dimesio@earthlink.net
https://bugs.winehq.org/show_bug.cgi?id=36101
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |secur32 Status|NEW |RESOLVED Resolution|--- |FIXED Fixed by SHA1| |f198b5a45a52aa0bcf79f1909c8 | |f6dc4e56c4143
--- Comment #20 from Bruno Jesus 00cpxxx@gmail.com --- Fixed by http://source.winehq.org/git/wine.git/commitdiff/f198b5a45a52aa0bcf79f1909c8...
https://bugs.winehq.org/show_bug.cgi?id=36101
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #21 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.9.23.
https://bugs.winehq.org/show_bug.cgi?id=36101
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |1.8.x
https://bugs.winehq.org/show_bug.cgi?id=36101
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|1.8.x |---
--- Comment #22 from Michael Stefaniuc mstefani@redhat.com --- Removing 1.8.x milestone from bugs included in 1.8.6.
-
wine-bugs＠winehq.org