http://bugs.winehq.org/show_bug.cgi?id=25205
Summary: WoW Launcher does not start Product: Wine Version: unspecified Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nagybal@gmx.net
this bug exist for longer now. But since 1.2 for sure.
The error is about some Mismatched architecture '#arch=win64' and a not a valid registry file.
Please find shot log attached.
I am unable to run the updates without the Launcher. The only way I can patch the game is grabbing the patched version from a friend.
http://bugs.winehq.org/show_bug.cgi?id=25205
--- Comment #1 from Balazs Nagy nagybal@gmx.net 2010-11-17 15:17:31 CST --- Created an attachment (id=32003) --> (http://bugs.winehq.org/attachment.cgi?id=32003) wow does not start
http://bugs.winehq.org/show_bug.cgi?id=25205
Balazs Nagy nagybal@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #32003|Launcher |Launcher.txt filename| |
http://bugs.winehq.org/show_bug.cgi?id=25205
Balazs Nagy nagybal@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nagybal@gmx.net
http://bugs.winehq.org/show_bug.cgi?id=25205
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #32003|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=25205
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #2 from Juan Lang juan_lang@yahoo.com 2010-11-17 15:46:34 CST --- Your configuration is invalid. Probably you've updated to a 64-bit distro? In any event, create a new wineprefix and install WoW into it.
http://bugs.winehq.org/show_bug.cgi?id=25205
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Juan Lang juan_lang@yahoo.com 2010-11-17 15:48:45 CST --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=25205
Balazs Nagy nagybal@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #4 from Balazs Nagy nagybal@gmx.net 2010-11-17 16:03:27 CST --- I use 64x openSUSE since I use linux for six years now. Only the wow and wine packages update.
Maybe I carry the .wine config files after every bigger disto update but thats it.
Can we handle this case as a bug? As I did nothing to my wine configuration. Where shall I start looking for the corrupted config files?
I googled wineprefix as well. Wow is a 27 GB big game in size. Can I just use the already existing installation?
http://bugs.winehq.org/show_bug.cgi?id=25205
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-18 06:33:59 CST --- Apparently you've installed 64-bit Wine package. Install 32-bit one instead. Also when reporting a bug always specify Wine version.
http://bugs.winehq.org/show_bug.cgi?id=25205
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-18 06:34:16 CST --- Closing invalid.
http://bugs.winehq.org/show_bug.cgi?id=25205
Balazs Nagy nagybal@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |1.3.7 Resolution|INVALID |FIXED
http://bugs.winehq.org/show_bug.cgi?id=25205
Balazs Nagy nagybal@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|FIXED |
--- Comment #7 from Balazs Nagy nagybal@gmx.net 2010-11-20 01:37:32 CST --- Dear All,
How you exactly meant installing the 32 bit version??? I do have a 64 bit architecture. If I remove (using Yast) the wine package and leave the package wine-32bit wine does not start at all.
And again. I did not change anything, it worked earlier. The only thing what happened that I installed the updates for wine and the game itself.
Please advise.
Thank You
http://bugs.winehq.org/show_bug.cgi?id=25205
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|nagybal@gmx.net |marcus@jet.franken.de
--- Comment #8 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-20 04:49:36 CST --- Adding Marcus, perhaps he has some ideas for you to suggest.
Please use user support forums for general help.
http://bugs.winehq.org/show_bug.cgi?id=25205
Marcus Meissner marcus@jet.franken.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |ASSIGNED Ever Confirmed|0 |1
--- Comment #9 from Marcus Meissner marcus@jet.franken.de 2010-11-20 05:16:38 CST --- You probably have a 32bit wine RPM installed, instead of the 64bit wine.
rpm -q --qf '%{ARCH}' wine
should show x86_64 instead of i586.
If it does not, install the 64bit RPM.
rpm -e wine zypper in wine
should do the trick automatically.
The setup that should work is like: wine - 64bit stuff wine-32bit - 32bit stuff
http://bugs.winehq.org/show_bug.cgi?id=25205
Marcus Meissner marcus@jet.franken.de changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|wine-bugs@winehq.org |marcus@jet.franken.de
http://bugs.winehq.org/show_bug.cgi?id=25205
--- Comment #10 from Balazs Nagy nagybal@gmx.net 2010-11-21 07:58:01 CST --- Dear Herr Meissner,
thank you for your help. Checked the version. The output what I get is x86_64. Seems to be the correct one. I do have both installed: wine and wine-32bit. I tried to remove the wine-32bit so I have the 64 bit version only but then yast wants to remove wine too.
http://wiki.jswindle.com/index.php/Wine_Prefixes
export WINEPREFIX=$HOME/.wine-wow/ winecfg
This helped. Now shall we move this conversion to a forum? I would like to find that corrupted setting. I have other configuration on the .wine folder which got lost like this. (Sound with logitech headset etc.)
http://bugs.winehq.org/show_bug.cgi?id=25205
--- Comment #11 from Balazs Nagy nagybal@gmx.net 2010-11-21 14:49:12 CST --- Seems to be that there is a difference if I create a 64-bit or a 32-bit WINEPREFIX
export WINEPREFIX=$HOME/.wine-wow/ WINEARCH=win32
I googled it but I was unable to find out how can I figure it out what 32 or 64 bit "prefix" I am using in my .wine directory right now.
http://bugs.winehq.org/show_bug.cgi?id=25205
--- Comment #12 from Marcus Meissner marcus@jet.franken.de 2010-11-21 18:53:46 CST --- $ grep arch= ~/.wine/system.reg #arch=win64
would be a 64bit prefix. win32 would be a 32bit prefix.
(replace .wine with your WINEPREFIX)
we can communicate hzere , or via private mail ( marcus@jet.franken.de )
http://bugs.winehq.org/show_bug.cgi?id=25205
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |INVALID AssignedTo|marcus@jet.franken.de |wine-bugs@winehq.org
--- Comment #13 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-22 17:15:50 CST --- Thanks Marcus. Marking this bug as invalid, please consult user support forums for further help.
http://bugs.winehq.org/show_bug.cgi?id=25205
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Dmitry Timoshkov dmitry@codeweavers.com 2010-11-22 17:16:04 CST --- Closing invalid.