Linux Support

[xrogaan]

I don't know why your system is more stable when running a dual GPU configuration. The "crash", though, is the driver stack failing. So anything that depends on it goes down when it dies. The cause may not be an overfull VRAM, check your logs! (And why is overdrive keeping you from sharing that information?)

Of course I can share the info, just not reporting as a bug to https://gitlab.freedesktop.org/drm/amd/-/issues because

Code: Select all

Dec 11 14:06:58 ulterno-desktop kernel: amdgpu: Overdrive is enabled, please disable it before reporting any bugs unrelated to overdrive.

Dude, that's a kernel notice. It's the kernel people telling you to not report bugs to them if overdrive is active. Overdrive allows overclocking, it may be a source of hardware instability and as such the would be kernel bugs are invalid.

And as you would have guessed from the command parameters, /sys/class/drm/card1/device/devcoredump/data is no longer available.
I will try that again next time I happen to remove the 2nd GPU.

The codedump is for the freedesktop/kernel people should you report a bug. We can't really do anything with it.

You should try to use the latest firmware and latest mesa, if you are not already. And then disable any kind of tweak you've done to your hardware, if any (including the custom fan speed). I'm sorry I can't help you more than that.

[ulterno]

The codedump is for the freedesktop/kernel people should you report a bug. We can't really do anything with it.

That is really the only "that information" that I haven't shared.

You should try to use the latest firmware and latest mesa, if you are not already. And then disable any kind of tweak you've done to your hardware, if any (including the custom fan speed). I'm sorry I can't help you more than that.

I understand. But I can't really consider running letting the zero-fan work at the moment, considering how hot it lets the GPU get and how expensive a new GPU would be in these times. (the RX 570 also stopped working yesterday, so this is the only one I have now)

[ninchuka]

I was having alot of crashes with error 123 with a different model/shader/whatever sometimes modded files other times vanilla, I am playing a game with interworlds hence why I havent been reporting it, but I tried switching to using proton GE-25 and I didnt have any crashes like I was having on native linux build I was constantly crashing after loading my lastest save which switching to proton fixed, so if anyone is having those crashes on linux, try that out

[rudi_pioneer]

I thought X4 was broken in gnome (fedora, Ubuntu, any), but comes out issue is that ventures download dialog isn’t visible and waiting that out gets the game going. Tried latest fedora, Ubuntu, silver blue, and bazzite

[xrogaan]

I thought X4 was broken in gnome (fedora, Ubuntu, any), but comes out issue is that ventures download dialog isn’t visible and waiting that out gets the game going. Tried latest fedora, Ubuntu, silver blue, and bazzite

That may be wayland's "feature" of preventing steal of focus. If it is too extreme, badly behaving software would be broken. Prompt appear behind the main windows. If there is an option, like KDE, try reducing the level at which focus stealing is enforced.

see: https://www.neowin.net/news/kde-plasma- ... r-wayland/

[Browser_ice]

I thought X4 was broken in gnome (fedora, Ubuntu, any), but comes out issue is that ventures download dialog isn’t visible and waiting that out gets the game going. Tried latest fedora, Ubuntu, silver blue, and bazzite

I have been playing X4 in Ubuntu 24.04 for at least one year without issues. I was on Windows 10 before.

I just looked at it and realize I never did override the ProtonDB compability. But works alright.

Game has been running for at least 6 hours today. Here are the monitor numbers for it:
CPU = 3.72%
CPU Time = 9:40:26
Memory = 13.5 GB (I have 32 GB)
Disk Read total = 3.3 GB
Disk Write total = 508.1 MB
Priority = normal

[ninchuka]

Game has been running for at least 6 hours today. Here are the monitor numbers for it:
CPU = 3.72%
CPU Time = 9:40:26
Memory = 13.5 GB (I have 32 GB)
Disk Read total = 3.3 GB
Disk Write total = 508.1 MB
Priority = normal

how is your x4 read and write so low after 6 hours after a couple or so (admittedly with interworlds so much bigger galaxy and more ship models) mine was at 66GB read and 800~MiB write but even with reemergence it was much higher then that if I remember correctly

[xrogaan]

I thought X4 was broken in gnome (fedora, Ubuntu, any), but comes out issue is that ventures download dialog isn’t visible and waiting that out gets the game going. Tried latest fedora, Ubuntu, silver blue, and bazzite

I have been playing X4 in Ubuntu 24.04 for at least one year without issues. I was on Windows 10 before.

I just looked at it and realize I never did override the ProtonDB compability. But works alright.

Game has been running for at least 6 hours today. Here are the monitor numbers for it:
CPU = 3.72%
CPU Time = 9:40:26
Memory = 13.5 GB (I have 32 GB)
Disk Read total = 3.3 GB
Disk Write total = 508.1 MB
Priority = normal

You don't need proton for X4, this game has a native version...

[ninchuka]

I thought X4 was broken in gnome (fedora, Ubuntu, any), but comes out issue is that ventures download dialog isn’t visible and waiting that out gets the game going. Tried latest fedora, Ubuntu, silver blue, and bazzite

I have been playing X4 in Ubuntu 24.04 for at least one year without issues. I was on Windows 10 before.

I just looked at it and realize I never did override the ProtonDB compability. But works alright.

Game has been running for at least 6 hours today. Here are the monitor numbers for it:
CPU = 3.72%
CPU Time = 9:40:26
Memory = 13.5 GB (I have 32 GB)
Disk Read total = 3.3 GB
Disk Write total = 508.1 MB
Priority = normal

You don't need proton for X4, this game has a native version...

it has a native version but I found the windows version way more stable for me for whatever reason

[rudi_pioneer]

Knowing about Wayland stealing focus saved my bacon -

In bazzite on framework desktop (not other PCs, nor other OSes) instead of random splash screen game never gets past initial splash screen. But running game with gamescope and force cursor fixes the issue.

It’s very niche issue. Aurora with flatpak steam doesn’t have this issue, for example

[alt3rn1ty]

Just migrated to Pop!_OS 24.04 LTS & Cosmic Desktop v1.0
Heroic Launcher installed, which in turn installed GOG Linux native X4 and all DLCs

I did not notice in the first post any mention about Ventures - But FYI my game saves copied across from Windows will not load, they need the ventures extension which is not installing.

Also previously on windows I have been enjoying Frame Generation with my NVidia 5070 ti - Linux Native X4 does not have the settings options to set it up.

Lastly another FYI - Game save location on this setup is home/.var/app/com.heroicgameslauncher.hgl/config/egosoft/X4

[rudi_pioneer]

Update: with KDE Plasma, running this with steam helps "SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 %command%" - i don't fully understand what it does, but issue is mostly gone!

[xrogaan]

Update: with KDE Plasma, running this with steam helps "SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 %command%" - i don't fully understand what it does, but issue is mostly gone!

Thanks, here's an explanation: https://wiki.libsdl.org/SDL3/SDL_HINT_V ... FOCUS_LOSS

For posterity:

Code: Select all

## SDL_HINT_VIDEO_MINIMIZE_ON_FOCUS_LOSS

A variable controlling whether fullscreen windows are minimized when they lose focus.

The variable can be set to the following values:

    "0": Fullscreen windows will not be minimized when they lose focus.
    "1": Fullscreen windows are minimized when they lose focus.
    "auto": Fullscreen windows are minimized when they lose focus if they use exclusive fullscreen modes, so the desktop video mode is restored. (default)

Note: the "_HINT" is specific to the C code, the environment variable doesn't contain it.

[EGO_Aut]

Pop!_OS 22.04 LTS -now i have time to get some experience
PC: Medion MS-7848 (1.0) - 4790/16GB/Vega56
VR: PICO4

Hallo Linux Community!
I want to connect my Pico4 VR with my "old" Linux PC.
What would you recommend to do, Pico does not support linux official, but i did read that it should work with ALVR or WiVRn Or is there another, better App out there?
Steam and BattlegroupVR is already installed to test it out....
Linux is new to me, please explain it to me as simply as possible, thank you.

Edit: Installed WiVrn Server, but i dont know how to install/find the client "WiVRn App" on my pico4

[xrogaan]

Pop!_OS 22.04 LTS -now i have time to get some experience
PC: Medion MS-7848 (1.0) - 4790/16GB/Vega56
VR: PICO4

Hallo Linux Community!
I want to connect my Pico4 VR with my "old" Linux PC.
What would you recommend to do, Pico does not support linux official, but i did read that it should work with ALVR or WiVRn Or is there another, better App out there?
Steam and BattlegroupVR is already installed to test it out....
Linux is new to me, please explain it to me as simply as possible, thank you.

Edit: Installed WiVrn Server, but i dont know how to install/find the client "WiVRn App" on my pico4

I'm not using VR at all. Did a succinct search on "PICO4 VR linux". Got this howto: https://github.com/suppressio/vr-pico4-steam-linux
Might help you moving forward, though it doesn't seem to be a "one click install" method.

[EmeraldFlint]

There's something to this, i'll investigate more. I'm also on wayland.

I've tried another linux machine (framework 13 with eGPU), this one with AMD Radeon RX 7600M XT, and same issue with video memory filling up and not releasing is happening.

So original thought about this being driver issue for new cards doesn't hold water, 7600M definitely isn't new.

I'm having the same issue with my AMD Radeon RX 6600. I'm on Manjaro with it's latest shipped Mesa drivers 21.3.1.

[brnw2]

Hello,
I need help with an error message that appears when running the X4 Foundation game program.
This is my first installation on the basic Linux version of Steam.
I tested with all versions of Proton and Linux running without success. The errors are different, but no simpler.
After verification, here is the error message:

/.steam/debian-installation/steamapps/common/X4 Foundations/testandlaunch: line 52: 16773 Segmentation fault (core dumped) ./${GAME} "$@"
Game Recording - game stopped [gameid=392160]

Thanks to whoever replies to me.

[EGO_Aut]

Hello,
I need help with an error message that appears when running the X4 Foundation game program.
This is my first installation on the basic Linux version of Steam.
I tested with all versions of Proton and Linux running without success. The errors are different, but no simpler.
After verification, here is the error message:

/.steam/debian-installation/steamapps/common/X4 Foundations/testandlaunch: line 52: 16773 Segmentation fault (core dumped) ./${GAME} "$@"
Game Recording - game stopped [gameid=392160]

Thanks to whoever replies to me.

What ChatGPT said"

Code: Select all

X4 Foundations (Egosoft) – Segmentation Fault on Startup (Linux / Steam)
The error message indicates a segmentation fault during game startup under Linux. This is a low-level memory access error and is almost always caused by driver, Vulkan, or runtime library issues, not by a corrupted savegame.
1. Most Common Causes on Linux
a) Graphics Driver / Vulkan (very common)
X4 Foundations requires Vulkan. A segmentation fault at launch usually means:
outdated or broken GPU drivers
missing or misconfigured Vulkan libraries
missing 32-bit Vulkan loader
Check Vulkan:
Code kopieren
Bash
vulkaninfo | less
If this fails or prints errors, Vulkan is not correctly installed.
Fix (depending on GPU):
NVIDIA: use the proprietary driver (not nouveau)
Code kopieren
Bash
nvidia-smi
must work.
AMD / Intel: install up-to-date mesa and Vulkan drivers.
b) Missing 32-bit Libraries (very common with Steam)
Even native Linux games often require 32-bit components.
On Debian / Ubuntu based systems:
Code kopieren
Bash
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install \
  libvulkan1 libvulkan1:i386 \
  mesa-vulkan-drivers mesa-vulkan-drivers:i386 \
  libgl1 libgl1:i386
c) Steam Runtime Conflicts
X4 often runs more reliably without the Steam runtime.
Test: Steam → X4 → Properties → Launch Options:
Code kopieren

STEAM_RUNTIME=0 %command%
For diagnostics only:
Code kopieren

PROTON_LOG=1 %command%
(The log will appear in your home directory.)
d) Corrupted Configuration Files
Broken settings files can cause an immediate crash.
Reset configuration:
Code kopieren
Bash
mv ~/.config/EgoSoft/X4 ~/.config/EgoSoft/X4.backup
Then start the game again.
e) Mods or Beta Versions
Disable all mods
Make sure no beta branch is selected
(Steam → Properties → Betas → “None”)
2. Check X4 Log Files (Important)
X4 creates its own logs, which are more useful than Steam’s output.
Code kopieren
Bash
~/.config/EgoSoft/X4/<SteamID>/logfile.txt
Look for messages such as:
Vulkan error
failed to create device
missing extension
libstdc++ / GLIBCXX errors
You can paste the last relevant lines here if needed.
3. Known Special Cases
Wayland: X4 is generally more stable under X11
→ log in using an Xorg session
Hybrid GPU systems (Intel + NVIDIA): Force NVIDIA:
Code kopieren
Bash
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
4. Recommended Troubleshooting Order
vulkaninfo runs without errors
Correct and up-to-date GPU driver installed
32-bit Vulkan and Mesa libraries installed
Steam runtime disabled
X4 configuration reset
No mods, no beta branch
5. If the Crash Persists
Please provide:
Linux distribution and version
GPU model
Driver version
Output of vulkaninfo | head -n 20
Last ~50 lines of logfile.txt
With that information, the root cause can usually be identified precisely.

[Rastuasi]

Hello,
I need help with an error message that appears when running the X4 Foundation game program.
This is my first installation on the basic Linux version of Steam.
I tested with all versions of Proton and Linux running without success. The errors are different, but no simpler.
After verification, here is the error message:

/.steam/debian-installation/steamapps/common/X4 Foundations/testandlaunch: line 52: 16773 Segmentation fault (core dumped) ./${GAME} "$@"
Game Recording - game stopped [gameid=392160]

Thanks to whoever replies to me.

What ChatGPT said"

Code: Select all

X4 Foundations (Egosoft) – Segmentation Fault on Startup (Linux / Steam)
The error message indicates a segmentation fault during game startup under Linux. This is a low-level memory access error and is almost always caused by driver, Vulkan, or runtime library issues, not by a corrupted savegame.
1. Most Common Causes on Linux
a) Graphics Driver / Vulkan (very common)
X4 Foundations requires Vulkan. A segmentation fault at launch usually means:
outdated or broken GPU drivers
missing or misconfigured Vulkan libraries
missing 32-bit Vulkan loader
Check Vulkan:
Code kopieren
Bash
vulkaninfo | less
If this fails or prints errors, Vulkan is not correctly installed.
Fix (depending on GPU):
NVIDIA: use the proprietary driver (not nouveau)
Code kopieren
Bash
nvidia-smi
must work.
AMD / Intel: install up-to-date mesa and Vulkan drivers.
b) Missing 32-bit Libraries (very common with Steam)
Even native Linux games often require 32-bit components.
On Debian / Ubuntu based systems:
Code kopieren
Bash
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install \
  libvulkan1 libvulkan1:i386 \
  mesa-vulkan-drivers mesa-vulkan-drivers:i386 \
  libgl1 libgl1:i386
c) Steam Runtime Conflicts
X4 often runs more reliably without the Steam runtime.
Test: Steam → X4 → Properties → Launch Options:
Code kopieren

STEAM_RUNTIME=0 %command%
For diagnostics only:
Code kopieren

PROTON_LOG=1 %command%
(The log will appear in your home directory.)
d) Corrupted Configuration Files
Broken settings files can cause an immediate crash.
Reset configuration:
Code kopieren
Bash
mv ~/.config/EgoSoft/X4 ~/.config/EgoSoft/X4.backup
Then start the game again.
e) Mods or Beta Versions
Disable all mods
Make sure no beta branch is selected
(Steam → Properties → Betas → “None”)
2. Check X4 Log Files (Important)
X4 creates its own logs, which are more useful than Steam’s output.
Code kopieren
Bash
~/.config/EgoSoft/X4/<SteamID>/logfile.txt
Look for messages such as:
Vulkan error
failed to create device
missing extension
libstdc++ / GLIBCXX errors
You can paste the last relevant lines here if needed.
3. Known Special Cases
Wayland: X4 is generally more stable under X11
→ log in using an Xorg session
Hybrid GPU systems (Intel + NVIDIA): Force NVIDIA:
Code kopieren
Bash
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia %command%
4. Recommended Troubleshooting Order
vulkaninfo runs without errors
Correct and up-to-date GPU driver installed
32-bit Vulkan and Mesa libraries installed
Steam runtime disabled
X4 configuration reset
No mods, no beta branch
5. If the Crash Persists
Please provide:
Linux distribution and version
GPU model
Driver version
Output of vulkaninfo | head -n 20
Last ~50 lines of logfile.txt
With that information, the root cause can usually be identified precisely.

ChatGPT has already been proven bad on these forums. 98% hallucinations when reading the logs

[EGO_Aut]

ChatGPT has already been proven bad on these forums. 98% hallucinations when reading the logs

Then please enlighten us with a solution.
In my opinion, ChatGPT can help quickly, and it has helped me many times, but that's not the topic here.