This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu5
---------------
apparmor (4.1.0~beta5-0ubuntu5) plucky; urgency=medium
* Add patch to fix fusermount3 profile breaking AppImages (LP: #2098993)
- d/p/u/fusermount3_profile_fixup.patch
* debian/apparmor.maintscript: remove tar and wpa_supplicant profiles
if they were previously installed via an upgrade
-- Ryan Lee <[email protected]> Thu, 20 Feb 2025 09:18:01 -0800
** Changed in: apparmor (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2098993
Title:
Last updates to apparmor broke all AppImages, which depend on
fusermount
Status in apparmor package in Ubuntu:
Fix Released
Bug description:
Ubuntu 25.04.
After last updates to apparmor, all AppImages stopped running, giving
the message:
$ ./filename.AppImage
fusermount: mount failed: Permission denied
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage
if you run it with the --appimage-extract option.
See https://github.com/AppImage/AppImageKit/wiki/FUSE
for more information
open dir error: No such file or directory
Relevant lines from journalctl:
פבר 20 17:32:20 ape kernel: audit: type=1400 audit(1740065540.628:588):
apparmor=“DENIED” operation=“mount” class=“mount” info=“failed flags match”
error=-13 profile=“fusermount3” name=“/tmp/.mount_overGrsjqzZw/” pid=22454
comm=“fusermount” fstype=“fuse.overGrive-3.5.2-x86_64.AppImage”
srcname=“overGrive-3.5.2-x86_64.AppImage” flags=“ro, nosuid, nodev”
פבר 20 17:32:20 ape kernel: audit: type=1400 audit(1740065540.629:589):
apparmor=“DENIED” operation=“mount” class=“mount” info=“failed flags match”
error=-13 profile=“fusermount3” name=“/tmp/.mount_overGrsjqzZw/” pid=22455
comm=“fusermount” fstype=“fuse” srcname=“/dev/fuse” flags=“ro, nosuid, nodev”
ProblemType: Bug
DistroRelease: Ubuntu 25.04
Package: apparmor 4.1.0~beta5-0ubuntu2
ProcVersionSignature: Ubuntu 6.12.0-15.15-generic 6.12.11
Uname: Linux 6.12.0-15-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.31.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 20 19:02:21 2025
InstallationDate: Installed on 2022-01-31 (1116 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.12.0-15-generic
root=UUID=06eb0295-6f5f-4d0e-96e7-4d2e2fe687ac ro quiet splash
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M
vt.handoff=7
SourcePackage: apparmor
Syslog:
2025-02-18T19:59:56.591218+02:00 ape dbus-daemon[9035]: [session uid=0
pid=9033 pidfd=4] AppArmor D-Bus mediation is enabled
2025-02-20T17:25:43.744723+02:00 ape dbus-daemon[20337]: [session uid=0
pid=20335 pidfd=4] AppArmor D-Bus mediation is enabled
2025-02-20T17:26:25.182143+02:00 ape dbus-daemon[20735]: [session uid=0
pid=20733 pidfd=4] AppArmor D-Bus mediation is enabled
2025-02-20T17:38:06.201216+02:00 ape dbus-daemon[24041]: [session uid=0
pid=24039 pidfd=4] AppArmor D-Bus mediation is enabled
UpgradeStatus: Upgraded to plucky on 2025-01-30 (21 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2098993/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
