Bug 2158474

Summary:	Flatpak needs fusermount, doesn't depend on fuse
Product:	[Fedora] Fedora	Reporter:	Marcus Müller <marcus>
Component:	flatpak	Assignee:	David King <amigadave>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	37	CC:	amigadave, debarshir, gnome-sig, klember, mail
Target Milestone:	---
Target Release:	---
Hardware:	aarch64
OS:	Linux
Whiteboard:
Fixed In Version:	flatpak-1.15.1-2.fc38 flatpak-1.14.1-2.fc37	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-01-11 01:21:22 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcus Müller 2023-01-05 14:56:57 UTC

Description of problem:
`flatpak install org.kde.krita` fails after downloading every dependency package with the inability to start fusermount; no wonder, only fusermount3 is available
 
Version-Release number of selected component (if applicable):
1.14.1

How reproducible:


Steps to Reproduce:
1. Fresh F37 installation
2. dnf install flatpak; flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
3. flatpak install org.kde.krita

Actual results:
Warning: Could not unmount revokefs-fzse filesystem at /var/tmp/flatpak-cache-XNAY1/org.freedektop.Platform.GL.default-3YMAY1: Failed to execute child process "fusermount" (No such file or directory)

Expected results:

Actually works

Additional info:

The necessary /usr/bin/fusermount is available through `dnf install fuse`.

Either, we make the flatpak RPM depend on `fuse` (which is fuse 2) explicitly, or we modify / configure flatpak to use the `fusermount3` instead of `fusermount`.

I'd strongly tend towards the latter, as the flatpak.spec has

BuildRequires:  pkgconfig(fuse3)

so, using `fusermount` (i.e., fuse 2) instead of `fusermount3` is probably a bug, and we're just lucky it works.

Comment 1 Fedora Update System 2023-01-06 06:30:33 UTC

FEDORA-2023-b4bb5edf45 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-b4bb5edf45

Comment 2 Fedora Update System 2023-01-07 02:20:18 UTC

FEDORA-2023-b4bb5edf45 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-b4bb5edf45`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b4bb5edf45

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2023-01-11 01:21:22 UTC

FEDORA-2023-b4bb5edf45 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.