You will need to create an AppArmor profile for the AppImage to work
using unprivileged user namespaces with privileged operations. Here's a
more detailed explanation in a different bug:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056627/comments/4
--
You received this bug notificati
Could someone please confirm whether this is fixed?
Lsb_release
Description:Ubuntu 24.04.1 LTS
Apparmor
Version: 4.0.1really4.0.1-0ubuntu0.24.04.3
srdjan@serenity:~$ /home/srdjan/Software/Obsidian-1.4.13.AppImage
[9225:1102/202058.416464:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox
Andreas - more details about add picture and bubblewrap is here
https://bugs.launchpad.net/ubuntu/+source/budgie-control-
center/+bug/2065708
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.la
From what I understand, the unprivileged_userns profile disables
capabilities:
$ cat /etc/apparmor.d/unprivileged_userns
# Special profile transitioned to by unconfined when creating an unprivileged
# user namespace.
#
abi ,
include
profile unprivileged_userns {
audit deny capability, <---
I installed the Budgie Desktop with Noble on 28 September 2024, and it
appears to me that this bug hasn't been fixed by the SRU - I've got the
SRU installed and the misbehavior is still occurring.
```
flerken: $ uname -a
Linux flerken 6.8.0-45-generic #45-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 30
12:
This bug was fixed in the package apparmor -
4.0.1really4.0.1-0ubuntu0.24.04.3
---
apparmor (4.0.1really4.0.1-0ubuntu0.24.04.3) noble; urgency=medium
* Revert to version 4.0.1-0ubuntu0.24.04.2 except for the patch
that enables the bwrap-userns-restrict profile (LP: #2072811).
Thanks very much for the explanation, @jjohansen.
--
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/2064672
Title:
[SRU] - fixes for apparmor on noble
Status in apparmor pa
This SRU should land soon. It is up to the release team to decide when
it will be released. There are a couple reason this is baking longer (28
days) than the minimum 7 days. In -proposed is a previous iteration
caused a regression and had to be reverted. The 24.04.1 release happened
recently and t
Thank you everyone for your hard work on this. Can I ask how long until
this fix will be 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/2064672
Title:
[SRU] - f
Verification completed on apparmor noble-proposed
$ apt policy apparmor
apparmor:
Installed: 4.0.1really4.0.1-0ubuntu0.24.04.3
Candidate: 4.0.1really4.0.1-0ubuntu0.24.04.3
Version table:
*** 4.0.1really4.0.1-0ubuntu0.24.04.3 100
100 http://archive.ubuntu.com/ubuntu noble-proposed/ma
Hello Georgia, or anyone else affected,
Accepted apparmor into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apparmor/4.0.1really4.0.1-0ubuntu0.24.04.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new pa
11 matches
Mail list logo