https://bugs.winehq.org/show_bug.cgi?id=43768
Bug ID: 43768 Summary: crash game Product: Wine-staging Version: 2.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: paolinidiego@gmail.com CC: erich.e.hoover@wine-staging.com, michael@fds-team.de, sebastian@fds-team.de Distribution: ---
Created attachment 59271 --> https://bugs.winehq.org/attachment.cgi?id=59271 log
crash while loading the character.
https://bugs.winehq.org/show_bug.cgi?id=43768
paolinidiego paolinidiego@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|crash game |WOW crash game
https://bugs.winehq.org/show_bug.cgi?id=43768
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |normal Version|2.17 |2.0
--- Comment #1 from Sebastian Lackner sebastian@fds-team.de --- I assume you refer to the game World of Warcraft, is that correct? Not critical, see bug reporting guideline. Also, you didn't fill out the version information correctly, the log shows you are using 2.0 and not 2.17.
The error you encounter is most likely this:
--- snip --- wine client error:0: version mismatch 525/447. Your wine binary was not upgraded correctly, or you have an older one somewhere in your PATH. Or maybe the wrong wineserver is still running? --- snip ---
It seems like you are still running an old version of Wine in the background. Please terminate the old processes and then try again. This error can also be caused by mixing files from multiple installations. If you have compiled Wine yourself in the past, make sure to uninstall those files before using a package version. Another idea you could try is to upgrade to the latest version 2.17.
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #2 from paolinidiego paolinidiego@gmail.com --- ok thanks a lot, Monday I try to cancel everything, thanks for the help.
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #3 from paolinidiego paolinidiego@gmail.com --- I tried to eliminate all the wine installations, I compiled I have nothing, and reinstalled the wine staging from the repo as a guide on the site but still the same problem. if you have any suggestions I am here. (google translate)
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #4 from paolinidiego paolinidiego@gmail.com --- Created attachment 59272 --> https://bugs.winehq.org/attachment.cgi?id=59272 crash wine-staging 2.17
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #5 from Sebastian Lackner sebastian@fds-team.de --- Now it is the correct version of Wine, but it seems like you are not using a clean prefix:
--- snip --- err:winediag:wined3d_dll_init The GLSL shader backend has been disabled. You get to keep all the pieces if it breaks. --- snip ---
Also, the path where WOW is installed looks unusual: "Z:\home\azzurra\wow\...". Typically it should be located in your wine prefix.
If you still remember which changes you did in this specific prefix please try to undo them. Otherwise, I would suggest to start again with a clean prefix. To do that you can delete or rename the ~/.wine directory in your home folder. Afterwards, it is necessary to install Battle.Net and WOW from scratch.
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #6 from paolinidiego paolinidiego@gmail.com --- the wine prefix is clean, just created. wow is in that folder because i installed it there. he has been there for 10 years.
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #7 from Sebastian Lackner sebastian@fds-team.de --- (In reply to paolinidiego from comment #6)
the wine prefix is clean, just created. wow is in that folder because i installed it there. he has been there for 10 years.
It is not a clean prefix, by default the GLSL backend is enabled. What has changed in the past is WOW itself, it now tries to use DX11 by default which only works with the GLSL backend.
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #8 from paolinidiego paolinidiego@gmail.com --- I turned off glsl, just created the new prefix, by comments, say to disable it, that wow has more performance
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #9 from paolinidiego paolinidiego@gmail.com --- Created attachment 59289 --> https://bugs.winehq.org/attachment.cgi?id=59289 reinstalled the game, but the problem persists.
https://bugs.winehq.org/show_bug.cgi?id=43768
Ker noa blue-t@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t@web.de
--- Comment #10 from Ker noa blue-t@web.de --- since we have as a last line fixme:file:MoveFileWithProgressW MOVEFILE_WRITE_THROUGH unimplemented
this reminds me of https://bugs.winehq.org/show_bug.cgi?id=43857 where i had a similiar issue (although i didn't attach the complete console output)
https://bugs.winehq.org/show_bug.cgi?id=43768
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #11 from joaopa jeremielapuree@yahoo.fr --- Does the bug still occur with wine-5.11?
https://bugs.winehq.org/show_bug.cgi?id=43768
--- Comment #12 from joaopa jeremielapuree@yahoo.fr --- No news from the reporter since 7 years more. And surely invalid since not using a clean wineprefix.
Can an administrator close this bug as ABANDONED?
https://bugs.winehq.org/show_bug.cgi?id=43768
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED
--- Comment #13 from Gijs Vermeulen gijsvrm@gmail.com --- Resolving ABANDONDED as per Comment #12.
-
wine-bugs＠winehq.org -
WineHQ Bugzilla