Looking at the upstream bug report, the above denials are the likely cause of the bad file descriptor errors.
pika-backup-trace-DEBUG: 17:11:48.301: src/borg/process.rs:612:0: borg output: sending file descriptor: Bad file descriptor pika-backup-CRITICAL **: 17:11:48.301: src/borg/utils.rs:16:0: Parse error sending file descriptor: Bad file descriptor pika-backup-WARNING **: 17:11:48.302: Mounting Backup Archives: - sending file descriptor: Bad file descriptor flatpak/bubblewrap pokes holes in its confinement for portals using unix sockets. This is a bit of a guess atm but it looks like pika is assuming one of the replaced descriptors is a unix socket and attempting to send a descriptor across it via SCM rights but the descriptor is no longer a unix socket and the fd can not be passed, resulting in the Bad file descriptor error. -- 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
