Drop fuse (version 2) from all Atomic Desktops images #50
Labels
No labels
docs
kind
bug
kind
enhancement
kind
package-request
release
f40
release
f41
release
f42
release
f43
release
f44
release
f45
release/rawhide
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
atomic-desktops/tracker#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We no longer have any application requiring fuse version 2 (they all use fuse3 now).
So the library got dropped with an update in F40 once the last users was updated (rpm-ostree).
Fuse 2 is however apparently required for AppImage to work.
We recommend using Flatpaks, but a lot of users likely use AppImages to get some applications on Atomic Desktops.
Should we carry the fuse2 library "indefinitely" in the base image to keep compatibility?
I've re-added the package to F40 to keep the compatibility at least for this release.
We should decide quickly if we want it in Fedora 41, an then when (if ever) we want to drop it.
See: https://github.com/fedora-silverblue/issue-tracker/issues/589
It's probably too short notice to drop it for F41 so I'll likely keep it there as well, but we still need to have that discussion.
For what it is worth, users of Bazzite use AppImages for some software because the creator does not ship a flatpak for it. We will plan on keeping it in our images if upstream decides to remove fuse 2.
another report: https://bugzilla.redhat.com/show_bug.cgi?id=2305841
I'm more inclined to help people out here and add the fuse2. In general, AppImages are spread especially that these should work everywhere, so people might be confused when they don't.
See also:
I'm adding it back everywhere for now.
PRs:
mentioned in commit ci-test@bed8509fd8936bb78ab4dd75413e0f867c8eec35
mentioned in commit ci-test@73eddcef47ea32638133a1428aebef6cfde28aaa
This is also a good candidate for a sysext. Let's keep this open for now.
For what it's worth, secureblue doesn't support AppImage/libfuse2 out of the box due to security concerns.
Also, the new type2-runtime is linked statically, so "libfuse2 is no longer required on the target system".
This abandonware should be dropped for good, methinks.
Interesting. That would still break the older AppImages but if the new ones work that would be OK. We should be able to do that in F44 maybe.
mentioned in commit ci-test@0c7bdf90ba91a79a299354137128d34305e09504
mentioned in commit ci-test@baaab74d38f5e0f7d97eb1d545c537fb9cb9e743
mentioned in commit ci-test@6da354c479ae73d80e8e1c713cf0b82f6469d8ec
set status to In progress
Proposed to be dropped for F44: https://fedoraproject.org/wiki/Changes/AtomicDesktopDropFuse2
changed title from
Should we keep fuse (version 2) in the base image for AppImage compatibility?toDrop fuse (version 2) from all Atomic Desktops imagesmentioned in commit ci-test@7e1d9634e03c86219231e994f64189372f219828
mentioned in commit ci-test@131822bad7ee98de14cbd4ca040b4a4e5f1fdf78
set status to Done
This has been merged for F44.
mentioned in commit ci-test@3e6479c029fb2c6fd8683bc596e991cd6d814145
Hello @Siosm, I’m on Fedora Silverblue 44 beta and my AppImages don’t work, despite being type2-runtime AppImages (as indicated by Gear Lever):
Did I miss something?
What commands did you use to check that they are type2?
And which AppImage is that? You should probably report that to the upstream project as I won't be able to fix it.