Bug Unity crashes when I change workspace

Hello
I'm using Unity(1:5.6.0f3+20170331-1) which I installed using pamac on my Manjaro system(I'm using it with Openbox).

My issue is very simple: Every time I change the workspace while unity is running, it freezes and then closes automatically after a minute. No error messages are displayed.

Here are the last lines of my Editor.log file just after one of these crashes:

Spoiler

Code (CSharp):

1. requesting resize 857 x 309
2. resizing window to 857 x 309
3. Desktop is 1366 x 768 @ 60 Hz
4. requesting resize 855 x 309
5. resizing window to 855 x 309
6. Desktop is 1366 x 768 @ 60 Hz
7. requesting resize 855 x 309
8. resizing window to 855 x 309
9. Desktop is 1366 x 768 @ 60 Hz
10. requesting resize 855 x 296
11. resizing window to 855 x 296
12. Desktop is 1366 x 768 @ 60 Hz
13. requesting resize 853 x 296
14. resizing window to 853 x 296
15. Desktop is 1366 x 768 @ 60 Hz
16. Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.013108 seconds (Nothing changed)
17. Issue TrimJob to reduce GI Cache size to maximum 10GB at: '/home/jefferson/.cache/unity3d/GiCache'
18. [00:00:00] Enlighten: Precompute started.
19. Launched and connected shader compiler UnityShaderCompiler after 0.09 seconds
20. UPID Received 'fcbdfec2-cfec-470c-b0da-8fb029703066'.
21. TrimDiskCacheJob: Current cache size 0mb
22. [00:00:05] Enlighten: Finished 1 Layout Systems job (0.00s execute, 0.00s integrate, 4.57s wallclock)
23. [PathTracer][LP] Issuing deduplication and tetrahedralization job. Combined: 80257199cfa681a16be5e09b3c2208f4, tetrahedralized probes: 00000000000000000000000000000000, non-tetrahedralized probes: 00000000000000000000000000000000, dependencies: 00000000000000000000000000000000
24. Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.006791 seconds (Nothing changed)
25. [00:00:05] Enlighten: Finished 1 Tetrahedralize Probes job (0.00s execute, 0.00s integrate, 0.39s wallclock)
26. [00:00:05] Enlighten: Precompute took 4.963386 seconds.
27. Enlighten scene contents:   0 geometries.   0 instances.   0 systems.   0 probe groups.   0 cube maps. Scene is up-to-date.
28. [00:00:05] Enlighten: Bake started.
29. [PathTracer][LP] Integrating deduplicated and tetrahedralized probes for hash 80257199cfa681a16be5e09b3c2208f4.
30. Setting up 2 worker threads for Enlighten.
31.   Thread -> id: 7f6beeee5700 -> priority: 1
32.   Thread -> id: 7f6bee6e4700 -> priority: 1
33. [00:00:08] Enlighten: Finished 1 Bake Runtime job (0.33s execute, 0.00s integrate, 2.68s wallclock)
34. [00:00:08] Enlighten: Bake took 2.683597 seconds.
35. Refresh: detecting if any assets need to be imported or removed ... Refresh: elapses 0.007895 seconds (Nothing changed)
36. [PathTracer] Lightmap reset.
37. [PathTracer][LP] Light probes reset.
38. [PathTracer] building lightmap data asset.
39. [00:00:09] Enlighten: Reflection Probes started.
40. [00:00:09] Enlighten: Finished 1 Ambient Probes job (0.00s execute, 0.00s integrate, 0.05s wallclock)
41. [00:00:09] Enlighten: Finished 1 Reflection Probes job (0.04s execute, 0.00s integrate, 0.06s wallclock)
42. [xcb] Unknown sequence number while processing queue
43. [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called
44. [xcb] Aborting, sorry about that.
45. Unity: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
46. /home/builduser/buildslave/unity/build/Editor/Platform/Linux/UsbDevices.cpp:UsbDevicesQuery
47. Stacktrace:
48.  
49.  
50. Native stacktrace:
51.  
52.    /opt/Unity/Editor/Data/MonoEmbedRuntime/libmono.so(+0x91be1) [0x7f6c54cdabe1]
53.    /usr/lib/libpthread.so.0(+0x11fdf) [0x7f6c68565fdf]
54.    /usr/lib/libc.so.6(gsignal+0x110) [0x7f6c5fef1a10]
55.    /usr/lib/libc.so.6(abort+0x179) [0x7f6c5fef3139]
56.    /usr/lib/libc.so.6(+0x2c606) [0x7f6c5feea606]
57.    /usr/lib/libc.so.6(__assert_fail+0x41) [0x7f6c5feea6b1]
58.    /usr/lib/libX11.so.6(+0x41c39) [0x7f6c68dcdc39]
59.    /usr/lib/libX11.so.6(+0x41cea) [0x7f6c68dcdcea]
60.    /usr/lib/libX11.so.6(_XEventsQueued+0x5c) [0x7f6c68dcdfdc]
61.    /usr/lib/libX11.so.6(_XGetRequest+0x54) [0x7f6c68dd0e24]
62.    /usr/lib/libX11.so.6(+0x44f3e) [0x7f6c68dd0f3e]
63.    /usr/lib/libX11.so.6(_XError+0x132) [0x7f6c68dd0702]
64.    /usr/lib/libGLX_mesa.so.0(+0x1d331) [0x7f6c52865331]
65.    /usr/lib/libGLX_mesa.so.0(+0x19403) [0x7f6c52861403]
66.    /usr/lib/libGLX_mesa.so.0(+0x4ac07) [0x7f6c52892c07]
67.    /opt/Unity/Editor/Unity() [0x1966b1f]
68.    /opt/Unity/Editor/Unity() [0x254280c]
69.    /opt/Unity/Editor/Unity() [0x2542abb]
70.    /opt/Unity/Editor/Unity() [0x2572a38]
71.    /opt/Unity/Editor/Unity() [0x2572a81]
72.    /opt/Unity/Editor/Unity() [0x1952e19]
73.    /opt/Unity/Editor/Unity() [0x1955b9a]
74.    /usr/lib/libgtk-x11-2.0.so.0(+0x1307ab) [0x7f6c6aa6b7ab]
75.    /usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x144) [0x7f6c69e88f74]
76.    /usr/lib/libgobject-2.0.so.0(+0x21f81) [0x7f6c69e9af81]
77.    /usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x8de) [0x7f6c69ea366e]
78.    /usr/lib/libgobject-2.0.so.0(g_signal_emit+0x8e) [0x7f6c69ea3fae]
79.    /usr/lib/libgtk-x11-2.0.so.0(+0x2488cb) [0x7f6c6ab838cb]
80.    /usr/lib/libgtk-x11-2.0.so.0(gtk_main_do_event+0x4a2) [0x7f6c6aa6a502]
81.    /usr/lib/libgdk-x11-2.0.so.0(+0x5b46b) [0x7f6c6a6e146b]
82.    /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x2a6) [0x7f6c699a85a6]
83.    /usr/lib/libglib-2.0.so.0(+0x4a80f) [0x7f6c699a880f]
84.    /usr/lib/libglib-2.0.so.0(g_main_loop_run+0xc1) [0x7f6c699a8b31]
85.    /usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb6) [0x7f6c6aa693a6]
86.    /opt/Unity/Editor/Unity() [0x4c0bde]
87.    /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f6c5fede510]
88.    /opt/Unity/Editor/Unity() [0x4db418]
89.  
90. Debug info from gdb:
91.  
92. Fatal error: No such file or directory
93.  
94. =================================================================
95. Got a SIGABRT while executing native code. This usually indicates
96. a fatal error in the mono runtime or one of the native libraries
97. used by your application.
98. =================================================================
99.  
100.  

Thanks.

 

So... anything? anyone?

 

Similar thing happens on Ubuntu with LXDE.

 

These xcb messages preceding the crash seem to be related to a driver issue on some systems.