Pcsx2 won’t launch
I installed PCSX2 via bazaar, and it loads for about it a second then closes itself. If I run it via terminal I get this error message:
qt.text.font.db: OpenType support missing for “Noto Sans”, script 11
Then it goes into an unhandled SIGSERV, which I can add on here if it’s helpful.
I tried installing the noto-sans-all font pack via rpm-ostree to see if that would help, with no luck.
As far as I can tell my installation of Bazzite is fully up to date.
Solution:Jump to solution
Summary and solution:
On Bazzite, the current stable release of PCSX2, v2.4.0, crashes if a Steam Controller is connected.
Solution: for now, either do not use a Steam Controller, or use a nightly version that is v2.5.200 or newer. Alternatively, you can turn off “Enable SDL Input Source” in Settings->Controller....
143 Replies
apps from bazar are flatoaks
so they should't have much to do with the system
it launches for me
rpm-ostree status if you can provide the output of that via terminals.
Also if it's a fresh install with no reboots yet.I can get that, yes; will shortly.
Its not a fresh install, but relatively new. I installed Bazzite early September
Now no gurantees we can get it to work. But also a suggestion is to uninstall and purge all the files for PSCX2 via warehouse (preinstalled) and reinstall it in case it developed an issue.
Oh of course! I appreciate any and all help 😊
Here’s the output. Apologies for it being a picture instead of a screengrab, much easier for me accessibility wise
It's a strange error though.
A missing noto sans font or not being able to use it is freaky and only screams install issue with the flatpak to me
Well packages are layered but it's up to date and I don't THINK either of those would make fonts go weird
i can almost guarantee we can get it working
simple test
I can remove those packages if its helpful for troubleshooting
Naw I don't think that'll cause it.
create a new user
install PCSX2 using that user
Okay, complete newbie question: how do I make a new user? This is my first time doing much of anything with Linux in a long, long time
I'd actually say try to purge and reinstall the flatpak, and ensure flatpaks are updated before a new user but I have to get back to work
Would purging it be any different than uninstalljng via bazaar or the flatpak terminal command? I have tried both so far
sudo useradd -m OTHER_USER_NAME
sudo passwd OTHER_USER_NAME
to set the password
now you can log inGotcha, thanks!
Flatpak tends to leave things behind when it uninstalls something in case you want to reinstall later. Think how Android has started doing it recently.
Warehouse lets you cleanup leftover files. It doesn't leave much, mind you, but sometimes the first step is a clean reinstall.
(of a flatpak)
Tried on the new user, same exact issue and error message if I run it in the terminal
Gotcha, I’ll go into warehouse and see about doing that
there is no data on a new user though
True but making and deleting a user seemed a bit much regardless. Not that it's too much extra.
Oh I meant on my main user account
so if it were a problem would not affect the user
Hm...
Also weh replace that nestopia with puNES.
puNES superiority.
could have been some random config somewhere
Fair point. It does seem font related.
Things I have now done here since we started talking:
I have made a new user and tried installing it there, with the same error message.
I have gone into warehouse and removed everything I could find labeled pcsx2
new user ensures it's clean
Regarding nes emulators, I’d prefer to be using mesen but haven’t figured out getting it running here. I’ll give puNES a try
puNES might seem a bit over the top but
It has a KICKASS crt filter shader.
Screen curve and all
Thats my preference reason for mesen so cool to know! Ill def check it out
try this as the other user
flatpak install flathub net.pcsx2.PCSX2 --user
preferably make sure it's removed by bazar
basically
by default flatpak by default has 2 "installations"
one per user & the other system wide
hoping that installing it per user helps isolate it further
from the systemGot it! I’ll give it a go
Hmm. It is giving me an error saying no remote ref found for flathub
oh yeah
you gotta add the remote for the user as well
Just did flatpak install flathub and installed it, if I put in the full command again it gives me the same error message. Does it need to restart?
strange
i get no error or any output really when launching it
& it launches
you add the remote like this
flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo --userAhh I see
Okay, that let me install pcsx2 via flathub, and the same error message upon running it:
oh
there seems to be a more interesting error at the bottom
one that mentions SDL input
The unhandled SIGSEGV? I thought the two were combined, not separate issues; I can provide the rest of the terminal output
Is it possibly disliking my steam controller?
It could but post the whole log here first.
That said Imma go lay down. Annoying workday.
That was it, wow.
possibly
Oof
Hopefully its just the setup process
Steam controllers are a weird beast...
Yeah it may have been trying to automap and panicking
As this works fine on the windows version of pcsx2, and I need to use it for accessibility purposes.
I appreciate the help from both of you! Totally understand the need to go lie down
Okay, turning it back on after I get through setup immediately crashes it :/
possible i guess
oh
dang
hmm
That said we DO have retroarch if you need a backup solution. I prefer the standalones, but retroarch is there for my weird stuff like wonderswan
maybe
Also I wonder what'd happen if you launched it via steam...
lainch it from Steam
Yeah add it to steam and try that. See if steam's controller mapping passes off to it
to let Steam do it's Steam input magic
This has happened to me with one other program using SDL, so it seems to be an SDL issue.
I’ll give that a go
Dang, same thing with launching via steam
Wonder if Retroarch will have an easier time...I think it has PCSX2 as a core.
I mean I hate using it myself but it's good for emergencies even if I prefer the raw emulator. Though I wonder if you can change the SDL options in PCSX2 while the controller is off
Perhaps turn settings off that may be reaching out to the controller in advance
Thats a good idea,I’ll take a look.
it dies have a core as i recall
At the moment ive been dual booting back into windows for pcsx2, so itd be nice to not need to anymore
The options are to try to get PCSX2 to behave. Or alternativelly utilizing retroarch. I usually don't like using it as the cores underperform compared to standalone, but it is PS2 we're talking about
PS2 is hardly difficult to emulate on PC hardware these days.
Even if I do prefer the standalones.
As said I use retroarch for weirdness or things that don't have standalones like say...wonderswan
wonder if non flatpak pcsx2 works fine
...Hmn
Wait
Flatpak permissions on PCSX2
Yeah, I prefer not retroarch as well, I prefer dedicated stuff if possible
Maybe it needs an additional device or input permission for the steam controller
And is segfaulting unable to get it despite seeing it
See if you can post the whole error here. Maybe it can be solved with permission finangling...
I turned off SDL Input Source in PCSX2 under controllers, and it didnt crash when I turned my steam controller back on, so thats a start!
Okay, let me go grab it
Here's hoping turning SDL off was all that was needed though. Definitely try it with SDL off. And we can fiddle deeper in permissions with the error if you wind up needing SDL
But here's hoping the SDL bit solved it and you can map the controller so we don't gotta
Alright, I’ll go get it setup and launch something to see if my inputs work
If you want to help pcsx2 out...
https://github.com/PCSX2/pcsx2/issues/13188
GitHub
[BUG] [CRASH]: Immediate application crash with controller. · Issu...
Describe the Bug When connecting my Steam Controller (with, or without Steam running), PCSX2 immediately crashes and will continue to crash on startup until I turn the controller off. Reproduction ...
Someone seems to have filled this exact issue and hasn't gotten back to the team yet but don't know if it's completely the same
....oh lol
They're also using bazzite so
Yeah
Can probably help pcsx2 fix it if you're so inclined
Oh cool! Yes absolutely, I will look into that
I’m a once programmer/modder now disabled gamer so helping with stuff like this is my jam
I'm sad the person filed it then went radio silent on them but hey they wrote the bug for you :P
you can actually downgrade the flatpak pretty far
Hah true!
& check each version up
if one of them works
that's good
Can help them pinpoint the problem starting point in the git bug
helps find when it broke
The other person already pinpointed app image does it to do you don't even have to worry about that part
yeah it's probably common to all variants
possibly not all versions though
For going back to older versions via flatpak, how would I go about doing so?
Went ahead and commentedon the issue tracker, with some extra information and that I’d try to track down the version update that caused it
exokained here https://docs.flathub.org/docs/for-users/downgrading
Downgrading | Flathub Documentation
It is possible to downgrade an installed application (or runtime) to an
As for where to start... The other user said it worked one or two months before and it's an August bug so our best start point is around... Early July late June.
Yeah, figured I would jump back a few months, find one that worked, then go forward half the updates and keep halving until I find it
Thanks Nagito! I’ll give that a try
not sure hiw far the flatpak lets you go back though
Given app image has the problem too you may be able to use those releases on their git as well
Nothing better than a bug with plenty of options
Indeed!
Not a huge array of build options on flathub, but can at least tell which version works as a starting point this way
also given that you mentioned SDL
you could try the arch distro package i think it has one
that should be built against recent/possibly the latest SDL
not only did you mention SDL
but SDL with a different game
Yeah, it was with severed chains, the legend of the dragoon remaster project
was it the same crash issue?
I don’t recall if I got the same error code exactly, but it also uses SDL and it also works on windows but not bazzite for me
if that isn't a flatpak/appimage you can try sticking it into Steam & using Steam Linux runtime as the compatibility layer
the runtime specifically contains a vendored version of SDL
because SDL issues aren't exactly un heard of
Ah interesting! Thanks for the heads up
And yeah, it’s not either of those. If I recall correctly it launches via a script
there were some SDL issues with the switch from 2 to 3
SDL3 does come with an SDL2 shim
but the shim isn't perfect
speaking of SDL
i recall that it handles all input for Wine/proton
& thus input for all Windows games on Linux
Hmm, if thats the case then maybe it’s a specific SDL version or config causing the issue? I have had most games just work fine so far
yeah that's my idea the specific SDL version breaks the Steam controller
or maybe PCSX2 interacts with it weirdly
I think its the specific SDL version. Done some testing, and the latest stable version is where it’s broken. An older stable version works, and the latest nightly version works, so somewhere in there it broke and then was fixed. Going to narrow it down for that PCSX2 bug listing on github.
Thank you to both of you for the assistance!
wouldb't say i'm done helping
we could check the SDL version in the flatpak i guess
in appimage i donno
So the flatpak version matches the latest stable version on their website, 2.4.0
flatpak does use SDL3
Narrowing it down! Somewhere between 2.5.204 and 2.5.178 it was fixed
should probably be backported whatever it is
Found it!
In 2.5.200 they updated to SDL 3.2.24. It doesn’t crash on this version. On 2.5.199 it does
Something that sped this up is they have tagged nightly builds with descriptors, so I could find the ones that modified SDL versions
Going to now find which nightly broke it in the first place
you can run the executable with
SDL_LOGGING=verbose
as an env varAlright, found the version where it starts crashing, and its when they updated to SDL 3
& that'll log more
yeeeeeeeah
kinda expected
SDL_LOGGING=verbose would have told you the SDL version anyways
but nice they tagged the releases
says this
Yeah, made it easy to find! Only
had to download 15 versions, which isn’t bad at all between the hundreds of nightlies it could have been
devs should have tested it extra hard
it is a new version of SDL after all
Somewhat agreed. Its hard when the device causing an issue is something not even in production anymore
I’m guessing a steamdeck doesn’t cause this issue. If I had one I’d test it
yeah Steam controllers ain't made anymore
a billion people use the deck for emulation
someone would have noticed
I used to work in audio programming for software and hardware, and there was this awesome research lab called the interoperability lab. They collect every bit of audio hardware they can and test if it can connect with each other, and report any errors they run into to the devs
Made me wish everything had something like that set up
wonder if SDL tells you what went wrong if you run it with verbose logging
also for this does remind me
i think i heard somewhere that SDL3 had issues with Steam controllers
Ah interesting!
Lets see, so an env var is something I add after the rest of the terminal command, right?
Been quite a while since I messed with them
env vars go before
args go after
shortest way would be
SDL_LOGGING=verbose net.pcsx2.PCSX2
for the flatpak
nice information to see it recognized & stuff but nothing jumps out as obviously wrong to me i'm not an SDL dev
Yeah, same here
Might be something occuring right after that step
Only possible thing is the serial being NONE instead of a number, as that feels like a constant its initialized to.
How would I run an appimage the same way via the terminal? I can compare to a version where it works
These two confuse me
"DISABLING HIDAPI"
"Hey lets use HIDAPI!"
Oh hah true! That is an excellent point
Here’s the verbose logging for the latest nightly
And yeah, this one doesn’t immediately disable HIDAPI
So the first disables, but immediately tries to use it. Second one manages to utilize it despite container
Sounds like a "todo" that exploded.
Yeah, or the wrong case for a switch statement or something similar
Some sort of cascade probably. This is a wild guess but maybe there's no log message before the sigsegv because it was an assumed success path
Quite possible! Or logging is set to something where verbose doesn’t trigger it, like DEBUG or something
Takes me back to writing code for AVB/TSN in 2012 😆😅
Looots of implementing giant switch states for IEEE specs
I'm just happy to see that neglected bug get attention. Nothing is worse than a full filing, nothing but good responses, then silence.
I can understand filing a bug, devs a dick, then silence. But that seemed more someone that gave up so they just stopped messaging
Which is a shame
Yeah :/. its equally as frustrating as a “nevermind, I fixed it” followup with no further clarification
Or the 500 unsolved questions in bazzite help that are solved. @.@
Just not marked as such
But no the "Nevermind I fixed it" is the WORST
Yeah, I can imagine!
For this one, should I make a write up in here that clearly states whats going on and then mark that as the solution?
As its easy to solve now that I know to just use a nightly release for now
...Shite so few people do a set as solved I forget how to do it.
never learned to do this on any Discord forum
never made a post myself
I almost want to @ someone to remember how to do it. Lemme check
i just lurk on a few & help people with stuff nobody else wants to
Here we go
So you can summarize the findings, right click and do the thingie
Got it!
Solution
Summary and solution:
On Bazzite, the current stable release of PCSX2, v2.4.0, crashes if a Steam Controller is connected.
Solution: for now, either do not use a Steam Controller, or use a nightly version that is v2.5.200 or newer. Alternatively, you can turn off “Enable SDL Input Source” in Settings->Controller.
❤️