-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
min-ed-launcher crashes (or fails to start ED) with proton-cachyos #151
Comments
It looks like it's not recognizing you're running via Proton because the arg parsing looks for specific strings. The logic will need to change/be refactored. I'm unable to check myself at the moment, do you know if this version of proton requires something specific to run (OS settings, env vars, etc...) or should I be able to run it on a standard arch install? |
I'm not sure to be honest, that's well above my paygrade and unfortunately these days I have pretty bad cognitive and memory impairment. :/ Unfortunately we don't have a vanilla Arch install in the house any more although my spouse has CachyOS but with the vanilla Arch kernel and he also has this problem if he tries to use proton-cachyos. Best I can do is provide this info: https://wiki.cachyos.org/features/cachyos_settings/ and https://github.com/CachyOS/CachyOS-Settings for specifics. Sorry I can't be more helpful than that. :/ I can spin up a VM and try it with vanilla Arch if that would be helpful? EDIT: Or I can ask in the CachyOS forums? (Or both?) EDIT: Have posted to the CachyOS forums: https://discuss.cachyos.org/t/proton-cachyos-min-ed-launcher-cant-launch-elite-dangerous/5890 |
Hello, I am the maintainer of
This proton is meant to run on the host without a container normally, that's how we package it for CachyOS at least. There is also a version of it that is built with the Steam Linux Runtime (Sniper), so assuming that it is always not in a container is not the case. Normally, in recent versions, how a compatibility tool is supposed to run, i.e. which container to use, is controlled by the "manifest"
{
...
"require_tool_appid" "1628350"
...
}
If that field doesn't exist, the tool is run in Steam's already setup scout environment, in which Steam itself runs in. In I do not know if it would be workable for you to work a bit backwards and parse the information in Note: Steam has introduced a That's all I can think of right now, feel free to ping me with any questions. We are working on multiple runtime/compat_tool support on umu-launcher too and any information could help us make a better implementation there too, so this is generally of interest to me. |
Thanks for the in-depth response. Should be enough for me to get this fixed. Hopefully some time this week. |
This should be fixed. There was an issue when Steam first started using reaper that required convoluted arg manipulation that doesn't seem to be a problem anymore. That was a while ago though and I'm not sure if I'm forgetting some edge case. @ThornedRose Can you test the CI Build and let me know if it's fixed? |
@rfvgyhn I can confirm it now correctly launches all fine :) I tested with both a terminal (konsole) and without (just in case). My spouse (on CachyOS but using mainline Arch kernel instead) also tested and worked 100% fine for him too. Thanks heaps for your help! o7 Is there anywhere I can donate to the project? |
Thanks for reporting back. I don't have any donation services setup. Thanks for the offer though. |
Describe the bug/error
I recently switched from vanilla Arch Linux to CachyOS which provides a custom version of proton -
proton-cachyos
, in a similar vein to Glorious Eggroll'sproton-ge-custom
. However when using this version of Proton, min-ed-launcher fails, I'm not sure whether it's crashing or just stopping at some point and failing to continue.Loading Elite Dangerous with
proton-cachyos
but without min-ed-launcher (i.e. using the default Frontier launcher), ED runs just fine.I tried with Konsole (since I'm using KDE), Alacritty and terminal-less but the result is the same - I either have to run min-ed-launcher with a different version of Proton or run the game with
proton-cachyos
through the Frontier launcher.Debug log
Log after unsuccessfully launching with
proton-cachyos
:With proton-cachyos log
Log after successfully running the game with
proton-experimental
:With proton-experimental log
System details:
CPU: AMD Ryzen 5 5600X (12) @ 4.65 GHz
GPU: AMD Radeon RX 6800 XT [Discrete]
Display (G27Q): 2560x1440 @ 144 Hz in 27" [External, HDR]
Memory: 32 GiB
Swap: 32 GiB
OS: CachyOS x86_64
Kernel: Linux 6.13.0-2-cachyos
OpenGL: 4.6 (Compatibility Profile) Mesa 24.3.4-cachyos1.2
Vulkan: 1.3.296 - radv [Mesa 24.3.4-cachyos1.2]
Shell: fish 3.7.1
DE: KDE Plasma 6.2.5
WM: KWin (Wayland)
min-ed-launcher: 0.11.2
Steam: 1.0.0.81-4 (native) (CachyOS repo)
proton-cachyos: 1:9.0.20250117-1
python: 3.13.1-2, 3.11.11
python-semantic-version: 2.10.0-7
python-watchdog: 3.0.0-2
konsole: 24.12.1.-1.1
alacritty: 0.15.0-1.1
ED Odyssey: 4.0.0.1904
The text was updated successfully, but these errors were encountered: