http://bugs.winehq.org/show_bug.cgi?id=21269
Summary: Babylon 5 - I've Found Her: crashes when colliding with objects if using a joystick Product: Wine Version: 1.1.35 Platform: x86 URL: http://ifhgame.ru/download/ifh11_setup.exe OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: 011001@web.de
The game crashes if you're using a joystick and your ship collides with an object.
Setting the game not to use force feedback makes no difference to the bug but setting the controls not to use a joystick at all makes it dissapear.
The fastest way to reproduce this i can think of is: Go to http://www.ifhgame.ru/ and download the “Babylon 5: I’ve Found Her” prequel campaign “Danger and Opportunity” Full Package for Windows. Direct link: http://ifhgame.ru/download/ifh11_setup.exe Install and start the game. Start a new Campain, not the Training, and fly towards some nearby object till you collide with it. You might need to take a look at the control settings to do this.
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download, Installer
http://bugs.winehq.org/show_bug.cgi?id=21269
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|Installer |
--- Comment #1 from Jeff Zaroyko jeffz@jeffz.name 2010-01-06 18:46:22 --- please attach the terminal output including the crash as a file.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #2 from Jens 011001@web.de 2010-01-06 19:55:04 --- Created an attachment (id=25599) --> (http://bugs.winehq.org/attachment.cgi?id=25599) Terminal output 1, but game does not start with this
Tried starting the game from the terminal to record the output but it does not get beyond the launcher screen with this.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #3 from Jens 011001@web.de 2010-01-06 20:10:31 --- (In reply to comment #1)
please attach the terminal output including the crash as a file.
Done, but the game does not start beyond the launcher screen when i try it like that. I used the same command line that is used by the application launcher that was created by wine, which i usually use to start the game. I've no idea why it's not working this way. How can i fix that? But interestingly enough it tells something about problems with the joystick.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #4 from Jeff Zaroyko jeffz@jeffz.name 2010-01-06 20:45:03 --- (In reply to comment #3)
I used the same command line that is used by the application launcher that was created by wine, which i usually use to start the game.
That's not the same as using the launcher. The application launcher usually sets a working directory, you will have to do this manually.
http://wiki.winehq.org/FAQ#head-8d8c06cf7fb33269c085a07531b61e5c730566e0
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #25599|0 |1 is obsolete| |
--- Comment #5 from Jens 011001@web.de 2010-01-07 10:01:44 --- Created an attachment (id=25604) --> (http://bugs.winehq.org/attachment.cgi?id=25604) Terminal output 2, the last two lines appeared when the game crashed
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #6 from Jens 011001@web.de 2010-01-07 10:06:19 --- (In reply to comment #4)
Thank you! That worked. Please see terminal output 2.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #7 from Jeff Zaroyko jeffz@jeffz.name 2010-01-07 18:26:49 --- (In reply to comment #5)
Created an attachment (id=25604)
--> (http://bugs.winehq.org/attachment.cgi?id=25604) [details]
Terminal output 2, the last two lines appeared when the game crashed
There is no crash output here. See if you can get a proper backtrace by starting the game with winedbg http://wiki.winehq.org/Backtraces
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #8 from Jens 011001@web.de 2010-01-08 09:05:56 --- Created an attachment (id=25610) --> (http://bugs.winehq.org/attachment.cgi?id=25610) Terminal output 3, backtrace attempt
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #9 from Jens 011001@web.de 2010-01-08 09:23:00 --- (In reply to comment #7)
There is no crash output here. See if you can get a proper backtrace by starting the game with winedbg
I've attempted a backtrace. See terminal output 3. But it does not seem any better. It also ends in a empty line and does not give me any command prompt after crashing. Typing 'quit' worked, though. ^^
I hope i'm competent enough to compile wine from source, if that is necessary?
Also, is it safe to assume that the responsible component is winmm?
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #25610|0 |1 is obsolete| |
--- Comment #10 from Jens 011001@web.de 2010-03-24 13:57:47 --- Created an attachment (id=27016) --> (http://bugs.winehq.org/attachment.cgi?id=27016) Backtrace
I noticed i tried to do the backtrace on the wrong process. Sorry for that.
This looks more like a proper backtrace i guess.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #11 from Jens 011001@web.de 2010-04-04 14:43:17 --- Created an attachment (id=27206) --> (http://bugs.winehq.org/attachment.cgi?id=27206) Backtrace with WINE 1.1.42 compiled from source with CFLAGS="-O0 -g -gdwarf-2"
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #12 from Jens 011001@web.de 2010-04-04 14:55:39 --- (In reply to comment #7)
Since i couldn't find any function names or line numbers in my first backtrace i compiled WINE 1.1.42 from source using this command: make depend && make CFLAGS="-O0 -g -gdwarf-2"
and did a new backtrace (please see above). But it doesn't contain any function names or line numbers either.
Is there anything else i can do?
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #13 from Vitaliy Margolen vitaliy@kievinfo.com 2010-04-04 20:59:45 --- (In reply to comment #11)
jens@NE51:~$ winedbg
You sure you are using the self-compiled Wine and not the one form your system?
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #14 from Jens 011001@web.de 2010-04-05 03:38:06 --- (In reply to comment #13)
Pretty much. I first removed my previous wine installation using: sudo apt-get remove wine
(which left ~/.wine untouched) and made sure it was gone by trying to execute the commands "wine" and "winecfg".
Also, after compiling, the first thing i did was executing winecfg to have a look at the version number which was 1.1.42. I hadn't installed that version on my system before, i'm sure i didn't do any update since it was released.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #15 from Vitaliy Margolen vitaliy@kievinfo.com 2010-04-05 09:00:07 --- (In reply to comment #14) Then run your self-compiled Wine directly from source directory where you compiled it, without even installing it. Ex:
~/wine.git/wine winedbg game.exe
If that won't work, recompile Wine with -O2 instead of -O0.
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #25604|0 |1 is obsolete| | Attachment #27016|0 |1 is obsolete| | Attachment #27206|0 |1 is obsolete| |
--- Comment #16 from Jens 011001@web.de 2010-04-05 10:32:21 --- Created an attachment (id=27222) --> (http://bugs.winehq.org/attachment.cgi?id=27222) Backtrace
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #17 from Jens 011001@web.de 2010-04-05 10:48:28 --- (In reply to comment #15)
That seems to have done the trick! Please see new attached backtrace above.
Does this now include every information you would expect from a good backtrace or is there something else i can do?
Btw. how is it that this gives another output than my previous try? Does "sudo apt-get remove wine" and "sudo checkinstall" not completely replace the previous installed version of Wine with the newly compiled one? My System is Ubuntu 9.10 btw. if that is of any relevance.
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |directx-dinput
--- Comment #18 from Jens 011001@web.de 2010-04-07 14:46:35 --- Changed the component from Unknown to DirectX DInput.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #19 from Jens 011001@web.de 2010-12-17 03:03:11 CST --- This bug is still present in Wine 1.3.9.
By now i'm using a different mashine (only kept the joystick). Ubuntu 10.10 x86_64 GNU/Linux 2.6.35-23-generic
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Platform|x86 |x86-64
http://bugs.winehq.org/show_bug.cgi?id=21269
Lucas Fialho Zawacki lfzawacki@yahoo.com.br changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lfzawacki@yahoo.com.br
--- Comment #20 from Lucas Fialho Zawacki lfzawacki@yahoo.com.br 2012-04-04 17:04:24 CDT --- Still present in Wine 1.5.1. I'm going to give this bug a look when I have some time.
http://bugs.winehq.org/show_bug.cgi?id=21269
--- Comment #21 from Lucas Fialho Zawacki lfzawacki@yahoo.com.br 2012-04-17 14:02:34 CDT --- A fix for this is present in Wine 1.5.2, works for me. Can the OP retest?
http://bugs.winehq.org/show_bug.cgi?id=21269
Jens 011001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #22 from Jens 011001@web.de 2012-04-22 15:25:27 CDT --- Yes, i can confirm this issue is fixed in 1.5.2 for me, too. Thanks alot!
I'm marking this as fixed then.
http://bugs.winehq.org/show_bug.cgi?id=21269
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Alexandre Julliard julliard@winehq.org 2012-04-27 12:59:31 CDT --- Closing bugs fixed in 1.5.3.