#Help.
1 messages ยท Page 1 of 1 (latest)
someone help me ๐ญ
it bascially launch. and just crash.
i installed olympus using
yay -S olympus
do i have to isntall the bin version?
are you installing everest while celeste is open
no
well the Celeste file is open
System.IO.IOException: Text file busy : '/home/ohhq/.local/share/Steam/steamapps/common/Celeste/Celeste'
at Interop.ThrowExceptionForIoErrno(ErrorInfo errorInfo, String path, Boolean isDirError)
alr
lemme retry
with closing steam all togehteher
its closed now
@thorn dragon here u go im showing u
also PLEASE ping me if u talk here :)
will be way more easier to notice
so i basically just launched olympus. it opened steam as it should i think idk. and asked if i wanted to launch celeste with custom parameters that olympus probably put
There are two types of logs; crash logs and log.txt.
Crash logs are generated when you see an "Oooops! :(" crash handler screen. They contain extra information which regular logs don't.
To access those, there's a button that says Open log file folder, which should take you to where they're stored. Make sure to grab the latest one!
For more subtle issues, non-crashing problems or other miscellaneous stuff, log.txt is checked. To find it, do the following:
- Open Olympus.
- Press the Manage button in the Installations panel on Olympus' main menu. (it's to the left)
- Press Browse to open the Celeste folder.
- Look for the file named exactly
log.txtinside that folder. Do not graberror_log.txtor look into theLogHistoryfolder as those are not thelog.txtyou're looking for.
Your username may sometimes show up in those logs. If you're concerned about that, remember to censor it before uploading. Every text editor should have a replace function, commonly opened with Ctrl+H.
what distro is this
arch linux
also read the message completely
i dont even see the "Ooooops :(" crash handler screen.
it just simply close
but it still runs in the background
read the message completely
okie
tl;dr run execstack -s /path/to/Celeste/binary, this is caused by glibc 2.41 executable stack restrictions
the "binary" being the executable?
/home/ohhq/.local/share/Steam/steamapps/common/Celeste/celeste
?
yes, with the capital C
okie
before you ask, execstack is provided by an aur package with the same name