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

[Flatpak] Osu does not launch #82

Closed
cassiofb-dev opened this issue May 26, 2024 · 10 comments
Closed

[Flatpak] Osu does not launch #82

cassiofb-dev opened this issue May 26, 2024 · 10 comments

Comments

@cassiofb-dev
Copy link

Hi, first of all thanks for this awesome project!

I mostly use flatpak to run things but many devs use app image as official distribution so I thought it would be amazing to execute app images inside flatpak sandbox!

I tried to play osu but it does not start, here are the steps:

  1. I clicked the launch button
  2. For some seconds the button title changed to "launching..."
  3. The button title changed to "launch"

I clicked on enable debug logs to provide a better log file, here is it: gearlever.log

@mijorus
Copy link
Owner

mijorus commented Jun 6, 2024

Judging from your logs, this should't be related, but the latest version (1.6.0) fixed an issue with apps like Osu! that had special characters in the name

@cassiofb-dev
Copy link
Author

Hi, yeah. I upgraded to 1.6.0 (the latest version today) and I'm getting the same behavior.

@TuxDeluxe
Copy link
Contributor

TuxDeluxe commented Jun 8, 2024

I've seen this happen on my system when I did not have FUSE installed. If it isn't installed on your system these app images will not launch. Is it possible to install fuse and give it another try?

@cassiofb-dev
Copy link
Author

@TuxDeluxe , indeed I didnt have fuse installed. I installed it and the same thing happened, when I tried to run in terminal I got app image error but that was expected because I'm using Alpine. Is there anyway to check logs when gearlever runs appimages on flatpak sandbox?

Here is the image with the error outside flatpak sandbox:

image

@mijorus
Copy link
Owner

mijorus commented Jun 9, 2024

To be honest it looks something that has to do with your system rather than with Gear Lever

@mijorus mijorus closed this as not planned Won't fix, can't repro, duplicate, stale Jun 9, 2024
@TuxDeluxe
Copy link
Contributor

Yeah, because app images sometimes don’t work on alpine, they won’t work through gearlever either. Seems like a problem with how osu relies on glibc rather than musl.

@cassiofb-dev
Copy link
Author

@TuxDeluxe yeah, I thought the app image was executed in flatpak sandbox. Does it executes on the host system? If so I think there's really nothing that can be done.

App Image doesn't support Alpine and other distros not using glibc at all and I thought this project made it execute inside the sandbox. This is the issue I found on App Image project: AppImage/AppImageKit#877

@TuxDeluxe
Copy link
Contributor

@cassiofb-dev gearlever does sandbox some commands but it uses

flatpak-spawn —host

to run app images which essentially runs them on the hosts machine.

@mijorus
Copy link
Owner

mijorus commented Jun 11, 2024

@TuxDeluxe yeah, I thought the app image was executed in flatpak sandbox. Does it executes on the host system? If so I think there's really nothing that can be done.

App Image doesn't support Alpine and other distros not using glibc at all and I thought this project made it execute inside the sandbox. This is the issue I found on App Image project: AppImage/AppImageKit#877

They don't, as others have suggested.
App images are launched on the host system, the goal of this project is just to automate the "desktop file creation" part.

@Samueru-sama
Copy link

@cassiofb-dev Take a look at this if you want to sandbox appimages: https://github.com/mgord9518/aisap

App Image doesn't support Alpine and other distros not using glibc at all and I thought this project made it execute inside the sandbox. This is the issue I found on App Image project: AppImage/AppImageKit#877

You can actually sort of do this already as the static runtime is already used in go-appimage

sort of because of this small issue lol

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