On Wed, Apr 03, 2013 at 09:12:00PM +0200, Philipp Kern wrote: Hi. I'm chiming in since I experience exactly the same.
> what graphics driver do you use? Can you try »openclonk --nofullscreen«? X.Org X Server 1.12.4 [ 72.175] (II) intel(0): [DRI2] DRI driver: i965 $ openclonk --nofullscreen [11:12:47] Using XRandR version 1.3 [11:12:47] Command line: openclonk --nofullscreen openclonk: unrecognized option '--nofullscreen' [11:12:47] OpenClonk Beyond the Rocks Delta [11:12:47] Version: 5.3.3 [025] Delta linux-x86_64 (b78664b43cae) The program 'openclonk' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRROutput (invalid Output parameter)'. (Details: serial 264 error_code 167 request_code 150 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 --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) > It is *probably* more useful to directly contact the developers on [1] with as > much detail about your configuration as possible, but if that's not an option > I > can play man-in-the-middle for this. I confess that I'm in a "disengage brain" mood, and I rather not spoil it by engaging with yet another BTS. Ciao, Enrico -- GPG key: 4096R/E7AD5568 2009-05-08 Enrico Zini <enr...@enricozini.org>
signature.asc
Description: Digital signature
