** Changed in: snapd
Assignee: Zygmunt Krynicki (zyga) => (unassigned)
** Changed in: snapd
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773515
Title:
app
One problem is that if snapd is removed via installation of a
metapackage (as in my case) then there isn't really a point where the
sysadmin makes the clear choice of purging vs removing.
This bug is still biting, so I wonder if @zyga could revisit this issue.
--
You received this bug notificati
I ran into this issue. Workaround fixed it perfectly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773515
Title:
apparmor fails after removal of snapd
To manage notifications about this bug go to
I have an unfinished patch that moves the snap-confine apparmor profile
out of /etc entirely. I will try to finish and propose it.
** Changed in: snapd
Status: Triaged => Confirmed
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notifi
Zygmunt, you shouldn't override the dpkg behavior as there is an
expectation on a Debian based system on how things in /etc are treated
and what dpkg expects. That said, you could change the packaging in
various ways. Eg, stop shipping it in /etc at all or disable the profile
via /etc/apparmor.d/di
I have a hunch that this happens because /etc/* is marked as a
configuration file and not automatically removed unless the package is
purged. I think we could special case that file and remove it on regular
package remove using postrm script.
** Also affects: snapd
Importance: Undecided
Fink Nottle: AFAIK apparmor should not be breaking. The parser loads all
profiles but doesn't stop on a profile that fails to load. The error
message is displayed but remaining profiles are loaded anyway. It there
some specific profile that you were expecting to see loaded that did not
after you re
This is still broken. A key security feature of the OS breaks if you
uninstall some garbage package. I wouldn't have noticed it if I hadn't
seen the logs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
This has also bugged me for some number of months but the work around is really
easy -- just use
apt purge snapd
instead of
apt remove snapd
What happens is that upon removal of the snapd package, dpkg sees that
/var/lib/snapd/apparmor/snap-confine is empty and removes it which later
breaks ap
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/1773515
Title:
appa
@Jamie
Thanks, I hadn't thought of purging to try and clean up from issues like
this when there's a left over file but on hearing you say it then it
seems so obvious!
As I said above I manually removed the file to get apparmor loading
(actually three of them in the /etc/apparmor folders) and not
May 26 10:36:35 ThisOne apparmor[2850]: AppArmor parser error for
/etc/apparmor.d/usr.lib.snapd.snap-confine.real in
/etc/apparmor.d/usr.lib.snapd.snap-confine.real at line 11: Could not
open '/var/lib/snapd/apparmor/snap-confine'
The above indicates that /etc/apparmor.d/usr.lib.snapd.snap-confine
"Does anything happen if you run:
sudo dpkg --configure -a"
Absolutely nothing. As I said I have manually removed the files, if that
may affect it.
Worth noting I run Ubuntu Studio, not vanilla Ubuntu or even Xubuntu,
and sometimes configuration steps may get missed by that team (eg
Xubuntu is a
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773515
Title:
apparmor fails after removal of snapd
To manage notifications about this
The half-installed packages are probably the cause. Does anything happen
if you run:
sudo dpkg --configure -a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773515
Title:
apparmor fails after remov
I do 99% of my package management with apt-get so it was removed via the
command "sudo apt-get remove snapd"
>From dkpg.log from just either side of the last mentions of snapd
2018-05-16 13:29:33 startup packages remove
2018-05-16 13:29:33 status installed snapd:amd64 2.32.8+18.04
2018-05-16 13:29
BTW as I don't plan to reinstall snapd the next day I did a find
find /etc/apparmor.d/ -iname "*snap*"
/etc/apparmor.d/usr.lib.snapd.snap-confine.real
/etc/apparmor.d/cache/usr.lib.snapd.snap-confine.real
/etc/apparmor.d/local/usr.lib.snapd.snap-confine.real
and then manually deleted those files
The maintainer scripts definitely remove that file but perhaps something
went wrong and the installation was only partial. Do you have any dpkg
logs from the removal?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Summary changed:
- apparmour fails after removal of snapd
+ apparmor fails after removal of snapd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773515
Title:
apparmor fails after removal of sna
19 matches
Mail list logo
