http://bugzilla.opensuse.org/show_bug.cgi?id=1009637 http://bugzilla.opensuse.org/show_bug.cgi?id=1009637#c1 Dominique Leuenberger <dimstar@opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bberberov+suse@gmail.com Flags| |needinfo?(bberberov+suse@gm | |ail.com) --- Comment #1 from Dominique Leuenberger <dimstar@opensuse.org> --- Thank you very much for your bug report (In reply to Boian Berberov from comment #0)
UFO:AI consistently crashes now. This started occurring a couple of months ago, but I don't know which is the last working version.
'a couple of months' is quite bad - and makes it quite difficult to narrow down what could cause it now. What openSUSE Version are you playing this on? (I'm just installing it again and will try to reproduce - I'm using TUmbleweed)
Steps to reproduce: - Start UFO:AI - Select "Single-Player" - Select "Skirmish" - Choose a map and "Start Game", I tested with the africa_small and a few others.
Thanks for the detailed descriptions to reproduce it - that will surely help I hope
The game loads, and the screen announcing the map and "Victory Conditions" shows up. You can move the map in the background and it renders fine with no errors or crashes with multiple graphics configurations. One the Start button is pressed it crashes after a couple of seconds.
Error: Received signal 11.
That's the actual issue we need to narrow down. If you run this on a recent version of openSUSE, systemd-crashhandler should have intercepted it and produced a coredump. You can cehck that with 'coredumpctl' - you should find ufoai there in the list of crashed tasks. If so, you can do: coredumpctl gdb PID (replace PID with the number found in the earlier coredumpctl command) at the (gdb) prompt, type "bt" (don't forget to hit enter) gdb MIGHT be asking you to install -debuginfo packages; follow the instructions given by gdb how to do it (you can copy the zypper command line produced) - then reproduce above steps, until no further debuginfo is missing. Then copy the output of "bt" in a text file and attach it here for review. -- You are receiving this mail because: You are on the CC list for the bug.