Posted July 17, 2017
high rated
Had problems starting Jotun after installing downloadable v2.2.0.4. A large window would appear and then close.
Solution was to pass parameter -force-opengl to Jotun executable. You can patch the start.sh script with this command (modify path to start.sh as needed at the end):
.../Jotun $ ./start.sh
Running Jotun
[snipped lines]
Importing game controller configs
support/gog_com.shlib: line 94: 5119 Aborted (core dumped) ./"${bin_64}"
$ less ~/.config/unity3d/Thunder\ Lotus\ Games/Jotun/Player.log
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
Jotun.x86_64: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Stacktrace:
Native stacktrace:
/home/user/bin/games/gog/Jotun/game/Jotun_Data/Mono/x86_64/libmono.so(+0x91772) [0x7faa97dee772]
/lib64/libpthread.so.0(+0x115b0) [0x7faa9ad0a5b0]
/lib64/libc.so.6(gsignal+0x9f) [0x7faa994d78df]
/lib64/libc.so.6(abort+0x16a) [0x7faa994d94da]
/lib64/libc.so.6(+0x2dd67) [0x7faa994cfd67]
/lib64/libc.so.6(+0x2de12) [0x7faa994cfe12]
/lib64/libX11.so.6(+0x4132a) [0x7faa9a56732a]
/lib64/libX11.so.6(+0x413db) [0x7faa9a5673db]
/lib64/libX11.so.6(_XEventsQueued+0x5d) [0x7faa9a5676cd]
/lib64/libX11.so.6(_XGetRequest+0x55) [0x7faa9a56a515]
/lib64/libX11.so.6(+0x4462f) [0x7faa9a56a62f]
/lib64/libX11.so.6(_XError+0x133) [0x7faa9a569df3]
/lib64/libGLX_mesa.so.0(+0x1cdb2) [0x7faa9605edb2]
/lib64/libGLX_mesa.so.0(+0x18e84) [0x7faa9605ae84]
/lib64/libGLX_mesa.so.0(+0x4a698) [0x7faa9608c698]
./Jotun.x86_64() [0xe9dfef]
./Jotun.x86_64() [0xe9ecd2]
./Jotun.x86_64() [0x465194]
/lib64/libc.so.6(__libc_start_main+0xf1) [0x7faa994c2401]
./Jotun.x86_64() [0x46e699]
Debug info from gdb:
I refuse to debug myself!
No threads.
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
[snipped lines]
XError: BadMatch (invalid parameter attributes) (error 8, opcode 151/34, serial 75, XID 0240000c, display 0x2a51b60
Solution was to pass parameter -force-opengl to Jotun executable. You can patch the start.sh script with this command (modify path to start.sh as needed at the end):
$ sed -Ei "s/execute_game(.+)$/execute_game_with_params\1 -force-opengl/" /path/to/installed/games/Jotun/start.sh
Here's the default behaviour: .../Jotun $ ./start.sh
Running Jotun
[snipped lines]
Importing game controller configs
support/gog_com.shlib: line 94: 5119 Aborted (core dumped) ./"${bin_64}"
$ less ~/.config/unity3d/Thunder\ Lotus\ Games/Jotun/Player.log
[xcb] Unknown sequence number while processing queue
[xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
[xcb] Aborting, sorry about that.
Jotun.x86_64: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Stacktrace:
Native stacktrace:
/home/user/bin/games/gog/Jotun/game/Jotun_Data/Mono/x86_64/libmono.so(+0x91772) [0x7faa97dee772]
/lib64/libpthread.so.0(+0x115b0) [0x7faa9ad0a5b0]
/lib64/libc.so.6(gsignal+0x9f) [0x7faa994d78df]
/lib64/libc.so.6(abort+0x16a) [0x7faa994d94da]
/lib64/libc.so.6(+0x2dd67) [0x7faa994cfd67]
/lib64/libc.so.6(+0x2de12) [0x7faa994cfe12]
/lib64/libX11.so.6(+0x4132a) [0x7faa9a56732a]
/lib64/libX11.so.6(+0x413db) [0x7faa9a5673db]
/lib64/libX11.so.6(_XEventsQueued+0x5d) [0x7faa9a5676cd]
/lib64/libX11.so.6(_XGetRequest+0x55) [0x7faa9a56a515]
/lib64/libX11.so.6(+0x4462f) [0x7faa9a56a62f]
/lib64/libX11.so.6(_XError+0x133) [0x7faa9a569df3]
/lib64/libGLX_mesa.so.0(+0x1cdb2) [0x7faa9605edb2]
/lib64/libGLX_mesa.so.0(+0x18e84) [0x7faa9605ae84]
/lib64/libGLX_mesa.so.0(+0x4a698) [0x7faa9608c698]
./Jotun.x86_64() [0xe9dfef]
./Jotun.x86_64() [0xe9ecd2]
./Jotun.x86_64() [0x465194]
/lib64/libc.so.6(__libc_start_main+0xf1) [0x7faa994c2401]
./Jotun.x86_64() [0x46e699]
Debug info from gdb:
I refuse to debug myself!
No threads.
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
[snipped lines]
XError: BadMatch (invalid parameter attributes) (error 8, opcode 151/34, serial 75, XID 0240000c, display 0x2a51b60
Post edited July 17, 2017 by bartmanus