Segfault with ficsit-cli
Hello, I'm segfaulting with ficsit cli on an Alma9 VM.
I am using the linux-amd64 (server is with x86_64)
13 Replies
🆙
I don't know if there is anything we can do about this directly, since it is probably a problem with a library?
@Mircea might have some troubleshooting ideas
are you able to change the VM configuration so that you can manage mods via ficsit-cli or SMM installed on another machine?
I could not reproduce it in an alma 9 docker container
And tbh I don't really know how go can segfault, any crash from go code would be a go panic, which is handled and printed by go
@Jay (pinging since I don't know your notification settings)
I tried to use SMM, but it seems to not be working properly, don't know why, as i didn't find any logs
Thanks, don't know why I didn't get any ping, as I asked discord to notify me for answer on this thread :sighh:
I tries the RPM and the binary 😦
Wdym by not working properly?
And the logs are going to be in
%localappdata%\SatisfactoryModManager, or ~/.cache/SatisfactoryModManager for linuxChanges made on my computer, where not seen on the server
will have a look tonight then!
So you could successfully add the server to SMM, but then mods weren't installed to it?
yeah, maybe it was conflicting with the fact I used ficsit-cli?
No, that shouldn't be an issue
Do you have multiple profiles in SMM?
will look in the logs then
If you do, make sure to select the server install in SMM and assign it to the profile you want it to use
yeah, I also leave the default one empty, and create a "moded" profile (but I did that with ficsit-cli on the server too)