http://bugs.winehq.org/show_bug.cgi?id=18675
Antoine Mazeas antoine@karthanis.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |antoine@karthanis.net
Robert Gladson hiddenfoxling@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |hiddenfoxling@gmail.com
seiichiro0185@tol.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |seiichiro0185@tol.ch
Jonathan Hunt jonathan@xlcus.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan@xlcus.com
Øyvind L Nygård rapseknaps@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rapseknaps@gmail.com
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED Status|RESOLVED |CLOSED
--- Comment #20 from Antoine Mazeas antoine@karthanis.net 2009-07-20 12:22:11 CDT --- Since 1.1.22, a previously installed GW setup tries to repair the data on every start (as the title says). It has nothing to do with installation, which has been addressed, since it has been tested against a fresh "-image" (aka "download all contents before launch") install: it still tries to repair on every start.
--- Comment #21 from Jamin Collins jcollins@asgardsrealm.net 2009-07-20 12:27:29 CDT --- Created an attachment (id=22478) --> (http://bugs.winehq.org/attachment.cgi?id=22478) Reverts the problematic git commit.
The solution, as indicated elsewhere in this bug report is to revert the problematic commit. The attached patch does so.
--- Comment #22 from Robert Gladson hiddenfoxling@gmail.com 2009-07-22 19:12:50 CDT --- This issue continues to permeate in the offical 1.1.26 repositories for Debian. Is there a reason for the problematic git change?
--- Comment #23 from Dmitry Timoshkov dmitry@baikal.ru 2009-07-28 01:52:37 CDT --- See the comments in this bug, it's the bug in GuildWars. The bug is still open because apparently Windows memory layout permits this buggy app to survive.
--- Comment #24 from Jan Kalab pitlicek@gmail.com 2009-07-28 02:57:40 CDT --- I just submitted a ticket to their support system:
Hi, I'm sorry to announce you that your game doesn't work in Linux under Wine (http://www.winehq.org). But it used to. But since Wine developers made some changes in recent versions, one bug in your code appeared.
Bug report in Wine's bugzilla is here: http://bugs.winehq.org/show_bug.cgi?id=18675 I recommend to notice comment #14 by Alexander Juliard (one of leading Wine developer) who explains what's wrong in your code.
I hope you will fix it soon, so we, Linux gamers, can play your game again.
--- Comment #25 from nh2@deditus.de 2009-07-28 06:39:07 CDT --- @ Jan Kalab: Is the GW ticket system open/viewable so that we can see if there are questions, comments or progress?
--- Comment #26 from Jan Kalab pitlicek@gmail.com 2009-07-28 07:24:09 CDT --- Unfortunately not. But I'll post updates when something important happens. Current status is:
We are going to escalate your request to a senior customer support representative. We will get back to you as soon as possible to provide a solution for the issue you reported.
--- Comment #27 from Jan Kalab pitlicek@gmail.com 2009-08-04 03:10:11 CDT --- Here is the reply from NCsoft:
Guild Wars was developed on and released for native Windows based PCs. We are aware that there is an interest in having the game available using other operating systems or on other platforms, and we will continue to evaluate these possibilities in the future.
While not officially supported, you can read this article (http://wiki.guildwars.com/wiki/Guild_Wars_on_CrossOver) about using CrossOver to possibly play Guild Wars on an Intel based Macintosh with BootCamp or Linux based computer.
Unfortunately, I am afraid that Guild Wars is not officially supported for this Operating Systems and therefore we are unable to assist you further.
--- Comment #28 from Lee Ball lee@leenukes.co.uk 2009-08-05 09:13:40 CDT --- (In reply to comment #27)
There is also a mention of the Bug on this page: http://wiki.guildwars.com/wiki/Guild_Wars_on_Wine
"Issue with newer versions
As of wine 1.1.21 Guild Wars will try to repair the data archive on every start, and possibly not install. This is due to a memory allocation bug in Guild Wars. A support ticked to arena.net has been filed for this issue. See the wine bugzilla for details. Older versions work fine."
Here is the reply from NCsoft:
Guild Wars was developed on and released for native Windows based PCs. We are aware that there is an interest in having the game available using other operating systems or on other platforms, and we will continue to evaluate these possibilities in the future.
While not officially supported, you can read this article (http://wiki.guildwars.com/wiki/Guild_Wars_on_CrossOver) about using CrossOver to possibly play Guild Wars on an Intel based Macintosh with BootCamp or Linux based computer.
Unfortunately, I am afraid that Guild Wars is not officially supported for this Operating Systems and therefore we are unable to assist you further.
--- Comment #29 from Øyvind L Nygård rapseknaps@gmail.com 2009-08-05 10:51:37 CDT --- Yea, I wrote that, that just reflects what's written here.
--- Comment #30 from Alexandre Julliard julliard@winehq.org 2009-08-05 13:22:50 CDT --- Created an attachment (id=22833) --> (http://bugs.winehq.org/attachment.cgi?id=22833) Fix realloc in place for large blocks
It's not really a GuildWars bug after all, my apologies to the GW developers...
That code path is not supposed to be triggered, what they do is something like HeapRealloc(HEAP_REALLOC_IN_PLACE_ONLY), and if that fails HeapAlloc()+memcpy+HeapFree(). We don't handle realloc in place correctly in that case which probably causes GW to fall into the memcpy code path. Attached patch should fix it.
--- Comment #31 from Alexandre Julliard julliard@winehq.org 2009-08-07 08:02:59 CDT --- Fixed by 7f64b8a9a98c849debcc779582607aaa0bf77390.
--- Comment #32 from Alexandre Julliard julliard@winehq.org 2009-08-07 12:46:09 CDT --- Closing bugs fixed in 1.1.27.