Probably related to
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2111205/comments/1.
The actual solution seems to be more involved than my suggested
workaround. From the comment there:
1. disconnected path
The failures with info="Failed name lookup - disconnected path" are due to
fusermount3 being run in a mount namespace, and trying to access fds that it
does not have access to. This is likely due to flatpak's sandbox design, and
its broken assumption that it can get away with doing fd passing without
mediation.
[…]
These are all open unix domain sockets to bwrap, possibly setup for
portal access. We need to investigate why bwrap would be setting these
up, and what the implication is. Generally stuff like this is setup as a
way to punch holes in security. Before adding those to the fusermnt3
profile.
Overall it looks like we are going to have to setup some
conditionals and treat fusermnt3 differently when run under flatpak.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2120439
Title:
Pika Backup fails to mount backup because of apparmor fusermount3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2120439/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
