I have tried several times and several ways to run the GOG version of Kerbal Space Program on the Linuxulator. I have read the documentation several times and it feels like there are missing steps that are not in the documentation. I have tried the following: * Installed the entirety of the linux-c7 packages and attempted to run the app, and the binary seems to hang in the terminal window, but the graphics never appear, and I am unable to ctrl-c out of it. * Installed Ubuntu 20.04 in /compat/ubuntu, installed my username with the same UID/GID as my userid as on the FreeBSD side, and had the same behavior as with linux-c7. * Installed Debian Bullseye, then converted it to Devuan Chimaera (to eliminate the issue of systemd) in /compat/devuan, set up user in the same way as ubuntu above. Same result. I currently have /compat/linux (c7) and /compat/devuan. I also set up an ubuntu jail as well as a devuan jail. On both of those, I installed Kerbal in the jail, when I try to run glxgears or the KSP binary, I get: storm@brahms:/var/log$ glxgears X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 151 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 31 Current serial number in output stream: 32 I posted the jail issue to the forum, and apparently ssh X forwarding does not support 3d graphics through the tunnel. Can 3d graphics be run through the linuxulator? If so, how can I get kerbal tp run? The Linux box I am running it on currently has a mobile i7, 16GB of RAM and Intel graphics. My FreeBSD box has a full i7, 32GB of RAM and an nVidia GTX780Ti.
(In reply to storm16 from comment #0) That reads more like a support request than a bug report. > Installed the entirety of the linux-c7 packages and attempted to run the app, > and the binary seems to hang in the terminal window, but the graphics never > appear, and I am unable to ctrl-c out of it. That would be bug #253337.
Actually, no, as I have already posted to the FreeBSD forums. I just wanted to provide as much information as possible on what I had done in the hopes that there was some hidden something that I had missed. Since I am relatively new to FreeBSD, and I am a sysadmin and not a coder, I had hoped that the developers might run across something based on my bug, especially since it also affects something like glxgears.
(In reply to storm16 from comment #2) could you please ktrace/kdump it? i.e., ktrace -di /path/to/glxgears and then kdump -HAR -m 128 > glxgears.out and see where it fails