-
-
Notifications
You must be signed in to change notification settings - Fork 439
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] Update manifest for UMU support #3674
[Flatpak] Update manifest for UMU support #3674
Conversation
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
I have read the CLA Document and I hereby sign the CLA |
umu flatpak update has been merged: However please note this PR needs modification now as the umu-launcher manifest has been renamed from: org.openwinecomponents.umu.launcher to: org.openwinecomponents.umu.umu-launcher |
Thanks for the letting us know 👍🏽 |
5d1c973
to
51a5af0
Compare
I don't think the manifest kept in this repo is that relevant? It's only used when installing a local test build. |
8465488
into
Heroic-Games-Launcher:main
Related to #3480 and depends on the updated Flatpak support in ULWGL aka umu to be merged/reviewed. After the Flatpak umu is installed in the user's system, the Heroic Games Launcher will need to allow explicit access to umu's
$XDG_DATA_HOME/umu
and the system/app/share
directory to run games through the launcher.The reason is because, without going into the details, umu will currently copy files from
/app/share
to its private Flatpak directory, and Valve's Steam Runtime tools (e.g., Pressure Vessel) are designed to only be executed from the user's home directory. Without explicit visibility to these directories defined in Heroic's manifest, it's likely that umu will fail to launch games successfully due to Flatpak's strict filesystem permissions.Use the following Checklist if you have changed something on the Backend or Frontend: