Installing snap-confine and ubuntu-core-launcher from xenial-proposed
resolved my issues, looking good. On the pending SRU page I don't see
this bug being marked as fixed by the upload, but from my POV this can
be considered as 'verification-done'.
--
You received this bug notification because
Still waiting on snap-confine to land (it is in xenial-proposed)-- you
can install snap-confine and ubuntu-core-launcher from
https://launchpad.net/ubuntu/+source/snap-
confine/1.0.38-0ubuntu0.16.04.4 and it will work.
--
You received this bug notification because you are a member of Ubuntu
Any fix for Ubuntu version 16.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user data
directory. errmsg: Permission denied
Err, I of course meant "will hopefully be fixed for all 16.04 LTS users
soon"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user
FYI, this is fixed in the snap-confine that is in xenial-proposed and so
it will hopefully be fixed for all 14.04 LTS users soon. In the meantime
if you don't want to install proposed packages, the workarounds listed
in this report continue to work. I'll list the complete workaround here:
1. make
This is too bad: Snap apps even don't run ...
Linux: 4.4.0-31-generic #50-Ubuntu SMP x86_64 GNU/Linux
Description:Ubuntu 16.04.1 LTS
snap2.0.10
:~$ vlc
failed to create user data directory. errmsg: Permission denied
:~$ sudo vlc
sudo: vlc: command not found
It has to be fixed as a soon
@brunonova + @gdstrand: Thanks, that did it for me.
Linux 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@liro, the full set of snap-confine changes need to land since they are
needed for a lot of other important snappy work and the snappy team will
do what it takes to make them land. AIUI, the snappy team is actively
working on landing snap-confine 1.0.36 (which has the fix for this bug)
and they'll
@Martin Pitt,
What about the patch in comment #7? It shouldn't be a too big change for
a SRU?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu Xenial)
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/1592696
There are a looot of changes in this, including a completely new build
system, which don't match the usual SRU policy. Please add the missing
SRU test case, an analysis of the regression potential, and point to a
test plan to ensure that there are no regressions on existing xenial
systems.
**
Sorry, "this" == upload sitting in the xenial-proposed SRU review queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user data
Doesn't "Fix Released" mean it is already pushed into repository? That
is definitely not the case now what it comes to Xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps
@Bruno Nova,
I'm sorry, I misread the apparmor_parser comment, and thought I only had
to run apparmor_parser. After modifying /etc/apparmor.d/usr.bin.ubuntu-
core-launcher as described in #7 running the apparmor_parser fixed snaps
for me.
Thanks a lot for this workaround, now I can start using
Is this going to be fixed in xenial? or just yakkety? I'm more
comfortable with a package update than a workaraund.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with
@Redmar, have you modified /etc/apparmor.d/usr.bin.ubuntu-core-launcher
according to comment #7 before running that command?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont
Yep, I'm still affected by this also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user data
directory. errmsg: Permission
I have tried the fix in #8 on 16.04 with encrypted home, but I still get
the same error:
redmar@raider:~$ sudo apparmor_parser -r
/etc/apparmor.d/usr.bin.ubuntu-core-launcher
redmar@raider:~$ hello
failed to create user data directory. errmsg: Permission denied
redmar@raider:~$ which hello
This bug was fixed in the package ubuntu-core-launcher - 1.0.29+1ubuntu1
---
ubuntu-core-launcher (1.0.29+1ubuntu1) yakkety; urgency=medium
* debian/usr.bin.ubuntu-core-launcher: add a couple more workaround rules
for ecryptfs (LP: #1592696)
-- Jamie Strandboge
Uploaded to yakkety and queued in snap-confine. Syncing with mvo and
zyga on timing of those other changes to see if the ecryptfs issues
should be separate SRU.
** Changed in: ubuntu-core-launcher (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because
For the workaround, simply use:
$ sudo apparmor_parser -r /etc/apparmor.d/usr.bin.ubuntu-core-launcher
No need to reboot and no need to install apparmor-utils.
As for the timing of the fix-- the snappy team is making some fairly
large changes to the launcher which is why the fix for this is not
As for the yakkety denial, it looks like a rule was missed. I'll make
sure that is fixed in yakkety and queued for the next SRU.
** Also affects: ubuntu-core-launcher (Ubuntu)
Importance: Undecided
Status: New
** Changed in: snapd (Ubuntu)
Status: Confirmed => Invalid
**
I already commented in https://bugs.launchpad.net/snappy/+bug/1574556/comments/5
I posted a log in there.
The fix (and workaround) is to add these lines to the end of the file
/etc/apparmor.d/usr.bin.ubuntu-core-launcher, before the closing bracket
('}'):
# Workaround
This is a good catch, thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user data
directory. errmsg: Permission denied
This is from a fresh install of the latest yakkety in virtualbox:
$ grep DEN /var/log/syslog
Jun 15 18:49:41 test-VirtualBox kernel: [ 90.415758] audit: type=1400
audit(1466009381.034:41): apparmor="DENIED" operation="open"
profile="/usr/bin/ubuntu-core-launcher"
For the yakkety system, what is the output of 'grep DEN
/vag/log/syslog'?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user
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/1592696
Title:
This is also a problem in Yakkety.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592696
Title:
snaps dont work with encrypted home: failed to create user data
directory. errmsg: Permission
28 matches
Mail list logo
