I still have the same issue:
$ snap --version
snap2.39.3
snapd 2.39.3
series 16
ubuntu 18.04
kernel 5.0.0-21-generic
[ 5625.716224] ecryptfs_dir_open: Error attempting to initialize the lower file
for the dentry with name [/]; rc = [-13]
[ 5625.716249] audit: type=1400
@Jamie,
I don't think so.
** Attachment added: "lp1592696.gz"
https://bugs.launchpad.net/ubuntu/xenial/+source/ubuntu-core-launcher/+bug/1592696/+attachment/4879396/+files/lp1592696.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Todor,
The profile you attached compiles fine. Did you adjust any files in
/etc/apparmor.d/abstractions/*?
Can you attach the the tar file from the following command?
$ sudo tar -zcvf lp1592696.gz /etc/apparmor.d
/var/lib/snapd/apparmor/profiles
--
You received this bug notification because
I got "cannot change profile for the next exec call: No such file or directory"
for all installed snaps.
I've encrypted my $HOME during clean install of 16.04 a year ago. At the
beginning I thing snaps worked, later something messed up.
** Attachment added: "usr.lib.snapd.snap-confine.real"
@Todor, can you please:
1. paste the denials you are seeing
2. attach /etc/apparmor.d/usr.lib.snapd.snap-confine.real
3. list the steps to reproduce including how your setup the encrypted dir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Jamie ,
so what should I do?
I removed /etc/apparmor.d/usr.bin.ubuntu-core-launcher and copy-paste the code
in /etc/apparmor.d/usr.lib.snapd.snap-confine.real and run sudo
apparmor_parser -r /etc/apparmor.d/usr.lib.snapd.snap-confine.real and the
problem still persist. Also installed
@Todor, /etc/apparmor.d/usr.bin.ubuntu-core-launcher is no now longer
used and the file to modify is now /etc/apparmor.d/usr.lib.snapd.snap-
confine.real (there have been several packaging changes since this bug
was filed with the move of ubuntu-core-launcher being renamed to snap-
confine and
I was missing /etc/apparmor.d/usr.bin.ubuntu-core-launcher so I created one and
pasted:
owner @{HOME}/.Private/ r,
owner @{HOME}/.Private/** mrixwlk,
# new-style encrypted $HOME
owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,
owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
but
I also ran into this problem trying out the htop snap. After removing
the snap I installed htop via apt, but it still failed with the same
message:
$ htop
failed to create user data directory. errmsg: Permission denied
$ which htop
/usr/bin/htop
Enabling xenial-proposed and running apt upgrade
Thanks for testing Tony. Regarding /home/espy/snap/hello that is bug and
separate from this update and I think that will be fixed once snap-
confine passes SRU and bug #1611063 is addressed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Installing the proposed packages worked for me, albeit with an extra
hoop of running a snap app as sudo first to get around the permission
problem.
After the installing, I did:
% sudo snap install hello
% hello
mkdir: cannot create directory ‘/home/espy/snap/hello’: Permission denied
% sudo
** Summary changed:
- snaps dont work with encrypted home: failed to create user data directory.
errmsg: Permission denied
+ snaps don't work with encrypted home: failed to create user data directory.
errmsg: Permission denied
--
You received this bug notification because you are a member of
12 matches
Mail list logo
