Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Hi!

I'm having issues with the Linux version on Arch + DWM here is what appears on the console after running rad-reader-release:

» Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal read themes.toml
(WebKitWebProcess:371927): Gdk-WARNING **: 21:30:45.375: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.   
    (Details: serial 150 error_code 8 request_code 1 (core protocol) minor_code 0)   
    (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.)

After which I just get a grey screen.

However!

The windows version seems to work fine with Wine, which probably means it will also work on macOS.

I'll try to test it later and let you know.

Best,

BD

I'm getting something very similar on ubuntu


```

PS /usr/local/bin/rad-reader> .\rad-reader-release                              

Overriding existing handler for signal 10. Set JSC_SIGNAL_FOR_GC if you want WebKit to use a different signal

read themes.toml

(WebKitWebProcess:1008787): Gdk-ERROR **: 07:43:53.512: The program 'WebKitWebProcess' received an X Window System error.

This probably reflects a bug in the program.

The error was 'BadValue (integer parameter out of range for operation)'.

  (Details: serial 211 error_code 2 request_code 152 (GLX) minor_code 34)

  (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.)

```

Would love to have a fix as this has me dead in the water.