Posted December 27, 2018
Hi.
I've recently played Nantucket on my desktop system without issues. Today I installed in on my laptop and it crashed on startup.
Software wise both systems are almost identical, up-to-date Arch Linux.
On the hardware side my desktop has a AMD card from last year and two 1080p monitors while the laptop is from 2011 and has a Intel HD 3000 and a 1366x768 display.
Symptoms:
...
displaymanager : xrandr version warning. 1.5
client has 3 screens
displaymanager screen (0)(LVDS1): 1366 x 768
Using libudev for joystick management
Importing game controller configs
./start.sh: line 16: 5229 Aborted (core dumped) ./"Nantucket.x86_64"
$ less ~/.config/unity3d/Picaresque\ Studio/Nantucket/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.
Nantucket.x86_64: xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
...
Workaround:
LIBGL_DRI3_DISABLE=true ./start.sh
I found the workaround by searching around for the issue but didn't investigate the root of the issue.
Hope it helps someone.
I've recently played Nantucket on my desktop system without issues. Today I installed in on my laptop and it crashed on startup.
Software wise both systems are almost identical, up-to-date Arch Linux.
On the hardware side my desktop has a AMD card from last year and two 1080p monitors while the laptop is from 2011 and has a Intel HD 3000 and a 1366x768 display.
Symptoms:
...
displaymanager : xrandr version warning. 1.5
client has 3 screens
displaymanager screen (0)(LVDS1): 1366 x 768
Using libudev for joystick management
Importing game controller configs
./start.sh: line 16: 5229 Aborted (core dumped) ./"Nantucket.x86_64"
$ less ~/.config/unity3d/Picaresque\ Studio/Nantucket/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.
Nantucket.x86_64: xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
...
Workaround:
LIBGL_DRI3_DISABLE=true ./start.sh
I found the workaround by searching around for the issue but didn't investigate the root of the issue.
Hope it helps someone.