#Unable to install Everest

43 messages · Page 1 of 1 (latest)

foggy jungle
#

I figure the version of Celeste and the hardware I'm on will be important, so I'm on a Steam Deck running Bazzite and playing the Linux SDL3 beta version. I'll send the log file in a minute.

shut roost
#

everest does not support sdl3

#

at least at this time

foggy jungle
#

Ah. That makes sense.

#

All the other versions just randomly get unplayably choppy while I'm playing, so that's why I'm on that version specifically.

shut roost
#

there was some testing done to see what changes would everest need to support sdl3

#

@warm cipher

#

don't you have a fork

warm cipher
#

uhh i dont have binaries, i could make some real quick

warm cipher
#

warning, some mods may not function though

shut roost
#

if they do, the sdl3 changes are more likely to blame

warm cipher
foggy jungle
#

Following the manual installation instructions, it doesn't seem to work and the game just doesn't start. Maybe I just didn't do it right?

shut roost
#

close steam (no, completely exit steam) and run celeste from the terminal

#

and see what it spits out

#

also wdym doesnt work

#

does the installation succeed

warm cipher
#

also id install that onto a completely clean sdl3 game build, i dont think upgrading will be magically handled properly

foggy jungle
#

I did have Steam verify the file integrity to replace the modified ones, but maybe totally uninstalling and reinstalling is what I need. Everest did install properly according to the terminal but Celeste just doesn't start after that.

#

Somehow, I didn't think to try running Celeste itself from the terminal to see what it says. I'll try that in a bit.

shut roost
#

you do need to have steam completely closed when you do that

warm cipher
#

i didnt really fully test the build from the zip laugheline maybe theres some issue there, i will try it myself tomorrow though

foggy jungle
#

I completely closed out Steam and ran Celeste through the terminal, and this was the error log it created.

shut roost
#

lovely

wintry shoalBOT
#

System.ComponentModel.Win32Exception: SELinux execheap probe failed! Please ensure Everest has this permission, then try again

This occurs due to a permission error on Linux systems running SELinux, such as Fedora. To resolve this, use the following steps to allow Celeste to have the permissions it needs:

  1. Open a terminal window on the computer the crash happened on and run sudo cat /var/log/audit/audit.log | grep -a execheap | grep -a Celeste
    • This searches the SELinux logs for entries showing that it denied Celeste execheap, which is a permission that .NET needs to function properly.
  2. If you see an output like type=AVC msg=audit(1702580366.688:3126): avc: denied { execheap } for pid=353681 comm="Celeste" ..., then continue with these steps. If you get an error or no output, follow the instructions below to report the issue.
    • This output indicates that such entries exist in the logs, indicating that Celeste was indeed denied this permission.
  3. Run sudo cat /var/log/audit/audit.log | grep -a execheap | grep -a Celeste | sudo audit2allow -M everest_core_fix
    • This finds the same entries as before in the SELinux logs, and then creates a rule that tells SELinux to allow Celeste to have this permission.
  4. Run sudo semodule -i everest_core_fix.pp
    • This enables the rule that was created in the previous step, allowing Celeste to have the execheap permission.

After this Celeste should run without issue.
After following these steps, try launching Celeste again. If the issue is not resolved, please report this on Discord.

foggy jungle
#

I'll try that out after work and report back. Thank you for all the help so far.

foggy jungle
#

After following those instructions and launching Celeste, it'll show the Everest splash screen for a second saying it's launching the game and then just not do that. There's no log file or anything, but here's what it says in the terminal at that moment.

(03/25/2025 17:39:00) [Everest] [Info] [EverestSplash] Running splash on EverestSplash149428
(03/25/2025 17:39:00) [Everest] [Info] [EverestSplash] Font Renogare loaded
Controller 0: Steam Deck Controller, GUID: de280512, Mapping: 030079f6de280000ff11000001000000,Steam Virtual Gamepad,a:b0,b:b1,back:b6,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,dpup:h0.1,guide:b8,leftshoulder:b4,leftstick:b9,lefttrigger:a2,leftx:a0,lefty:a1,rightshoulder:b5,rightstick:b10,righttrigger:a5,rightx:a3,righty:a4,start:b7,x:b2,y:b3,platform:Linux,
03/25 17:39:00 minidumps folder is set to /tmp/dumps
03/25 17:39:00 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(20250311203919)/tid(149479)
03/25 17:39:00 Init: Installing breakpad exception handler for appid(gameoverlayui)/version(1.0)/tid(149479)
Game Recording - game stopped [gameid=504230]
Removing process 149438 for gameID 504230
Removing process 149437 for gameID 504230
Removing process 149428 for gameID 504230
Removing process 149420 for gameID 504230
Removing process 149259 for gameID 504230
Removing process 149257 for gameID 504230
Removing process 149252 for gameID 504230

(process:149479): GLib-GObject-CRITICAL **: 17:39:06.435: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
reaping pid: 149479 -- gameoverlayui```
#

Oh, that takes up way more space than I thought on mobile. Oops.

shut roost
#

@warm cipher

(process:149479): GLib-GObject-CRITICAL **: 17:39:06.435: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

#

this seems like something outside of celeste

warm cipher
#

steam is an absolute mess

#

theres also the whole

#

overaly shit

#

its not relevant

warm cipher
foggy jungle
#

I'll do that again and see if that file gets recreated.

#

After reinstalling Everest since I stupidly uninstalled it for some reason, it weirdly just doesn't show the splash screen at all now and instead complains about FNA being missing. I don't think there's a log file being made.

warm cipher
#

verify game files and reinstall everest i guess

foggy jungle
#

I reinstalled it from scratch again and it just works now, so problem solved, I guess?

shut roost
#

i doubt it

#

this'll probably be an intermittent issue just like that other user