-
-
Notifications
You must be signed in to change notification settings - Fork 255
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
[Bug]: Crash on launching flatpak #3216
Comments
I've had a chance to try and reproduce this error today in relation to #3213 but I haven't come across it. Bottles launched normally both from the CLI and GUI. Apart from the problem in the above mentioned issue, there didn't seem to be any issues with Bottles on my Silverblue setup. Could there be something you configured in your system that causes this error? |
Unfortunately I don't know enough about Flatpak to tell if that is the case. I've digged up some more info from Warehouse. Is there anything out of the ordinary here? |
From #3213:
For the record, I only installed Bottles from GNOME Software (with Flathub as the only flatpak remote), and didn't do anything after that. After I ran into the crash, I tried removing/instaling the program a bunch of times. I also reinstalled after using the "cleanup" function in Warehouse, and still get the same error. |
I get this error too. #3218 (comment) I usually use Pamac to install/update Flatpak apps, but I had run |
I just downgraded to 51.9 using Warehouse and now Bottles is working. If you are already using 51.9 and getting the error, maybe you could try downgrading to 51.8? Worth a shot. |
Downgrading did not solve the problem. I also tried I installed the AUR version (which builds it from the source code), and that version worked. |
"There's more than one way to skin a cat" springs to mind. Well done. |
Cannot replicate. |
Describe the bug
The program crashes and refuses to launch, when running the flatpak.
To Reproduce
Package
Flatpak from Flathub
Distribution
Fedora Silverblue 39
Debugging Information
Troubleshooting Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: