Posted July 13, 2015
Hi,
I am experiencing crashes of Spacechem under Linux (Ubuntu 14.04 LTS). Running the game via start.sh from a terminal window results in the output below.
To explain the situation: The crashes seem to be a bit random. Sometimes I can play several levels before the game crashes and at other times the crash occurs as soon as I click into the window (I'm running Spacechem in windowed mode).
Has anybody else had similar crashes?
Thank you :)
Here's the terminal output:
Running Spacechem
Failed to open BO for returned DRI2 buffer (1024x768, dri2 back buffer, named 99).
This is likely a bug in the X Server that will lead to a crash soon.
Stacktrace:
at (wrapper managed-to-native) object.wrapper_native_0xf39bdd00 (int) <0xffffffff>
at Tao.OpenGl.Gl.glClear (int) <0x00018>
at #=qCEVmbqxlisYjT9VvcjIf2A==.#=qbS1jupdp5UGLeEIkRRvq6g== () <0x00c87>
at #=qfxVFOv8y83QVZWP$dPciyCYDhQ1534TA7alr25UUZoQ=.#=qwa9JlsZ8xPa9lEP0HTXGCw== (#=qCEVmbqxlisYjT9VvcjIf2A==) <0x00027>
at #=q9RvpkXA50$jg9YekHgA0N4noz_omAqQUJLXN3JuW6cg=.#=q_Zs2thSz3i1I2X$SiRjfRg== (string[]) <0x001d3>
at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>
at (wrapper managed-to-native) System.AppDomain.ExecuteAssembly (System.AppDomain,System.Reflection.Assembly,string[]) <0xffffffff>
at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly,string[]) <0x0002b>
at System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0x00027>
at (wrapper remoting-invoke-with-check) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at (wrapper xdomain-dispatch) System.AppDomain.ExecuteAssembly (object,byte[]&,byte[]&,string,string[]) <0xffffffff>
at (wrapper xdomain-invoke) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at (wrapper remoting-invoke-with-check) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at #=q9RvpkXA50$jg9YekHgA0N4noz_omAqQUJLXN3JuW6cg=.#=q_Zs2thSz3i1I2X$SiRjfRg== (string[]) <0x000cb>
at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>
Native stacktrace:
./mono() [0x80e16fc]
./mono() [0x81209fc]
./mono() [0x806094d]
[0xf776e420]
/usr/lib/i386-linux-gnu/dri/i965_dri.so(+0x39b72c) [0xf371172c]
/usr/lib/i386-linux-gnu/dri/i965_dri.so(+0x333d05) [0xf36a9d05]
/usr/lib/i386-linux-gnu/dri/i965_dri.so(+0x4108e) [0xf33b708e]
[0xf3a85dfc]
[0xf2127871]
[0xf50a0b68]
[0xf509f198]
[0xf50bd324]
[0xf50bd486]
./mono() [0x8064c2c]
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: Vorgang nicht zulässig.
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.
=================================================================
Aborted (core dumped)
I am experiencing crashes of Spacechem under Linux (Ubuntu 14.04 LTS). Running the game via start.sh from a terminal window results in the output below.
To explain the situation: The crashes seem to be a bit random. Sometimes I can play several levels before the game crashes and at other times the crash occurs as soon as I click into the window (I'm running Spacechem in windowed mode).
Has anybody else had similar crashes?
Thank you :)
Here's the terminal output:
Running Spacechem
Failed to open BO for returned DRI2 buffer (1024x768, dri2 back buffer, named 99).
This is likely a bug in the X Server that will lead to a crash soon.
Stacktrace:
at (wrapper managed-to-native) object.wrapper_native_0xf39bdd00 (int) <0xffffffff>
at Tao.OpenGl.Gl.glClear (int) <0x00018>
at #=qCEVmbqxlisYjT9VvcjIf2A==.#=qbS1jupdp5UGLeEIkRRvq6g== () <0x00c87>
at #=qfxVFOv8y83QVZWP$dPciyCYDhQ1534TA7alr25UUZoQ=.#=qwa9JlsZ8xPa9lEP0HTXGCw== (#=qCEVmbqxlisYjT9VvcjIf2A==) <0x00027>
at #=q9RvpkXA50$jg9YekHgA0N4noz_omAqQUJLXN3JuW6cg=.#=q_Zs2thSz3i1I2X$SiRjfRg== (string[]) <0x001d3>
at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>
at (wrapper managed-to-native) System.AppDomain.ExecuteAssembly (System.AppDomain,System.Reflection.Assembly,string[]) <0xffffffff>
at System.AppDomain.ExecuteAssemblyInternal (System.Reflection.Assembly,string[]) <0x0002b>
at System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0x00027>
at (wrapper remoting-invoke-with-check) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at (wrapper xdomain-dispatch) System.AppDomain.ExecuteAssembly (object,byte[]&,byte[]&,string,string[]) <0xffffffff>
at (wrapper xdomain-invoke) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at (wrapper remoting-invoke-with-check) System.AppDomain.ExecuteAssembly (string,System.Security.Policy.Evidence,string[]) <0xffffffff>
at #=q9RvpkXA50$jg9YekHgA0N4noz_omAqQUJLXN3JuW6cg=.#=q_Zs2thSz3i1I2X$SiRjfRg== (string[]) <0x000cb>
at (wrapper runtime-invoke) <Module>.runtime_invoke_int_object (object,intptr,intptr,intptr) <0xffffffff>
Native stacktrace:
./mono() [0x80e16fc]
./mono() [0x81209fc]
./mono() [0x806094d]
[0xf776e420]
/usr/lib/i386-linux-gnu/dri/i965_dri.so(+0x39b72c) [0xf371172c]
/usr/lib/i386-linux-gnu/dri/i965_dri.so(+0x333d05) [0xf36a9d05]
/usr/lib/i386-linux-gnu/dri/i965_dri.so(+0x4108e) [0xf33b708e]
[0xf3a85dfc]
[0xf2127871]
[0xf50a0b68]
[0xf509f198]
[0xf50bd324]
[0xf50bd486]
./mono() [0x8064c2c]
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: Vorgang nicht zulässig.
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.
=================================================================
Aborted (core dumped)
Post edited July 13, 2015 by JimPhelps
No posts in this topic were marked as the solution yet. If you can help, add your reply