This is probably related to OpenGL. The program uses some OpenGL call of a never OpenGL version than NX supports. Normally the application should check the provided version but this is not the first time that check is not (properly) done.
I suggest to try the x2go libglx workaround as described here: https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround
@Stefan: I think it is time to ship this lib and some wrapper script (as described on the wiki page) with x2go.
Uli
On Tue, Aug 25, 2020 at 10:16 AM richard lucassen <mailinglists@lucassen.org> wrote:
When starting "geeqie" (an image viewer) I get this in an x2go session on all 3 servers I run. Debian Bullseye (testing), sysV, Windowmaker as wm.
libx2go-config-perl 4.1.0.3-5 libx2go-log-perl 4.1.0.3-5 libx2go-server-db-perl 4.1.0.3-5 libx2go-server-perl 4.1.0.3-5 libx2go-utils-perl 4.1.0.3-5 x2goserver 4.1.0.3-5 x2goserver-common 4.1.0.3-5 x2goserver-x2goagent 4.1.0.3-5
(geeqie:27441): Gdk-ERROR **: 10:09:44.818: The program 'geeqie' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 300 error_code 16 request_code 143 (GLX) minor_code 1) (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.) Trace/breakpoint trap
Is this an x2go issue?
R.
-- richard lucassen http://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user