I'm trying to install the latest Everest but unfortunately it seems the game won't start from Steam after installing it- when I click the button, it starts launching and then immediately closes. I was on the stable version a while ago, and it was able to launch from there then. Launching from Olympus isn't working, but it wasn't working earlier either since I'm on the flatpak version of steam. I'm on Arch Linux, and my .NET install comes from the official repository. I've added my log-sharp here, but I don't think the game is logging anything before it closes. Help would be appreciated!
#Issue with installing Everest 4248
152 messages · Page 1 of 1 (latest)
send your log.txt from the celeste installation folder
actually hold on
Starting Celeste process: /home/jasmine/.var/app/com.valvesoftware.Steam/.local/share/Steam/steamapps/common/Celeste/Celeste (without args)
sh: line 1: /home/jasmine/.steam/root/steam.sh: No such file or directory
i'm not familiar with steam inxalls on linux but this shouldn't be happening
yeah i have the flatpak install so i don't have a .steam
but i was told it was fine since launching from steam would launch everest anyway, and that worked on the stable version
hmm
the log.txt has a modification date of before i installed the latest version so i don't think it's useful
@twilit drift @ivory falcon you two worked on the flatpak install right
more like @ Atom, im clueless on flatpak specific stuff
but they have steam on flatpak, not olympus, idk how supported is that
if i had to guess they should use olympus on flatpak because iirc that one has fixes for launching steam on flatpak too
yeah I can try that
dunno if olympus flatpak is public yet tho
yeah i have the flatpak install so i don't have a .steam
i interpreted that as an olympus flatpak

@twin wave does olympus support steam from flatpak?
(omfg they should really allow us to react to messages on #953393160464269402 its so annoying)
anyways 
become modding helper 
well not yet 
true imo imo @ celestecord_mods make me a modding helper pweaseeeee 
could you try xdg-open steam://run/504230 after installing everest and clicking the big everest button (even if it doesnt launch it) ?
yeah, i have everest installed already so would I just run that then?
Yup, it may work
ah, big everest button
It shouldn't launch your game but after this you may try xdg-open steam://run/504230
i see this
it doesn't launch steam (and celeste) ?
I tried closing steam first and uh, I see this
which is odd because I do have the .NET runtime installed
oh, that would probably do it, wouldn't it
let me check the name
maybe you should add the net runtime flatpak as a dependency to olympus flatpak, if its not too heavy @twilit drift
btw did you update, your steam flatpak ? you should be on 23.08 instead of 22.08
Could you try flatpak install org.freedesktop.Sdk.Extension.dotnet7/x86_64/23.08 after this and see if it works
The NET runtimes adds 226 Mbytes of download, I don't know if it should be the default
yeah that what i thought
net is choooonk
then forget it or maybe patch olympus to auto download it if you wanna go fancy
But if after this it works we may update the wiki to explain how to get modded celeste working on flatpak (+ maybe custom prompt on Olympus if the flatpak path is detected
)
I wouldn't like if a program escaped the flatpak sandbox to install a flatpak package 😆 (However we could theorically do it since we already have the flatpak-wrapper.sh)
I think putting a copy pasta on how to do it may do the trick
just run make it install it on a flatpak too
popax already hinted me the pains of core with the net runtime, i'll have to implement installing it on olympus.fna for everest core builds on ubuntu 0_0
Yup but that would require running it inside the steam flatpak since olympus flatpak only have access to its files + home dir (except .var directory)
oh i mean just do flatpak install ... in olympus code
Well it wouldn't work since flatpak install is a host command
dang
However the flatpak-wrapper.sh transform the command into flatpak-spawn --host flatpak install NET.whatever which make it run as a host command but also make it escape the sandbox (a bit like what we did before when launching celeste or such)
so that i think is the easiest,
but not the cleanest since the user has no control over anything
yup, no perfect solutions
I don't think saying to paste a command would be too much actually, we're on linux and it's a pretty easy command
just tried this (after updating all packages), and no dice :(
I still get the same error
Damn
I may have an idea but it would require extensive testing I may do it on my own flatpak installation and keep you updated
You're welcome, I'm sorry that we couldn't make it work directly tho
for what it's worth, i managed to get it "working" by installing a portable non-flatpak version of steam
not a great solution, but at least it launches now haha
Oh amazing ! I will soon publish the Olympus flatpak and I may take a look to the steam flatpak to make it work
that would be awesome!
@abstract slate If you have Flatseal could you try setting up those two environments variable ?
PATH=/app/bin:/usr/bin:/usr/lib/sdk/dotnet7/bin
DOTNET_ROOT=/usr/lib/sdk/dotnet7
or using the following command but I would recommand Flatseal to tinker with flatpaks it's usually easier flatpak override --env VARIABLE=VALUE com.visualstudio.code
thanks ! P.S: feel free to ping me when you tested
@twilit drift just tested, still the same error :(
@ivory falcon just thought of it isn’t Everest looking for mono under linux ?
no
it uses this thing https://github.com/flibitijibibo/MonoKickstart
basically a bundled mono
so no worries about that
Hmm why would it search for dotnet then
So it uses dotnet ?
yeah
Oh so the latest stable would work indeed ?
iirc it uses the runtime dependent setup instead of the standalone one
it should
Because I’m pretty sure I don’t have dotnet on my computer
Damn
@abstract slate Could you try installing the latest stable Everest version instead ?
run dotnet --list-runtimes to see
yeah stable everest works for me
On flatpak ?
That will probably be an issue once it hits stable
on windows the os itself handles informing the user, on linux it prints to stdout a message i think?
Depends if you launch it through the shortcut probably just crash in front of you (or doesn’t start)
yeah it will look like it doesn't launch, so probably that is the launcher's task to make sure the user is informed
I still wonder why it doesn’t work inside the steam flatpak with the dotnet extension
Because I verified from a shell inside my Olympus flatpak and dotnet binaries are accessible (without some magic trick)
ltrace it to see where tries to find the .net runtime
So it should be ltrace xdg-open steam://run/504230
Either that or directly from the flatpak shell ltrace /to/celeste/bin
the latter
don't think xdg-open will launch celeste as its child so ltrace will just stop when xdg does
Yea you’re right
Yea unknown command on my end
this is going to cause issues on the steam deck 
Just thought of something too on flatpak, could you try adding this env ?
in the steam launch command for celeste LD_LIBRARY_PATH=/usr/lib/sdk/dotnet7/lib %command%
hopefully doesn't override anything | because according to https://github.com/flathub/org.freedesktop.Sdk.Extension.dotnet7 it may be needed
just tested and it doesn't work
@ivory falcon
not sure why it doesn't find the .NET runtime
Hehe 
well pretty hacky Idk how to make it run on steam now 
but it's already some progression
does that mean you managed to make it work? with the LD_LIBRARY_PATH env var?
on my system, runtimes are listed under /usr/share/dotnet/... not in /usr/lib/... maybe thats the issue?
Yup ! I was helped because there’s an enable.sh which exports 3 env variables, PATH, DOTNET_ROOT and LD_LIBRARY_PATH
This did the trick to run miniinstaller inside the Olympus flatpak but I couldn’t make it work with the same strategy inside the steam flatpak 🥲
cool! does that mean you can release it now?
The Olympus flatpak ?
yeah
The Olympus flatpak is pretty much ready for normal use like Everest stable and beta, with loenn working (might try ahorn later on)
For the core since it needs another runtime + adding env var I might do a PR to make it compatible later
oh i see, cool
Since I can’t make core work on steam flatpak now it’s a bit weird since you would need system wide + dotnet7 flatpak because the installation process would work from the flatpak but not from the system-wide if core runtime isn’t there
oh yeah i see
An end goal could be to be able to run a non drm Celeste game directly inside the flatpak maybe - would totally erase the issue of runtimes libs and such
Because for steam deck users once core goes stable there will be no possibility for them to play modded Celeste
A workaround would be to disable the read only file system and install dotnet but the installation would vanish after the next steam update 
yeah that would be kind of a pain
atleast they would still have the option of manually installing olympus
Yup
- maybe the Everest team will keep a « legacy » version which doesn’t require core (but logically with no more support and less features)
Stable versions never expire ^^'
Yup but core will hit stable and it may be great to have the latest non core stable labeled as something else
yeah, and you have to make sure that your everest versions yaml always keeps at least one legacy version on it
oh, since it only went down to 3000 (not to something like 100) i assumed the too old ones dont show up there
Btw what are the new features of the core version ? + the diff between XNA and FNA, I’m kinda new to the Celeste modding community so everyone talk about it in dev but I don’t know the advantages and the diff
I only know that dotnet is now required
Stables come from GitHub releases, but those weren't a thing for quite a while 
Stables used to come from Azure like the rest