<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Segfault in Xorg after RADEON(0): Failed to make 28944x66x32bpp GBM bo" href="https://bugs.freedesktop.org/show_bug.cgi?id=96396#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Segfault in Xorg after RADEON(0): Failed to make 28944x66x32bpp GBM bo" href="https://bugs.freedesktop.org/show_bug.cgi?id=96396">bug 96396</a> from <a class="email" href="mailto:darkdefende@gmail.com" title="Sebastian Parborg <darkdefende@gmail.com>"> Sebastian Parborg</a> <pre>(In reply to Michel Dänzer from <a href="show_bug.cgi?id=96396#c8">comment #8</a>) > (In reply to Magnus Holmgren from <a href="show_bug.cgi?id=96396#c7">comment #7</a>) > > [xcb] Unknown sequence number while processing queue > > [xcb] Most likely this is a multi-threaded client and XInitThreads has not > > been called > > This looks like a KSP bug. I think it's a bug with Unity (the game engine they are using). I have three other unity games that have the same problem. (Darkwood, Satellite Reign and wasteland2: directors cut) However Satellite Reign has a linux readme that states the following: > try command line option -force-opengl to force compatability with older > drivers, or -force-glcore for latest. With -force-opengl, Satellite Reign starts normaly. But with -force-glcore it exits (crashes ) with the xcb error. With Satellite Reign there is also a popup window where you can select the new unity3d opengl core render or the old that they state are for older GPUs and "safe". I've had this problem for quite a while now (over half a year with Darkwood as it were the first one to upgrade to the new unity3d version). If I read into the Satellite Reign comment, it seems like the new opengl core render probably works on Nvidia. I don't know if it works on AMDGPU-pro... I'm using a 290x with the radeon driver from git btw. So I would suspect that the opengl core render should work on that. Michel, maybe you can try to contact the unity3d guys and help them fix this problem? I'm guessing that if a actual developer of the linux drivers would contact them it would maybe be fixed sooner rather then later.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>