Bug already logged and fixed upstream: http://bugs.openclonk.org/view.php?id=976 I can confirm the Debian patch fixes the issue. While one can epatch, it would be nicer to revbump to openclonk 5.4 which also contains the fix (for some reason upstream calls the release 4.0 instead of 5.4). Steps to reproduce: 1) Start openclonk 5.3.3 Result: Openclonk crashes with the following output: $ openclonk [12:57:30] Using XRandR version 1.4 [12:57:30] Command line: clonk [12:57:30] OpenClonk Beyond the Rocks Delta [12:57:30] Version: 5.3.3 [025] Delta linux-x86_64 (@C4REVISION@) (clonk:5404): Gdk-WARNING **: The program 'clonk' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRROutput (invalid Output parameter)'. (Details: serial 246 error_code 145 request_code 139 minor_code 9) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.)
Yeah, I wanted to version bump it anyway, but there were some problems with the repository. Will check it out.
seems gtk3 codepath is broken
dedicated build path as well
no interest in bumping so far, I will bump to 5.3.3-r1 instead
will close when it hits stable branch +*openclonk-5.3.3-r1 (06 Feb 2014) + + 06 Feb 2014; Julian Ospald <hasufell@gentoo.org> +openclonk-5.3.3-r1.ebuild, + +files/openclonk-5.3.3-xrandr-primary-output.patch: + revbump, fix crash bug wrt #500544
