Public bug reported:
In the profile setup, the text field for Launchpad IDs does not allow
the dot '.' character, despite the fact it is a valid ID character.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a m
There is also the case of snaps with classic confinement, which exhibit
the same behavior as described here:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1713767
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
*** This bug is a duplicate of bug 1662552 ***
https://bugs.launchpad.net/bugs/1662552
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552 seems to
refer to "Strictly confined snaps".
This bug specifically calls out snaps with classic confinement.
--
You received this bug notificat
Public bug reported:
Snaps with classic confinement, like conjure-up, cannot be installed
when $HOME is on NFS.
On Ubuntu Xenial server, with snapd 2.25, running conjure-up 2.2.2 fails:
$ conjure-up
cannot create user data directory: /home/ubuntu/snap/conjure-up/549: Permission
denied
$ mount |
The same issue is observed on Xenial:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.2 LTS
Release:16.04
Codename: xenial
ii libpam-gnome-keyring:amd64 3.18.3-0ubuntu2 amd64
ii libpam-modules:amd64
@Tom,
Based on the MAAS screenshot you provided you are getting a 403 error code,
which is unexpected (404 would make more sense).
Can you please provide a listing of the directory structure of the mirror?
$ find /tmp/ -type d -printf '%M %g %u %p\n'
--
You received this bug notification becau
