View Issue Details

IDProjectCategoryLast Update
0016770AI War 1 / ClassicCrash/ExceptionJun 5, 2015 6:57 pm
ReporterRadiant Phoenix Assigned To 
Status newResolutionopen 
Summary0016770: Crash on Launch
DescriptionI recently switched over to my other laptop and decided to install AI War there.

The zip files seemed to download and extract fine, but when I tried to launch the game, it immediately crashed without displaying anything on the screen.

CLI output:
~/.AI-War$ ./AIWarLinux.x86_64
Set current directory to ~/.AI-War
Found path: ~/.AI-War/AIWarLinux.x86_64
Mono path[0] = '~/.AI-War/AIWarLinux_Data/Managed'
Mono path[1] = '~/.AI-War/AIWarLinux_Data/Mono'
Mono config path = '~/.AI-War/AIWarLinux_Data/Mono/etc'
Aborted (core dumped)

(/home/USERNAME replaced with ~)

The same thing happens if I try the x86 version, and besides, I know this is a 64-bit Linux installation

Both this computer and my other computer (which AI War ran just fine on) use Xubuntu 12.04
TagsNo tags attached.
Internal Weight

Activities

Radiant Phoenix

May 18, 2015 8:02 pm

reporter   ~0040992

Forum thread: http://www.arcengames.com/forums/index.php?topic=17517

Radiant Phoenix

May 20, 2015 6:08 am

reporter  

Player.log (1,118 bytes)   
Stacktrace:


Native stacktrace:

	~/.AI-War/AIWarLinux_Data/Mono/x86_64/libmono.so(+0x92db2) [0x7f2205d7bdb2]
	~/.AI-War/AIWarLinux_Data/Mono/x86_64/libmono.so(+0xd0735) [0x7f2205db9735]
	/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0) [0x7f2207c22cb0]
	~/.AI-War/AIWarLinux.x86_64() [0xba7f02]
	~/.AI-War/AIWarLinux.x86_64() [0xb8a55d]
	~/.AI-War/AIWarLinux.x86_64() [0xb8da5b]
	~/.AI-War/AIWarLinux.x86_64() [0xbab1eb]
	/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed) [0x7f220715c76d]
	~/.AI-War/AIWarLinux.x86_64() [0x44b9b9]

Debug info from gdb:

Could not attach to process.  If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
ptrace: Operation not permitted.
No threads.

=================================================================
Got a SIGSEGV while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries 
used by your application.
=================================================================

Player.log (1,118 bytes)   

Radiant Phoenix

May 20, 2015 12:51 pm

reporter   ~0041013

I *think* there are two things going on here:
* Something is crashing.
* Ubuntu doesn't let processes ptrace each other just because they're by the same user, for security reasons.

Radiant Phoenix

May 25, 2015 3:10 pm

reporter   ~0041164

Some googling suggested I should use "ldd" to see what libraries were in use.

For some reason, the results were different.

This is the list from the working computer. Lines marked with an asterisk are not listed on the computer where AI War doesn't work:

 linux-vdso.so.1 => (0x00007ffcba3a7000)
 libGLU.so.1 => /usr/lib/x86_64-linux-gnu/libGLU.so.1 (0x00007f9771ee9000)
 libGL.so.1 => /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 (0x00007f9771c89000)
 libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007f9771953000)
 libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x00007f9771742000)
 libXcursor.so.1 => /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x00007f9771538000)
 libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f9771333000)
 libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f9771116000)
 librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f9770f0e000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9770c11000)
 libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f97709fb000)
 libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f977063d000)
 /lib64/ld-linux-x86-64.so.2 (0x00007f977217c000)
 libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f977033c000)
* libglapi.so.0 => /usr/lib/x86_64-linux-gnu/libglapi.so.0 (0x00007f9770117000)
* libXdamage.so.1 => /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x00007f976ff14000)
 libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x00007f976fd0d000)
* libX11-xcb.so.1 => /usr/lib/x86_64-linux-gnu/libX11-xcb.so.1 (0x00007f976fb0b000)
* libxcb-glx.so.0 => /usr/lib/x86_64-linux-gnu/libxcb-glx.so.0 (0x00007f976f8f4000)
 libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x00007f976f6d5000)
* libXxf86vm.so.1 => /usr/lib/x86_64-linux-gnu/libXxf86vm.so.1 (0x00007f976f4d0000)
 libdrm.so.2 => /usr/lib/x86_64-linux-gnu/libdrm.so.2 (0x00007f976f2c5000)
 libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x00007f976f0ba000)
 libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x00007f976eeb7000)
 libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 (0x00007f976ecb0000)

The packages appear to be installed on both computers, but one of them isn't somethingsomething.

Radiant Phoenix

May 25, 2015 3:35 pm

reporter   ~0041171

Aha! There is another difference that I didn't report, because I was checking manually and didn't notice:

The non-working computer is using /usr/lib/fglrx/Libgl.so.1 instead of /usr/lib/x86_64-linux-gnu/mesa/LibGL.so.1

Radiant Phoenix

May 25, 2015 3:43 pm

reporter   ~0041173

Some googling suggests this is the issue.

I will uninstall the fglrx and see what happens.

Radiant Phoenix

May 25, 2015 3:55 pm

reporter  

Radiant Phoenix

May 25, 2015 3:57 pm

reporter   ~0041176

That didn't immediately fix the problem, but I'm restarting the computer to see if things change.

Radiant Phoenix

May 25, 2015 3:59 pm

reporter   ~0041177

Restarting completed the fix

Radiant Phoenix

May 25, 2015 8:35 pm

reporter   ~0041188

Last edited: May 25, 2015 8:45 pm

Well, crap. Now I've got it again.

"intel_do_flush_locked failed: Input/output error"

EDIT: But this time there's a black flash.

Radiant Phoenix

May 25, 2015 8:36 pm

reporter  

Radiant Phoenix

May 25, 2015 8:43 pm

reporter   ~0041189

Trying this thing: http://wayback.archive.org/web/20141014201925/http://blogs.operationaldynamics.com/paul/opensource/wine-i915-or-i965-intel_do_flush_locked

Radiant Phoenix

May 25, 2015 8:49 pm

reporter   ~0041190

Last edited: May 25, 2015 8:50 pm

Adding those PPAs, updating, and rebooting seems to have made the problem go away, at least temporarily.

I did not change /etc/default/grub

Time will tell if this has really solved this stage of the problem.

Radiant Phoenix

Jun 5, 2015 6:57 pm

reporter   ~0041843

Well, I haven't had a problem since.

Issue History

Date Modified Username Field Change
May 18, 2015 7:27 pm Radiant Phoenix New Issue
May 18, 2015 8:02 pm Radiant Phoenix Note Added: 0040992
May 20, 2015 6:08 am Radiant Phoenix File Added: Player.log
May 20, 2015 12:51 pm Radiant Phoenix Note Added: 0041013
May 25, 2015 3:10 pm Radiant Phoenix Note Added: 0041164
May 25, 2015 3:35 pm Radiant Phoenix Note Added: 0041171
May 25, 2015 3:43 pm Radiant Phoenix Note Added: 0041173
May 25, 2015 3:55 pm Radiant Phoenix File Added: Player.log.20150525.1554-immediately_after_removing_FGLRX
May 25, 2015 3:57 pm Radiant Phoenix Note Added: 0041176
May 25, 2015 3:59 pm Radiant Phoenix Note Added: 0041177
May 25, 2015 8:35 pm Radiant Phoenix Note Added: 0041188
May 25, 2015 8:36 pm Radiant Phoenix File Added: Player.log.20150525.2036-newproblem
May 25, 2015 8:43 pm Radiant Phoenix Note Added: 0041189
May 25, 2015 8:45 pm Radiant Phoenix Note Edited: 0041188
May 25, 2015 8:49 pm Radiant Phoenix Note Added: 0041190
May 25, 2015 8:50 pm Radiant Phoenix Note Edited: 0041190
Jun 5, 2015 6:57 pm Radiant Phoenix Note Added: 0041843