We use `snap run` now and this will create the dir with the right
permissions automatically
** Changed in: snapd (Ubuntu)
Status: Triaged => Fix Released
** Changed in: snappy
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Note that this issue will be resolved as soon as `snap run` is used to
launch apps (it's what has the logic to create this directory). That
will be released soon!
** Changed in: snapd (Ubuntu)
Status: Confirmed => Triaged
** Changed in: snappy
Status: Confirmed => Triaged
--
You r
@Bruno, Ok, I'm agree with you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611063
Title:
can't mkdir SNAP_USER_COMMON directory
To manage notifications about this bug go to:
https://bugs.launch
@Eldar, I was talking about the launcher scripts created in "/snap/bin/"
by snapd itself during "snap install", not about scripts bundled with
the snap.
As users, we can create the "common" directory manually.
But, as developers/packagers, we can't do much.
--
You received this bug notification
To brunonova, your methode shows perm denied:
mkdir: cannot create directory '/home/user/snap/my-snap/common': Permission
denied
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611063
Title:
can't m
The temporary solve:
$ snap run my-snap
This cmd create COMMON directory (Needs to ignore errors of prev cmd).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1611063
Title:
can't mkdir SNAP_USER_COMM
Yes, the problem is probably that the launcher script in /snap/bin/ doesn't
create that directory.
Maybe the description of the bug should be changed?
The launcher scripts needs to include these lines, I think:
if [ ! -d "$SNAP_USER_COMMON" ]; then
mkdir -p "$SNAP_USER_COMMON"
fi
** Also affe
