https://bugs.winehq.org/show_bug.cgi?id=47265
Bug ID: 47265 Summary: Strarcraft and StarCraft II crash immediately on launch Product: Wine-staging Version: 4.9 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: darinsmiller@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 64557 --> https://bugs.winehq.org/attachment.cgi?id=64557 terminal output of crash
Battlenet launches fine, but launching StarCraft Remastered and StarCraft II crash immediately.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- Is this bug present using Wine-Staging 4.7 or 4.8?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #2 from Darin Miller darinsmiller@gmail.com --- In Wine-Staging 4.7, Starcraft Remastered would launch then drop to the background and was not playable. In 4.8, Starcraft Remastered worked perfectly.
StarCraft II has worked perfectly in all previous releases of wine-staging until 4.9.
https://bugs.winehq.org/show_bug.cgi?id=47265
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Strarcraft and StarCraft II |Starcraft and StarCraft II |crash immediately on launch |crash immediately on launch
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- I'll get to this myself if I have to, but can someone please test if reverting the recent changes to the fake DLLs patch set fix this (i.e. apply commit https://github.com/wine-staging/wine-staging/commit/5634d119e0425bb3df1d440dd010cfb051e6628d on top of upstream Wine 4.9)?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #4 from Darin Miller darinsmiller@gmail.com --- Apologies, but I never patched wine, but this is what I attempted:
On Kunbuntu, following patching instructions here: https://askubuntu.com/questions/325404/help-installing-a-patch-inside-wine
I could not force apt to retrieve winehq-staging (keeps pulling down wine-staging in the ubuntu repos).
Also, I'm uncertain how to "wget" the patch(es) referenced in the above commit as I don't see a http copy link.
If you can direct me to a better instructions, I will try again.
https://bugs.winehq.org/show_bug.cgi?id=47265
Andrew Wesie awesie@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |awesie@gmail.com
--- Comment #5 from Andrew Wesie awesie@gmail.com --- It appears to be caused by 3e927c4aec9dbeef930b83f62ee0651b8c147247 ("ntdll: Extend NtGetTickCount() to return 64-bits. Forward kernel32 functions to it.").
NtGetTickCount is commonly used for anti-debugging and such. It is possible that the commit does not play nicely with the fake dll / syscall wrappers / etc. I haven't looked into it too much yet.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #6 from Andrew Wesie awesie@gmail.com --- Created attachment 64567 --> https://bugs.winehq.org/attachment.cgi?id=64567 Create function for GetTickCount in kernel32
It seems that the issue is not the NtGetTickCount change but the fact that kernel32 redirects GetTickCount. A simple wrapper in kernel32 around NtGetTickCount appears to fix the problem in Starcraft Remastered.
https://bugs.winehq.org/show_bug.cgi?id=47265
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #7 from winetest@luukku.com --- possible dupe bug 47266
https://bugs.winehq.org/show_bug.cgi?id=47265
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47265
Vidar Haarr vhaarr+wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vhaarr+wine@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47265
Berillions berillions@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |berillions@gmail.com
--- Comment #8 from Berillions berillions@gmail.com --- The patch works for me too. I had this issue with World of Warcraft + Wine-Staging-4.9 :-)
https://bugs.winehq.org/show_bug.cgi?id=47265
Maciej Stanczew maciej.stanczew+b@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew+b@gmail.com
--- Comment #9 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Same thing with Diablo III and Heroes of the Storm. Reverting Fake DLLs commits from Staging doesn't change anything (D3 still crashes the same way). Applying the patch from comment #6 fixes the problem -- D3, SC:R, SC2 and HotS all now work again.
https://bugs.winehq.org/show_bug.cgi?id=47265
Alexandr Oleynikov sashok.olen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sashok.olen@gmail.com
--- Comment #10 from Alexandr Oleynikov sashok.olen@gmail.com --- The issue also affect Overwatch and World of Warcraft. Patch from Andrew Wesie fixes it :)
https://bugs.winehq.org/show_bug.cgi?id=47265
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
https://bugs.winehq.org/show_bug.cgi?id=47265
Sveinar Søpler cybermax@dexter.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax@dexter.no
--- Comment #11 from Sveinar Søpler cybermax@dexter.no --- (In reply to Alexandr Oleynikov from comment #10)
The issue also affect Overwatch and World of Warcraft. Patch from Andrew Wesie fixes it :)
Aye. Can confirm that too. Ref. my own bug for WoW https://bugs.winehq.org/show_bug.cgi?id=47268
Thx Awesie :)
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #12 from Zebediah Figura z.figura12@gmail.com --- *** Bug 47268 has been marked as a duplicate of this bug. ***
https://bugs.winehq.org/show_bug.cgi?id=47265
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Product|Wine-staging |Wine Keywords| |regression Regression SHA1| |3e927c4aec9dbeef930b83f62ee | |0651b8c147247 Fixed by SHA1| |13e11d3fcbcf8790e031c4bc52f | |5f550b1377b3b Component|-unknown |kernel32
--- Comment #13 from Matteo Bruni matteo.mystral@gmail.com --- This should be fixed by https://source.winehq.org/git/wine.git/commitdiff/13e11d3fcbcf8790e031c4bc52...
https://bugs.winehq.org/show_bug.cgi?id=47265
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
https://bugs.winehq.org/show_bug.cgi?id=47265
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Starcraft and StarCraft II |Multiple Blizzard games |crash immediately on launch |(Diablo III, Heroes of the | |Storm, Overwatch, | |Starcraft, StarCraft II, | |World of Warcraft) crash | |immediately on launch
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #14 from Sveinar Søpler cybermax@dexter.no --- Created attachment 64608 --> https://bugs.winehq.org/attachment.cgi?id=64608 WoW crash log
(In reply to Matteo Bruni from comment #13)
This should be fixed by https://source.winehq.org/git/wine.git/commitdiff/ 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b
Did not for me. Same problem after pulling wine-staging from today (git 1d9a3f6d12322891a2af4aadd66a92ea66479233)
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #15 from Maciej Stanczew maciej.stanczew+b@gmail.com --- For me it works with D3, SC:R, SC2 and HotS. I have compiled Staging 4.9 with applied 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b (instead of Andrew's patch).
https://bugs.winehq.org/show_bug.cgi?id=47265
tempel.julian@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tempel.julian@gmail.com
--- Comment #16 from tempel.julian@gmail.com --- It still doesn't work for me without Andrew's patch either in HotS.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #17 from Sveinar Søpler cybermax@dexter.no --- (In reply to Maciej Stanczew from comment #15)
For me it works with D3, SC:R, SC2 and HotS. I have compiled Staging 4.9 with applied 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b (instead of Andrew's patch).
Did you apply ONLY the commit patch on top of 4.9, or did you pull "up-to" from GIT? (like I did + up to HEAD) In the case of the latter, could it perhaps be some other problem this time around?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #18 from Maciej Stanczew maciej.stanczew+b@gmail.com --- Only 4.9 with applied 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b (and a small merge conflict fix). It could be some other problem, or maybe the fix works for other games but not for WoW (I have not tested WoW or Overwatch).
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #19 from Sveinar Søpler cybermax@dexter.no --- (In reply to Maciej Stanczew from comment #18)
Only 4.9 with applied 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b (and a small merge conflict fix). It could be some other problem, or maybe the fix works for other games but not for WoW (I have not tested WoW or Overwatch).
Did the exact same, and WoW still crashes. It does NOT with Andrew's patch above, so i guess this is a World of Warcraft "only" bug (and possibly OverWatch?)
Does this warrant a NEW bugreport, or should THIS bug be reopened?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #20 from Alexandr Oleynikov sashok.olen@gmail.com --- Can you please check if you are also affected by bug 47255?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #21 from Sveinar Søpler cybermax@dexter.no --- (In reply to Alexandr Oleynikov from comment #20)
Can you please check if you are also affected by bug 47255?
Yeah, it seems adding this: https://bugs.winehq.org/attachment.cgi?id=64599&action=diff from the other bug fixes it.
wine @ HEAD: 381c4e7b667555147ef24ee19fff2f766b7303c2 wine-staging @ HEAD: 671295089e11784762bc84ecbb8253e72dac43b7 + https://bugs.winehq.org/attachment.cgi?id=64599&action=diff
and World of Warcraft seems to work atleast with vkd3d/d3d12. I did not test with DXVK tho.
Thanks :)
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #22 from Sveinar Søpler cybermax@dexter.no --- (In reply to Sveinar Søpler from comment #21)
and World of Warcraft seems to work atleast with vkd3d/d3d12. I did not test with DXVK tho.
Thanks :)
I spoke too soon it seems. Although i am now able to log in without crashing, upon playing a wee bit around in the world, it seems to have created another bug.
When turning the character around, the screen kind of "skips ahead". This is horribly annoying and rather unplayable when mouselooking, cos if you run and turn around a corner, you suddenly find yourself "skipping" sometimes a LOT and you end up running into things and whatnot.
Well.. atleast something more to work with i guess.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #23 from Berillions berillions@gmail.com --- For me WoW + DXVK works correctly with Andrew patch.
But with vkd3d, the game crashes with Error 132 when i connect a character who is in a Region from BFA (Zul'Dazar for example). If i connect a character who is in an old region as Kalimdor/Orgrimmar, it works.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #24 from Alexandr Oleynikov sashok.olen@gmail.com --- (In reply to Sveinar Søpler from comment #22)
(In reply to Sveinar Søpler from comment #21)
and World of Warcraft seems to work atleast with vkd3d/d3d12. I did not test with DXVK tho.
Thanks :)
I spoke too soon it seems. Although i am now able to log in without crashing, upon playing a wee bit around in the world, it seems to have created another bug.
When turning the character around, the screen kind of "skips ahead". This is horribly annoying and rather unplayable when mouselooking, cos if you run and turn around a corner, you suddenly find yourself "skipping" sometimes a LOT and you end up running into things and whatnot.
Well.. atleast something more to work with i guess.
That sounds like bug 42675 which is unrelated to this one.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #25 from Sveinar Søpler cybermax@dexter.no --- (In reply to Alexandr Oleynikov from comment #24)
That sounds like bug 42675 which is unrelated to this one.
Really? So, you think that sounds like a mousebug from 2017 that is NOT happening with wine-staging-4.8, nor is it happening with wine-staging-4.9 with Andrew's patch?
Wine-staging-4.8 = OK wine-staging-4.9 = crashing wine-staging-4.9 + https://bugs.winehq.org/attachment.cgi?id=64567&action=diff = OK wine-staging-git(381c4e7) = crashing wine-staging-git(381c4e7) + https://bugs.winehq.org/attachment.cgi?id=64599&action=diff = Can log in, but experience "warping" when turning around.
Just finished almost 2 hours with wine-staging-4.9 + Andrew's patch and vkd3d in WoW now with no crashing or horrible issues :)
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #26 from Berillions berillions@gmail.com --- In my case, if i compile Wine-Staging-4.9 + commit 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b, WoW + vkd3d crash after login and i don't have mouse cursor.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #27 from Sveinar Søpler cybermax@dexter.no --- (In reply to Berillions from comment #26)
In my case, if i compile Wine-Staging-4.9 + commit 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b, WoW + vkd3d crash after login and i don't have mouse cursor.
I just got a black screen with ONLY that commit on top of wine-staging-4.9.
You probably need that + https://bugs.winehq.org/attachment.cgi?id=64599&action=diff to be able to log in... and probably get my "camera skipping bug" if you do.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #28 from Berillions berillions@gmail.com --- (In reply to Sveinar Søpler from comment #27)
(In reply to Berillions from comment #26)
In my case, if i compile Wine-Staging-4.9 + commit 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b, WoW + vkd3d crash after login and i don't have mouse cursor.
I just got a black screen with ONLY that commit on top of wine-staging-4.9.
You probably need that + https://bugs.winehq.org/attachment.cgi?id=64599&action=diff to be able to log in... and probably get my "camera skipping bug" if you do.
With this both patches, i still have crash + no mouse cursor
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #29 from tempel.julian@gmail.com --- Andrew's patch can't be applied anymore to latest git-master and HotS still crashes on launch.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #30 from Sveinar Søpler cybermax@dexter.no --- (In reply to tempel.julian from comment #29)
Andrew's patch can't be applied anymore to latest git-master and HotS still crashes on launch.
World of Warcraft still crashes at wine-staging-GIT c92fddae8661233e7699e1914987f0cc4caa8217
https://bugs.winehq.org/show_bug.cgi?id=47255#c13 made no change for WoW w/vkd3d atleast...
https://bugs.winehq.org/show_bug.cgi?id=47265
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be
--- Comment #31 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
With commit 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b, NtGetTickCount() is no longer DECLSPEC_HOTPATCH. Andrew Wesie's patch didn't touch that.
Maybe that makes a difference.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #32 from Alexandr Oleynikov sashok.olen@gmail.com --- Can this bug be reopened then, if it's actually not fixed?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #33 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Created attachment 64643 --> https://bugs.winehq.org/attachment.cgi?id=64643 Make patchable patch
The attached patch make the function patchable once again.
Sent upstream.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #34 from Andrew Wesie awesie@gmail.com --- (In reply to Alistair Leslie-Hughes from comment #33)
The attached patch make the function patchable once again.
The code prior to the regression (3e927c) did not have DECLSPEC_HOTPATCH. I think there would need to be some justification for why this change is necessary.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #35 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to Andrew Wesie from comment #34)
(In reply to Alistair Leslie-Hughes from comment #33)
The attached patch make the function patchable once again.
The code prior to the regression (3e927c) did not have DECLSPEC_HOTPATCH. I think there would need to be some justification for why this change is necessary.
However 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b did.
-ULONGLONG WINAPI DECLSPEC_HOTPATCH get_tick_count64(void) +ULONG WINAPI NtGetTickCount(void)
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #36 from Andrew Wesie awesie@gmail.com --- (In reply to Alistair Leslie-Hughes from comment #35)
The code prior to the regression (3e927c) did not have DECLSPEC_HOTPATCH. I think there would need to be some justification for why this change is necessary.
However 13e11d3fcbcf8790e031c4bc52f5f550b1377b3b did.
-ULONGLONG WINAPI DECLSPEC_HOTPATCH get_tick_count64(void) +ULONG WINAPI NtGetTickCount(void)
It was removed because it was no longer necessary. 3e927c made the unfortunate choice of relaying GetTickCount to NtGetTickCount. Since GetTickCount had DECLSPEC_HOTPATCH, the commit's author applied DECLSPEC_HOTPATCH to NtGetTickCount as well.
With the corrected version, 13e11d, GetTickCount is a separate function and has DECLSPEC_HOTPATCH. As such, NtGetTickCount can go back to its previous form. I'm not even convinced that DECLSPEC_HOTPATCH on NtGetTickCount does anything on wine-staging due to the syscall wrappers.
As far as testing, I compiled Wine-staging v4.9 + 13e11d + d88c40, and I had no issues starting Starcraft Remastered, Overwatch, nor World of Warcraft (without d3d12).
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #37 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- (In reply to Andrew Wesie from comment #36)
(In reply to Alistair Leslie-Hughes from comment #35) As far as testing, I compiled Wine-staging v4.9 + 13e11d + d88c40, and I had no issues starting Starcraft Remastered, Overwatch, nor World of Warcraft (without d3d12).
I've just tried Diablo 3 and didn't have a crash.
At this stage it might be a issue with something else. A regression test would be nice, if possible, for those still experiencing the crash.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #38 from Sveinar Søpler cybermax@dexter.no --- (In reply to Andrew Wesie from comment #36)
As far as testing, I compiled Wine-staging v4.9 + 13e11d + d88c40, and I had no issues starting Starcraft Remastered, Overwatch, nor World of Warcraft (without d3d12).
I cannot get WoW to start with that and vkd3d nor wined3d (d3d11) (dxvk not tested)
I have nVidia 430.14 driver tho, and did not test this with 418.52.10(or .07).
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #39 from Andrew Wesie awesie@gmail.com --- (In reply to Sveinar Søpler from comment #38)
I cannot get WoW to start with that and vkd3d nor wined3d (d3d11) (dxvk not tested)
I followed the lutris script and disabled d3d12, nvapi, and nvapi64 using winecfg. WoW crashes if I don't disable those DLLs on my system. But this is not related to this bug since I had the same problem on Wine staging 4.8.
Are you able to run WoW with wine staging 4.8 with the same prefix you are using for testing?
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #40 from tempel.julian@gmail.com --- Heroes of the Storm started crashing with this commit (and it still does with latest git-master): https://github.com/wine-staging/wine-staging/commit/071fe01910b1360b8ea0e0ac...
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #41 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Hello,
I'm able to start WoW with wine-staging v4.9 rebased on top of git@c92fdda (including both 13e11d3 and d88c403) so I confirm the bug is fixed for me.
DECLSPEC_HOTPATCH NtGetTickCount() is not required for me, but anyone still having issues is free to try that.
I'm using Debian 8 Jessie amd64, NVIDIA proprietary driver 430.14, World of Warcraft 64-bit in legacy DirectX11 mode, d3dx12 disabled+virtual desktop+no WM management/decoration in winecfg, winetricks corefont (for battle.net CEF).
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #42 from Berillions berillions@gmail.com --- For my case too, wine-staging-git with last commit and without Andrew's patch, WoW works correctly.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #43 from Sveinar Søpler cybermax@dexter.no --- (In reply to Andrew Wesie from comment #39)
(In reply to Sveinar Søpler from comment #38)
I cannot get WoW to start with that and vkd3d nor wined3d (d3d11) (dxvk not tested)
I followed the lutris script and disabled d3d12, nvapi, and nvapi64 using winecfg. WoW crashes if I don't disable those DLLs on my system. But this is not related to this bug since I had the same problem on Wine staging 4.8.
Are you able to run WoW with wine staging 4.8 with the same prefix you are using for testing?
WoW runs fine with wine-staging-4.8, and wine-staging-4.9 w/your previous patch: https://bugs.winehq.org/attachment.cgi?id=64567&action=diff in the same wineprefix.
I have not tested todays GIT, but i did test with the two patches in mention here without success.
I also was able to run WoW with some GIT commit + a patch (https://bugs.winehq.org/show_bug.cgi?id=47255#c10), but had issues with "camera-warping" when mouselooking, so that was playable for me. There is no "camera-warping" issues with -4.8 or -4.9 with your patch (nor have i had those issues in the past).
nvapi/nvapi64 is disabled in dll-overrides, but i do use virtual desktop and vkd3d. Have not tested with dxvk tho.
Ill try another GIT pull when i get home tonight and see if recent commits have made a change for me. I configure wine with the default enabled MingW-W64, as disabling this had some issues with msvcr (that probably is fixed now).
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #44 from Sveinar Søpler cybermax@dexter.no --- I noticed there was a update to WoW today. Not sure about the patchnotes yet tho.
I did a fresh compile of : wine: 4d5c874f42e27ac992f361c71490985d7553571a staging: 1998c0570d22f804fe229e75e17b282619927071
And its a success :) Dunno if it was some old crud, since others had this working with an earlier GIT HEAD, or some "fix" with todays WoW patch? Working now, so I am a happy camper.
Thx for all the help and fixes/patches for this :)
https://bugs.winehq.org/show_bug.cgi?id=47265
Arthur Huillet arthur.huillet@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |arthur.huillet@free.fr
--- Comment #45 from Arthur Huillet arthur.huillet@free.fr --- Starcraft 2 still crashes on startup with latest wine-staging. This comment has it right: https://bugs.winehq.org/show_bug.cgi?id=47265#c40 Reverting the ntdll patch makes the problem go away.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #46 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- (In reply to Arthur Huillet from comment #45)
Starcraft 2 still crashes on startup with latest wine-staging. This comment has it right: https://bugs.winehq.org/show_bug.cgi?id=47265#c40 Reverting the ntdll patch makes the problem go away.
Hello,
This is a different regression. Please, file a new bug.
Regards.
https://bugs.winehq.org/show_bug.cgi?id=47265
Steffen Klee steffen.klee@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |steffen.klee@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #47 from tempel.julian@gmail.com --- I've opened it here: https://bugs.winehq.org/show_bug.cgi?id=47332
However, I can't provide a log file atm.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #48 from Berillions berillions@gmail.com --- Now for me WoW crash at launch with wine-staging-git immediatly at launch with Error 138 ...
https://bugs.winehq.org/show_bug.cgi?id=47265
Alexandr Oleynikov sashok.olen@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|sashok.olen@gmail.com |
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #49 from Sveinar Søpler cybermax@dexter.no --- (In reply to Berillions from comment #48)
Now for me WoW crash at launch with wine-staging-git immediatly at launch with Error 138 ...
I just tested with: Wine GIT-HEAD: 48a74277f5f9e0c87d8c01457236a89d94cb71d3 Wine-staging GIT-HEAD: 5681cd5466f1dbb60b4001d5f10ae8f94db23803 vkd3d GIT-HEAD: 068851b159db40209b78e78bbebbde93ec6596af
Wow set to D3D12.
No crashing atm, so the issues seems fixed for me now tho.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #50 from Berillions berillions@gmail.com --- (In reply to Sveinar Søpler from comment #49)
(In reply to Berillions from comment #48)
Now for me WoW crash at launch with wine-staging-git immediatly at launch with Error 138 ...
I just tested with: Wine GIT-HEAD: 48a74277f5f9e0c87d8c01457236a89d94cb71d3 Wine-staging GIT-HEAD: 5681cd5466f1dbb60b4001d5f10ae8f94db23803 vkd3d GIT-HEAD: 068851b159db40209b78e78bbebbde93ec6596af
Wow set to D3D12.
No crashing atm, so the issues seems fixed for me now tho.
It works for me only if the WTF folder for WoW already exist. If this folder is empty, i have the Error 138
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #51 from Sveinar Søpler cybermax@dexter.no --- (In reply to Berillions from comment #50)
It works for me only if the WTF folder for WoW already exist. If this folder is empty, i have the Error 138
Hmm.. Interesting. Some sort of permission problem perhaps? Is the WoW folder actually INSIDE the wineprefix? Or symlink/different stuff?
Eg. /home/yourname/.wine/drive_c/Program Files (x86)/World of Warcraft/_retail_/WTF
Ofc "yourname" is your username and ".wine" is the default wineprefix.. Depending on what you use to generate wineprefixes that would be different, and could be placed anywhere, but i would THINK problems can arise if there is some sort of permission thing.
I did not have any issues removing WTF folder and let it generate (other than all my settings and stuff ofc..)
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #52 from Sveinar Søpler cybermax@dexter.no --- Oh.. Ofc removing WTF folder would mean resetting all your settings, so unless you start WoW with -d3d11 or similar option, the default WoW setting is to try d3d12 afaik.
And if you do not have vkd3d or an updated version of that, chances are you would crash...
https://bugs.winehq.org/show_bug.cgi?id=47265
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #53 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 4.10.
https://bugs.winehq.org/show_bug.cgi?id=47265
--- Comment #54 from Arthur Huillet arthur.huillet@free.fr --- My comment #45 was wrong.
https://bugs.winehq.org/show_bug.cgi?id=47265
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hewanci@gmail.com
--- Comment #55 from Matteo Bruni matteo.mystral@gmail.com --- *** Bug 47330 has been marked as a duplicate of this bug. ***
-
wine-bugs＠winehq.org