I don't know, whether this matters: I still get some
apparmor="DENIED"-messages as shown in the attachment.
Snapd and snap.nextcloud seem to be up and running. Thanks again!
** Attachment added: "journalctl__grep_DENIED__tail.txt"
Thanks a lot for the hint! The following fixed the problem here:
$ sudo mv /etc/apparmor.d/usr.lib.snapd.snap-confine $HOME/tmp
$ sudo service apparmor restart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "usr.lib.snapd.snap-confine"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1814141/+attachment/5236594/+files/usr.lib.snapd.snap-confine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
According to apt-file usr.lib.snapd.snap-confine.real seems to be from
snapd:
$ apt-file find usr.lib.snapd.snap-confine
snapd: /etc/apparmor.d/usr.lib.snapd.snap-confine.real
** Attachment added: "usr.lib.snapd.snap-confine.real"
$ snap version
snap2.37.1.1+18.04
snapd 2.37.1.1+18.04
series 16
ubuntu 18.04
kernel 4.15.0-43-generic
$ snap changes
ID Status Spawn Ready Summary
566 Doneyesterday at 23:04 CET yesterday at 23:04 CET Running service
command
567 Done
I observe a similar behaviour since latest upgrade of snapd (update from
around 2019-02-02):
$ /snap/bin/nextcloud.occ
cannot read mount namespace identifier of pid 1: Permission denied
$ uname -a
Linux cnb012 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018
x86_64 x86_64 x86_64
