[Bug 35582] New: Stealth WoW update makes 64-bit client crash 5-10 seconds after logging in
https://bugs.winehq.org/show_bug.cgi?id=35582
Bug ID: 35582 Summary: Stealth WoW update makes 64-bit client crash 5-10 seconds after logging in Product: Wine Version: 1.7.12 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: adys.wh@gmail.com Classification: Unclassified
No relevant debug output before the crash.
fixme:seh:RtlAddFunctionTable 0x12dbe000 157 12db0000: stub fixme:seh:RtlDeleteFunctionTable 0x6000: stub fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x237630,L"kernel32<elf>"), for debug_info(abbrev:0x1502df10,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x237630,L"kernel32<elf>"), for debug_info(abbrev:0x1502df10,symt:(nil)) fixme:dbghelp:elf_search_auxv can't find symbol in module fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:process:GetLogicalProcessorInformationEx (3,(nil),0x33f074): stub fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported
http://bugs.winehq.org/show_bug.cgi?id=35582
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wpanlener@gmail.com
--- Comment #1 from Jerome Leclanche adys.wh@gmail.com --- *** Bug 35583 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=35582
Clement ZOTTI clement.zotti@sfr.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |clement.zotti@sfr.fr
--- Comment #2 from Clement ZOTTI clement.zotti@sfr.fr --- Same issue with 1.7.11 version which work before today Blizzard maintenance.
https://bugs.winehq.org/show_bug.cgi?id=35582
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win64
http://bugs.winehq.org/show_bug.cgi?id=35582
Andrew Mitchell ajmitch@ubuntu.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ajmitch@ubuntu.com
http://bugs.winehq.org/show_bug.cgi?id=35582
Tauro erick_darc@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |erick_darc@hotmail.com
--- Comment #3 from Tauro erick_darc@hotmail.com --- Same problem here :/
http://bugs.winehq.org/show_bug.cgi?id=35582
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Hardware|x86 |x86-64 Summary|Stealth WoW update makes |Stealth World of Warcraft |64-bit client crash 5-10 |update makes 64-bit client |seconds after logging in |crash 5-10 seconds after | |logging in
http://bugs.winehq.org/show_bug.cgi?id=35582
ygksmreo@grr.la changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ygksmreo@grr.la
--- Comment #4 from ygksmreo@grr.la --- Working workaround "wine Wow.exe -noautolaunch64" Only the 64bit version is crashing
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #5 from Clement ZOTTI clement.zotti@sfr.fr --- This won't work for me same crash as before.
My workaround was to rename the 64bit client Wow-64.exe into crashWow-64.exe So Wow.exe won't run 64 bit anymore.
(In reply to comment #4)
Working workaround "wine Wow.exe -noautolaunch64" Only the 64bit version is crashing
http://bugs.winehq.org/show_bug.cgi?id=35582
gpiez@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gpiez@web.de
--- Comment #6 from gpiez@web.de --- I got hit by the same bug.
"The instruction at 0x731970 referenced memory at 0x7f6abea8c028..."
Insteresting sections from pmap:
0000000000731000 36K r-x-- [ anon ] (probably warden) 000000000073a000 8K r---- [ anon ]
00007f6abea59000 2044K ----- psapi.dll.so 00007f6abec58000 4K r---- psapi.dll.so
Even if addresses differ, it looks always the same: Something is trying to access private memory from psapi.dll, which it isn't allowed to do. No lets figure out why this doesn't crash in windows :-)
http://bugs.winehq.org/show_bug.cgi?id=35582
Chris_9 jukeller@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jukeller@gmx.de
http://bugs.winehq.org/show_bug.cgi?id=35582
Shaun Sommer omegara1@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |omegara1@hotmail.com
--- Comment #7 from Shaun Sommer omegara1@hotmail.com --- I am having the same issue, however I am running the 32-bit version of the game on an old Dual core P4 processor (Gateway Profile 6 All-in-one). I have Ubuntu 13.10 and wine 1.7.11. I can get to character select but every time I go to enter world I getthe ERROR #132.
http://bugs.winehq.org/show_bug.cgi?id=35582
Arnoud Willemsen mail@lynthium.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mail@lynthium.com
http://bugs.winehq.org/show_bug.cgi?id=35582
paolinidiego paolinidiego@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |paolinidiego@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #8 from Zerohed zerohed@gmail.com --- (In reply to comment #7)
I am having the same issue, however I am running the 32-bit version of the game on an old Dual core P4 processor (Gateway Profile 6 All-in-one). I have Ubuntu 13.10 and wine 1.7.11. I can get to character select but every time I go to enter world I getthe ERROR #132.
Were you running the 64bit version and trying to run the 32bit version?
Please make sure it's [Release x86] version (and not x64), bottom left corner of the log in screen. If this is the case, rename Wow-64.exe to Wow-64.exe.bak
http://bugs.winehq.org/show_bug.cgi?id=35582
Zerohed zerohed@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zerohed@gmail.com
--- Comment #9 from Zerohed zerohed@gmail.com --- I don't know if this is helpful or not:
There's been reports of Error #132 on windows system in the last 13 hours: http://eu.battle.net/wow/en/forum/topic/9728382848
It looks like they are running 32bit windows: Operating System: Windows 7 Ultimate 32-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130828-1532)
However, this could just be the "normal" Error #132 and they just need to delete their cache folders.
http://bugs.winehq.org/show_bug.cgi?id=35582
Zerohed zerohed@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|zerohed@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #10 from Shaun Sommer omegara1@hotmail.com --- (In reply to comment #8)
(In reply to comment #7)
I am having the same issue, however I am running the 32-bit version of the game on an old Dual core P4 processor (Gateway Profile 6 All-in-one). I have Ubuntu 13.10 and wine 1.7.11. I can get to character select but every time I go to enter world I getthe ERROR #132.
Were you running the 64bit version and trying to run the 32bit version?
Please make sure it's [Release x86] version (and not x64), bottom left corner of the log in screen. If this is the case, rename Wow-64.exe to Wow-64.exe.bak
No I only have a 32-bit OS on here, and it defintely says Release x86 in the corner. I launch it with the -opengl tag as well. I can get to Character select, it just crashed when I try to log into the world. This old comp only has 2 GB of RAM...that could be an issue..
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #11 from Shaun Sommer omegara1@hotmail.com --- (In reply to comment #8)
(In reply to comment #7)
I am having the same issue, however I am running the 32-bit version of the game on an old Dual core P4 processor (Gateway Profile 6 All-in-one). I have Ubuntu 13.10 and wine 1.7.11. I can get to character select but every time I go to enter world I getthe ERROR #132.
Were you running the 64bit version and trying to run the 32bit version?
Please make sure it's [Release x86] version (and not x64), bottom left corner of the log in screen. If this is the case, rename Wow-64.exe to Wow-64.exe.bak
<code>err:service:service_send_start_message service L"BackupStack" failed to start fixme:service:scmdatabase_autostart_services Auto-start service L"BackupStack" failed to start: 1053 fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:heap:HeapSetInformation 0x1521000 0 0x193fef4 4 fixme:win:EnumDisplayDevicesW ((null),0,0x193ed18,0x00000000), stub! fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x193ec18,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x193eff8,0x00000000), stub! fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x193eef8,0x00000000), stub! fixme:win:EnumDisplayDevicesW ((null),0,0x193eff8,0x00000000), stub! fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8A8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:d3d:check_fbo_compat Format WINED3DFMT_B8G8R8X8_UNORM with rendertarget flag is not supported as FBO color attachment, and no fallback specified. fixme:win:EnumDisplayDevicesW ((null),0,0x193eef8,0x00000000), stub! err:ntdll:NtQueryInformationToken Unhandled Token Information class 28! fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x193fa6c,0,(nil),0x14fca8,0x193fa64,0x193fab8) stub! err:ntdll:NtQueryInformationToken Unhandled Token Information class 28! fixme:advapi:BuildSecurityDescriptorW ((nil),(nil),1,0x193fa68,0,(nil),0x14fca8,0x193fa60,0x193fab4) stub! fixme:winediag:AUDDRV_GetAudioEndpoint Winepulse is not officially supported by the wine project fixme:winediag:AUDDRV_GetAudioEndpoint For sound related feedback and support, please visit http://ubuntuforums.org/showthread.php?t=1960599 fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x1 at ctx(0x193b3cc,L"ntdll<elf>"), for debug_info(abbrev:0x1e36a4f0,symt:0x1e4cdf44) fixme:dbghelp_dwarf:dwarf2_parse_udt_type Unhandled Tag type 0x1 at ctx(0x193b3cc,L"ntdll<elf>"), for debug_info(abbrev:0x1e36a4f0,symt:0x1e4cdf44) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0xf at ctx(0x193b3cc,L"ntdll<elf>"), for debug_info(abbrev:0x1e36adac,symt:0x1e4cddf0) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x15 at ctx(0x193b3cc,L"kernel32<elf>"), for debug_info(abbrev:0x1e861050,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x193b3cc,L"kernel32<elf>"), for debug_info(abbrev:0x1e861050,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x193b3cc,L"libc.so.6"), for debug_info(abbrev:0x1ec33a80,symt:0x1ed0fda0) fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2) fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2) fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2) fixme:dbghelp_dwarf:compute_location Only supporting one reg (edx/19 -> -2) fixme:dbghelp_dwarf:dwarf2_parse_subprogram Unhandled Tag type 0x26 at ctx(0x193b3cc,L"libc.so.6"), for debug_info(abbrev:0x1f6db69c,symt:0x1fa0cbb4) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x193b3cc,L"libc.so.6"), for debug_info(abbrev:0x1f6db74c,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0xf at ctx(0x193b3cc,L"libc.so.6"), for debug_info(abbrev:0x1f6db74c,symt:(nil)) fixme:dbghelp_dwarf:dwarf2_parse_subprogram_block Unhandled Tag type 0x26 at ctx(0x193b3cc,L"libc.so.6"), for debug_info(abbrev:0x1fc4bf94,symt:(nil)) fixme:heap:HeapSetInformation (nil) 1 (nil) 0 fixme:process:GetLogicalProcessorInformationEx (3,(nil),0x33f074): stub fixme:winhttp:WinHttpDetectAutoProxyConfigUrl discovery via DHCP not supported</code>
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #12 from William Panlener wpanlener@gmail.com --- I suspect #11 to be a different bug related to missing rendering features in the driver for your older hardware as I mentioned in your thread on the World of Warcraft forums.
Reasons for this conclusion: * Your terminal output is different from all other reports * Your initial report was submitted 8 hours prior to the influx of users noticing the stealth update bug * Other users have reported similar issues in games other than World of Warcraft (http://forum.winehq.org/viewtopic.php?f=8&t=20494)
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #13 from William Panlener wpanlener@gmail.com --- #11 possible duplicate of http://bugs.winehq.org/show_bug.cgi?id=34871
http://bugs.winehq.org/show_bug.cgi?id=35582
roi1979 roi@torkilsheyggi.fo changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |roi@torkilsheyggi.fo
http://bugs.winehq.org/show_bug.cgi?id=35582
yann_c@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yann_c@yahoo.com
http://bugs.winehq.org/show_bug.cgi?id=35582
alburnett@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alburnett@gmail.com
--- Comment #14 from alburnett@gmail.com --- This issue is also present with Wine 1.6.2 on Debian Testing.
Also, the error still happens if you copy a new known good instance from Windows (v7 x64).
http://bugs.winehq.org/show_bug.cgi?id=35582
Skip Huffman skiphuffman@spamcop.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |skiphuffman@spamcop.net
--- Comment #15 from Skip Huffman skiphuffman@spamcop.net --- I believe I am also experiencing this error. on or about the twelfth I began to be unable to play. I could log in and select a character, but as the game tried to load, the progress bar would reach about 80% and then stall. Linux controls would then appear on the bottom of the screen and I would have to kill the wine environment.
I tried several things, up to and including deleting and reinstalling WoW.
After the reinstall I find myself no longer able to even log in. I get a flash of error #105 and then a message that I am disconnected from the server.
As a final step, I upgraded Wine to the latest unstable version. wine-1.7.12
Then I noticed this defect report. A bit late, but I thought my experience could be useful to the process.
I will be following this defect.
http://bugs.winehq.org/show_bug.cgi?id=35582
ogunden@phauna.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ogunden@phauna.org
http://bugs.winehq.org/show_bug.cgi?id=35582
rankincj@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rankincj@yahoo.com
--- Comment #16 from rankincj@yahoo.com --- I am also experiencing this bug, except that the 32 bit client is crashing for me too. I am launching it using the following command line:
$ Wow.exe -opengl -noautoload64bit
Crash log and terminal output are attached.
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #17 from rankincj@yahoo.com --- Created attachment 47545 --> http://bugs.winehq.org/attachment.cgi?id=47545 Terminal output when Wow.exe crashes.
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #18 from rankincj@yahoo.com --- Created attachment 47546 --> http://bugs.winehq.org/attachment.cgi?id=47546 Wow crash log
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #19 from rankincj@yahoo.com --- (In reply to comment #16)
I am also experiencing this bug, except that the 32 bit client is crashing for me too.
BTW, I am using the Wine RPMs from Fedora 20 with the latest Mesa binaries from git and a Radeon HD4890 graphics card.
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #20 from rankincj@yahoo.com --- I can make my 32 bit WoW client not crash by doing the following:
- Stop using "pulse" as the default ALSA device. - Turning my microphone "off".
This makes it impossible to use WoW's built-in voice chat, of course.
http://bugs.winehq.org/show_bug.cgi?id=35582
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |passion_visions@yahoo.com
--- Comment #21 from Dmitry Timoshkov dmitry@baikal.ru --- *** Bug 35607 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=35582
Pavel 89807457050@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |89807457050@mail.ru
--- Comment #22 from Pavel 89807457050@mail.ru --- The simple way to play wow: rename Wow-64.exe into Wow-64.exe.bak and start Wow.exe
thanks #4, #5
FOR TROUBLESHOOTING 1. It first appear 19 Feb 2014. It was wow fix 2. Same error exists before 19 Feb 2014 with another Blizzrd application (HS and BN) May be some code was implemented in wow 3. It stop: at 90% of loading character screen at addons 4. It work from Windows (if you have installed it into ntfs, etc)
I reinstall wine I update nvidia driver
I have 64xubuntu 12.10 at Intel with nvidia 670
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #23 from Pavel 89807457050@mail.ru --- 5. Probably it's Agent (aka battlenet-update-agent, aka Agent.exe) problem. Error from wow lead to https://eu.battle.net/support/en/article/cannot-communicate-with-battlenet-u... and I "Try manually updating Agent." It become an error. It didn't work. Wow probably start this agent at 90%. Agent have bug which crush Agent, then Agent crush wow.
My path to game /media/<user>/<HD name>/<folder1>/<folder2>/<wow folder>
I hope it help
http://bugs.winehq.org/show_bug.cgi?id=35582
rankincj@grr.la changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rankincj@grr.la
--- Comment #24 from rankincj@grr.la --- Launching wow with the following
wine Wow.exe -opengl -noautolaunch64bit
is now throwing out this error at the tail end when closing wow using the "exit game" option.
[2014-02-19T13:22:05Z][..\source\main.cpp:668][INFO]: System Survey 2.2.0.30, Data Version 2, Git Revision v2.2.0-3-g6536049, Copyright (C) 2013 Blizzard Entertainment. All rights reserved. [2014-02-19T13:22:05Z][..\source\main.cpp:731][INFO]: Exit value: 0
http://bugs.winehq.org/show_bug.cgi?id=35582
Adrian xadrianx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xadrianx@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=35582
wrayn@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wrayn@gmx.net
--- Comment #25 from wrayn@gmx.net --- also reproducible here with the 32-bit client by staying in the character selection screen and continuously turning your character around; stable as soon as I'm ingame, though.
http://bugs.winehq.org/show_bug.cgi?id=35582
chris@novazur.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |chris@novazur.fr
http://bugs.winehq.org/show_bug.cgi?id=35582
Jase Whipp jason.whipp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jason.whipp@gmail.com
--- Comment #26 from Jase Whipp jason.whipp@gmail.com --- Same issue here in both dev and stable wine from the Ubuntu wine PPA.
Tested versions 1.6.1 and 1.7.12. I don't see it happen on the 32 bit client at all.
System:
Ubuntu 13.10, AMD Phenom II x4, 8 Gig ram.
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #27 from Skip Huffman skiphuffman@spamcop.net --- Would it be inappropriate to put a link to instructions on how to install/run a 32 bit client on 64bit linux/wine?
http://bugs.winehq.org/show_bug.cgi?id=35582
Kevin Lyles kevinlyles@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kevinlyles@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=35582
Fresno acafresna@ono.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |acafresna@ono.com
http://bugs.winehq.org/show_bug.cgi?id=35582
zach.huff.386@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zach.huff.386@gmail.com
--- Comment #28 from zach.huff.386@gmail.com --- New WoW patch was released today 64 bit is working now.
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #29 from Yann Christin yann_c@yahoo.com --- @Zach: I still have the Problem. Which version of wine did you use?
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #30 from Zach zach.huff.386@gmail.com --- (In reply to Yann Christin from comment #29)
@Zach: I still have the Problem. Which version of wine did you use?
I'm on WoW US using the CSMT patched wine on arch linux wine-d3dstream-git
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #31 from Zach zach.huff.386@gmail.com --- It's now crashing again not sure why it worked. I was testing the d3d CSMT patch to compare performance with d3d and opengl. After that I thought the game might run in 64 bit with the patched wine version so I renamed my Wow-64.exe back to the original name and started it by running Wow-64.exe, it crashed on loading screen. Then I tried starting it with the launcher it downloaded/installed some update and started the game, I saw x64 in the bottom left at the login screen. I logged in and it was working, I exited and started the game multiple times that night. Then later I reverted back to unpatched wine from the arch repo to continue running game in opengl and it started crashing again. I tried installing the CSMT patched wine again but it still crashed.
http://bugs.winehq.org/show_bug.cgi?id=35582
Scott glajchs@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |glajchs@gmail.com
--- Comment #32 from Scott glajchs@gmail.com --- http://us.battle.net/wow/en/forum/topic/11915701490
"Seems like a fix was issued and then reverted 3 hours later. The change seems to be server-side since as far as I can tell no relevant client-side files have changed between the "working" and "not working" states.
Anyone claiming to have it working should reopen the game and retest. Anyone who cannot get it working simply missed the window of opportunity."
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #33 from chris@novazur.fr --- 64 bit version works for me now, after last update.
http://bugs.winehq.org/show_bug.cgi?id=35582
Sarah wintertanz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wintertanz@gmail.com
--- Comment #34 from Sarah wintertanz@gmail.com --- It worked briefly after today’s patch, but stopped working again later. After logging out to switch characters, the familiar crash happened.
http://bugs.winehq.org/show_bug.cgi?id=35582
shatteredlites@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |shatteredlites@gmail.com
--- Comment #35 from shatteredlites@gmail.com --- so how is this going will this be fixed soon?
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #36 from Sarah wintertanz@gmail.com --- Seems to be working again in 1.7.16 trunk (at least since wine-1.7.16-133-gd8ca8c2). See http://us.battle.net/wow/en/forum/topic/11675557804?page=7#128
I can confirm this. Using unpatched wine 1.7.16 from trunk, the 64 bit client is not crashing anymore.
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #37 from gpiez@web.de --- I can confirm that wine-1.7.16 crashes, while wine-git works. So this will probably be fixed in 1.7.17. A shame that 1.7.13 gives me 30 fps more...
http://bugs.winehq.org/show_bug.cgi?id=35582
--- Comment #38 from chris@novazur.fr --- (In reply to gpiez from comment #37)
I can confirm that wine-1.7.16 crashes, while wine-git works.
confirmed ! 64 bits version of wine-git freeze a few sec on caract choose, but doesn't crash.
http://bugs.winehq.org/show_bug.cgi?id=35582
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #39 from Jerome Leclanche adys.wh@gmail.com --- Does look fixed. Not sure if it's fixed in Wine or wow though.
https://bugs.winehq.org/show_bug.cgi?id=35582
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #40 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.17.
-
wine-bugs＠winehq.org