Skip to content
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

Crash after launching any ISO on Fedora 34 #310

Closed
lararosekelley opened this issue Aug 18, 2021 · 5 comments
Closed

Crash after launching any ISO on Fedora 34 #310

lararosekelley opened this issue Aug 18, 2021 · 5 comments

Comments

@lararosekelley
Copy link

Issue tracker is ONLY used for reporting bugs. Please use our discord for support and/or feature requests.

Expected Behavior

  • Launching an ISO would open successfully

Current Behavior

After launch, I get a black screen, and then this C/C++ error:

terminate called after throwing an instance of 'std::invalid_argument'
  what():  stoi
Aborted (core dumped)

Steps to Reproduce

  1. Fresh Fedora 34 install
  2. Download Slippi AppImage
  3. Download the following modules to resolve Perl errors - perl-Net-DBus perl-X11-Protocol perl-Sys-Hostname
  4. Launch Slippi, then click "Play"

Environment

Fedora 34

@lararosekelley
Copy link
Author

Attaching core dump in case it is useful -

dolphin.zip

@lararosekelley
Copy link
Author

Seems like launching the ISO from standalone netplay works, but not from the Slippi launcher. Going to attempt building from source with additional logging, we have a theory on Discord that the parsing of the user.json file is busted somehow

@mitchhit234
Copy link

I was having the same issue just now, using Fedora 33 though, but the weird thing to me was that my other Fedora machine was running just fine. I went and checked each user.json file as you pointed out and it seems that the Slippi download process I just went through on the machine with the issue had generated a user.json file in a different format than my original user.json

I copied over that working user.json file to my machine and everything worked after that. If you don't have a good/bad user.json file to compare, here was each file's fields

Bad -
connectCode
playKey
uid

Good-
uid
displayName
playKey
conenctCode
latestVersion

Curious to see if this helps you with your issue!

@lararosekelley
Copy link
Author

That worked! Thank you so much @mitchhit234 - I will flag this in the Discord as well

@Hnasar
Copy link

Hnasar commented Nov 5, 2021

There's a new issue running on Fedora 35 but it with a workaround: #323

Perhaps this should just be closed because it's old.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants