-
Notifications
You must be signed in to change notification settings - Fork 3
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 fails to execute child process ?dbus-launch? (No such file or directory) for fedora remote #565
Comments
Without
Maybe it has something to do with the |
Please try to reproduce this issue in a clean Fedora Silverblue installation. |
@travier I installed Fedora Silverblue 40 in a GNOME Box. The issue exists there, too. I only created a single user. Installing a flatpak either with
I assume the problem lies in So, why does the fedora remote require dbus-launch and the flathub remote doesn't? It has something to do with OCI vs OStree, I guess. And why does it work when run as the currently GUI logged-in user? I just ssh'ed to localhost as myself and ran
I know, I know, Flatpak and Silverblue seem to be systems dedicated for self-administrating end-users. But not being able to remotely install a flatpak seems a little bit odd. Ideally, I'd like to install flatpaks from fedora remote without being graphically logged in.
|
You should probably reach out to the Flatpak SIG for Fedora Flatpaks: https://fedoraproject.org/wiki/SIGs/Flatpak |
Describe the bug
Any attempt at installing a flatpak from the fedora remote results in an error:
Installing flatpaks from the flathub remote works, though:
To Reproduce
Expected behavior
I expect the flatpak being installed.
OS version:
Additional context
We layered the puppet package. When applying our puppet manifests we encounter this error for each flatpak from the fedora remote but not the flathub remote. The same manifest works without issues for Workstation 39 and 40.
The text was updated successfully, but these errors were encountered: