http://bugs.winehq.org/show_bug.cgi?id=27734
Summary: Aion crash every half hour and incorrectly displaying quest logs. Product: Wine Version: 1.3.23 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: mikahbot@gmail.com
Created an attachment (id=35489) --> (http://bugs.winehq.org/attachment.cgi?id=35489) Aion game crash text
So, I was able to install Aion by pulling the files from the Windows installation, installing the language font packs, mono, and the like. However, there are two things I found are annoying, and because of their frequency, I am setting the severity as major.
Problem #1: Every half hour of login time, Aion suddenly crashes. I always use it with a console command so that I can see the output and this is what I got [see attachment]. the first few lines before the ... is what I get when I play the game, and after if what happens when it crashes.
Problem #2: Every fresh login displays all the text information correctly. However, within 15 minutes or less, quest logs become glitched. When you click on a quest, I get a scroll with the text on it that's smooshed together [as is the easiest to explain]. Instead of being neatly separated as you see in this text, it's glued together. It's the same for the tracking options on the top right.
Is anyone else having these problems and if so, is there a possible fix or a workaround? Also, the options in the system menu don't seem to want to stick.
http://bugs.winehq.org/show_bug.cgi?id=27734
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |normal
--- Comment #1 from Jeff Zaroyko jeffz@jeffz.name 2011-07-08 20:24:30 CDT --- not major: http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
Is that the full output after acknowledging the crash dialog?
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #2 from mikahbot@gmail.com 2011-07-08 20:35:14 CDT --- (In reply to comment #1)
not major: http://bugs.winehq.org/page.cgi?id=fields.html#bug_severity
Is that the full output after acknowledging the crash dialog?
As far as I know, that is the last end of the log that I copied from the screen in konsole. When the game runs, this is what it constantly outputs: . err:d3d_surface:surface_load Not supported on scratch surfaces. err:d3d_surface:surface_load Not supported on scratch surfaces. err:d3d_surface:surface_load Not supported on scratch surfaces. err:d3d_surface:surface_load Not supported on scratch surfaces.
I truncated that, cause really that's all it shows. Then, as you saw in the attachment, that was the most important part that I thought. If you need more than that, how do I show you the full error log?
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #3 from Alex Bradbury asb@asbradbury.org 2011-07-09 02:58:13 CDT --- (In reply to comment #2)
I truncated that, cause really that's all it shows. Then, as you saw in the attachment, that was the most important part that I thought. If you need more than that, how do I show you the full error log?
http://wiki.winehq.org/FAQ#get_log
Use shell redirection to output to a file, then upload that file.
http://bugs.winehq.org/show_bug.cgi?id=27734
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #4 from Dan Kegel dank@kegel.com 2011-07-09 10:35:13 CDT --- There is one interesting line: err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash Bug 22482 mentions a few things one could try (e.g. winetricks ddr=opengl although I doubt Aion uses directdraw).
Does it help to follow the install procedure and tips in Aion's appdb page? http://appdb.winehq.org/objectManager.php?sClass=version&iId=20402
http://bugs.winehq.org/show_bug.cgi?id=27734
mikahbot@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #35489|0 |1 is obsolete| |
--- Comment #5 from mikahbot@gmail.com 2011-07-09 19:50:14 CDT --- Created an attachment (id=35503) --> (http://bugs.winehq.org/attachment.cgi?id=35503) The full log of errors gotten when the game crashed
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #6 from mikahbot@gmail.com 2011-07-09 19:57:48 CDT --- Created an attachment (id=35504) --> (http://bugs.winehq.org/attachment.cgi?id=35504) The full error log, gzipped
The file was too large to do a simple attachment, so I compressed it.
http://bugs.winehq.org/show_bug.cgi?id=27734
mikahbot@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #35503|0 |1 is obsolete| |
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #7 from mikahbot@gmail.com 2011-07-09 19:59:16 CDT --- Alright, sorry it took me a while. I just attached a full log of errors when the game crashes. I had to compress it because the file was 6.9 megs in size, only because of this one line it kept constantly repeating as I played the game.
Let me know what else you guys need from my end.
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #8 from Dan Kegel dank@kegel.com 2011-07-09 20:01:54 CDT --- The key line still seems like
err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #9 from mikahbot@gmail.com 2011-07-10 13:55:36 CDT --- Created an attachment (id=35511) --> (http://bugs.winehq.org/attachment.cgi?id=35511) Different error at crash
I got a little bit of a different error this time. I didn't do a full log divert because there would be no reason, since it keeps repeating the "expect a crash" line.
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #10 from Dan Kegel dank@kegel.com 2011-07-10 14:24:09 CDT --- There's no point in logging what happens after 'expect a crash', I think.
http://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #11 from mikahbot@gmail.com 2011-07-11 21:32:55 CDT --- (In reply to comment #10)
There's no point in logging what happens after 'expect a crash', I think.
I logged it just in case it mattered, that's all. Has anyone else had the same problems as me? I find that the logs do not display correctly either when viewing them through the map or creating a quest sticky at the top right. It happens maybe ten minutes after the game has run, though the crash itself hasn't been timed yet.
I added the UseSLGL disabled line to the registry, but the crashed happened before and after, so I don't think that did anything. Should I try updating to 1.3.24?
http://bugs.winehq.org/show_bug.cgi?id=27734
legluondunet@free.fr legluondunet@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |legluondunet@free.fr
https://bugs.winehq.org/show_bug.cgi?id=27734
--- Comment #12 from Austin English austinenglish@gmail.com --- This is your friendly reminder that there has been no bug activity for over a year. Is this still an issue in current (1.7.37 or newer) wine? If so, please attach the terminal output in 1.7.37 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=27734
super_man@post.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net, | |super_man@post.com
https://bugs.winehq.org/show_bug.cgi?id=27734
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |ABANDONED Summary|Aion crash every half hour |Aion client runs out of GDI |and incorrectly displaying |object handles after half |quest logs. |an hour
--- Comment #13 from Anastasius Focht focht@gmx.net --- Hello folks,
no further response from OP, resolving 'ABANDONED'.
Regards
https://bugs.winehq.org/show_bug.cgi?id=27734
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #14 from Austin English austinenglish@gmail.com --- Closing.