Modding, Mission Design, and Coding > FS2 Open Tools
PUBLIC BETA: Knossos 0.15.0-dev+73b131a (combined launcher/installer)
perihelion:
I'm not sure if I should post this here under Knossos or in the SCP build release board, but I am encountering the problem in Knossos 0.15.0... so I guess here makes as much sense as anywhere else.
It appears to me that I am unable to get Knossos to start FSO using any recent builds. At first I thought it was related to specific mods, but I can make the issue (partially) go away by switching to "stable builds only" under Knossos settings. Any mods that are configured to use specific older builds seem to run fine (there's a reason they were set to those older builds in the first place). Any mod that doesn't have an override is failing to start FSO unless I force Knossos to use the last stable build (which I have not updated in some time). The Nightlies and RC's I have updated just today.
When I say "will not run" I mean that Knossos says, "FSO is launching," but nothing happens after that. Not even a blip. No crash log, no error, nothing. I have seen this behavior with everything since nightly build 23.1.0-20230730.
Right, I should probably have mentioned earlier, I am running this on Linux Mint 20. Specs below. Any other Linux users notice anything weird happening with recent builds? I wish I had a clue.
--- Code: ---System: Kernel: 5.4.0-156-generic x86_64 bits: 64 compiler: gcc v: 9.4.0
Desktop: Cinnamon 4.6.7 wm: muffin dm: LightDM Distro: Linux Mint 20 Ulyana
base: Ubuntu 20.04 focal
Machine: Type: Desktop Mobo: Micro-Star model: B450 GAMING PLUS MAX (MS-7B86) v: 3.0
serial: <filter> UEFI [Legacy]: American Megatrends v: H.10 date: 07/22/2019
CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ rev: 2
L2 cache: 4096 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 102387
Speed: 1375 MHz min/max: 1550/3200 MHz Core speeds (MHz): 1: 1381 2: 1373 3: 1550
4: 1377 5: 1383 6: 1369 7: 1455 8: 1544 9: 1550 10: 1378 11: 1380 12: 1374 13: 1380
14: 1555 15: 1381 16: 1377
Graphics: Device-1: NVIDIA GM206 [GeForce GTX 950] vendor: eVga.com. driver: nvidia v: 470.199.02
bus ID: 29:00.0 chip ID: 10de:1402
Display: x11 server: X.Org 1.20.13 driver: nvidia
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 950/PCIe/SSE2 v: 4.6.0 NVIDIA 470.199.02
direct render: Yes
Audio: Device-1: NVIDIA GM206 High Definition Audio vendor: eVga.com. driver: snd_hda_intel
v: kernel bus ID: 29:00.1 chip ID: 10de:0fba
Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus ID: 2b:00.3 chip ID: 1022:1457
Device-3: Sunplus Innovation type: USB driver: snd-usb-audio,uvcvideo bus ID: 5-2.4:16
chip ID: 1bcf:2284
Sound Server: ALSA v: k5.4.0-156-generic
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel port: f000 bus ID: 22:00.0 chip ID: 10ec:8168
IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 2.30 TiB used: 459.06 GiB (19.5%)
ID-1: /dev/nvme0n1 vendor: A-Data model: SX8200PNP size: 953.87 GiB speed: 31.6 Gb/s
lanes: 4 serial: <filter>
ID-2: /dev/sda vendor: Hitachi model: HDS721050CLA362 size: 465.76 GiB speed: 3.0 Gb/s
serial: <filter>
ID-3: /dev/sdb vendor: Western Digital model: WD10EZEX-08WN4A0 size: 931.51 GiB
speed: 6.0 Gb/s serial: <filter>
Partition: ID-1: / size: 937.33 GiB used: 459.06 GiB (49.0%) fs: ext4 dev: /dev/nvme0n1p5
Sensors: System Temperatures: cpu: 38.0 C mobo: N/A gpu: nvidia temp: 46 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
1: deb https: //dl.winehq.org/wine-builds/ubuntu/ focal main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com ulyana main upstream import backport #id:linuxmint_main
2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Active apt repos in: /etc/apt/sources.list.d/starws-box-deadbeef-player-focal.list
1: deb http: //ppa.launchpad.net/starws-box/deadbeef-player/ubuntu focal main
Info: Processes: 345 Uptime: 2d 1h 07m Memory: 31.36 GiB used: 5.33 GiB (17.0%) Init: systemd
v: 245 runlevel: 5 Compilers: gcc: 9.4.0 alt: 9 Client: Unknown python3.8 client
inxi: 3.0.38
--- End code ---
perihelion:
I know everyone's busy, but has anyone else had problems with recent nightlies and SC builds failing to run from Knossos? I haven't heard anyone else complaining so I'm guessing this is a Linux thing. Older builds still launch and run like normal. But anything from late July onward just fails to launch without even an error message or any entry in the log that I can see, unless maybe there is some other log specific to Knossos I don't know how to find?
I'm sorry to double post, but I'm supposed to be helping someone debug a project he's working on, and I can't if I can't play it.
perihelion:
3rd post. Does anyone have ANY suggestions at all of what I can try short of uninstalling Knossos and trying to rebuild it from scratch?
I'm contemplating that step, but building Knossos in Linux isn't exactly easy for a non-programmer like me. I've managed to pull it off successfully a couple times despite myself, but it's nowhere near as easy installing something from a repository. Even if that's the only advise anyone could give me, I'd appreciate hearing it from someone more knowledgeable than me (which would be almost anyone on this forum!).
taylor:
--- Quote from: perihelion on August 19, 2023, 01:55:31 pm ---I know everyone's busy, but has anyone else had problems with recent nightlies and SC builds failing to run from Knossos? I haven't heard anyone else complaining so I'm guessing this is a Linux thing. Older builds still launch and run like normal. But anything from late July onward just fails to launch without even an error message or any entry in the log that I can see, unless maybe there is some other log specific to Knossos I don't know how to find?
--- End quote ---
Sorry for the late reply, but this is a known issue. It's not a knossos problem but an issue with the FSO linux builds. As best we can figure, in late July an update was released which gets applied to the GitHub ubuntu runner images and includes a newer version of gcc. This update causes one symbol to get forced to require gcc-12 or newer for any build to run. We've tried to fix it but I don't believe we've made any progress yet.
So simply installing gcc-12/g++-12, either yourself or through a distro upgrade, should fix it for you. For instance, upgrading to jammy (22.04 LTS) has been confirmed to get newer builds working again for others.
Goober5000:
There was a PR that attempted to fix this:
https://github.com/scp-fs2open/fs2open.github.com/pull/5580
It was merged on September 1 though, which means that if nightly builds after that date still don't work, we haven't found the root cause yet.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version