The ability to remove the snap without any dependency check/warning is
indeed worrying. The apparmor STATUS message likely not. The
apparmor=STATUS messages are most likely about profile loads and
replacements. In this case the profile="unconfined" means the task doing
the profile load is unconfine
I took a closer look at my system logs, and among the apparmor denied
messages and the systemd "scheduled restart job" / "started" messages,
there was also this:
Nov 01 04:10:34 computer snapd-desktop-integration.snapd-desktop-
integration[1042067]: Content snap command-chain for /snap/snapd-
desk
I was incorrect, checking older logs I see firmware-notifier (snap-
update-ns.firmware-updater, snap.firmware-updater.firmware-notifier) has
been denied by apparmor for a while. It's just a lot more visible now
with snapd-desktop-integration and prompting-client.
--
You received this bug notifica
I believe this started for me when I upgraded from noble to oracular.
After upgrading I was able to start the Firefox snap (by accident, I
thought I still had the deb version installed), but after removing the
Firefox and Thunderbird snaps, and removing then reinstalling some of
the framework/libra
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084099
Title:
so m
