I have a CentOS 7.9 system on which X2Go was previously working perfectly, but which is now broken. It broke after a typical yum update but I am not sure what changed to break things and I would like some help debugging and resolving this issue. I should mention that as part of my troubleshooting I have begun using NVIDIA kmod drivers from the ELRepo instead of ones installed from NVIDIA's .run file.
The behavior I'm seeing in every failed connection produces the following log entries. The system has both XFCE and MATE installed and both produce the same output.
Oct 19 10:21:29 c113256 /usr/bin/x2goruncommand: launching session with Xsession-x2go mechanism, using STARTUP="mate-session" Oct 19 10:21:29 c113256 /usr/bin/x2goruncommand: dbus wrapper available as /usr/bin/dbus-run-session Oct 19 10:21:30 c113256 kernel: resource sanity check: requesting [mem 0x000c0000-0x000fffff], which spans more than PCI Bus 0000:00 [mem 0x000c4000-0x000c7fff window] Oct 19 10:21:30 c113256 kernel: caller os_map_kernel_space.part.6+0x95/0xc0 [nvidia] mapping multiple BARs Oct 19 10:21:31 c113256 kernel: x2goagent[58376]: segfault at 48 ip 0000555fbee349ab sp 00007ffe380702a0 error 4 in nxagent[555fbecd6000+439000] Oct 19 10:21:31 c113256 abrt-hook-ccpp: Process 58376 (nxagent) of user 1001 killed by SIGSEGV - dumping core
Interestingly, x2goagent does not segfault if I have the X2Go client run /bin/xclock. The window opens without issue. /bin/firefox fails. /bin/glxgears also fails. Is this related to GL/GLX? How can I obtain more detailed information?
Thank you!
-- Eric Shell PBSci Technical Staff eshell@ucsc.edu 831 459 4919