[Bug 1760139] [NEW] Import SSH identity: Launchpad IDs can contain dots
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760139 Title: Import SSH identity: Launchpad IDs can contain dots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1760139/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662552] Re: snaps don't work with NFS home
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.launchpad.net/bugs/1662552 Title: snaps don't work with NFS home To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1662552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713767] Re: Snaps with classic confinement and /home on NFS
*** 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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713767 Title: Snaps with classic confinement and /home on NFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1713767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1713767] [NEW] Snaps with classic confinement and /home on NFS
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 | grep home node09ob28.maas:/mnt/nfs/ubuntu on /home/ubuntu type nfs4 (rw,relatime,vers=4.0,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.27.28.117,local_lock=none,addr=172.27.28.116) $ grep -i denied /var/log/syslog Aug 15 23:35:11 node09ob28 kernel: [ 902.908181] audit: type=1400 audit(1502840111.290:34): apparmor=“DENIED” operation=“sendmsg” profile="/snap/core/2462/usr/lib/snapd/snap-confine" pid=17018 comm=“snap-confine” laddr=172.27.28.117 lport=823 faddr=172.27.28.116 fport=2049 family=“inet” sock_type=“stream” protocol=6 requested_mask=“send” denied_mask=“send" Aug 15 23:35:11 node09ob28 kernel: [ 902.908200] audit: type=1400 audit(1502840111.290:35): apparmor=“DENIED” operation=“sendmsg” profile=”/snap/core/2462/usr/lib/snapd/snap-confine" pid=17018 comm=“snap-confine” laddr=172.27.28.117 lport=823 faddr=172.27.28.116 fport=2049 family=“inet” sock_type=“stream” protocol=6 requested_mask=“send” denied_mask=“send" Aug 15 23:35:11 node09ob28 kernel: [ 902.908215] audit: type=1400 audit(1502840111.290:36): apparmor=“DENIED” operation=“sendmsg” profile=”/snap/core/2462/usr/lib/snapd/snap-confine" pid=17018 comm=“snap-confine” laddr=172.27.28.117 lport=823 faddr=172.27.28.116 fport=2049 family=“inet” sock_type=“stream” protocol=6 requested_mask=“send” denied_mask=“send” NFS server configuration $ cat /etc/exports /mnt/nfs*(rw,sync,no_root_squash) ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713767 Title: Snaps with classic confinement and /home on NFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1713767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1644428] Re: Unable to log in with AD account after update
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 1.1.8-3.2ubuntu2 amd64 ii libpam-modules-bin 1.1.8-3.2ubuntu2 amd64 ii libpam-pwquality:amd64 1.3.0-0ubuntu1amd64 ii libpam-runtime 1.1.8-3.2ubuntu2 all ii libpam-sss:amd64 1.13.4-1ubuntu1.2 amd64 ii libpam-systemd:amd64 229-4ubuntu16 amd64 ii libpam0g:amd64 1.1.8-3.2ubuntu2 amd64 ii python-samba 2:4.3.11+dfsg-0ubuntu0.16.04.3amd64 ii samba2:4.3.11+dfsg-0ubuntu0.16.04.3amd64 ii samba-common 2:4.3.11+dfsg-0ubuntu0.16.04.3all ii samba-common-bin 2:4.3.11+dfsg-0ubuntu0.16.04.3amd64 ii samba-dsdb-modules 2:4.3.11+dfsg-0ubuntu0.16.04.3amd64 ii samba-libs:amd64 2:4.3.11+dfsg-0ubuntu0.16.04.3amd64 ii samba-vfs-modules2:4.3.11+dfsg-0ubuntu0.16.04.3amd64 >From /var/log/auth.log: 10:48:56 gcc-ubuntu-tst1 sudo: gcc : problem with defaults entries ; TTY=pts/18 ; PWD=/etc/sssd ; 10:48:56 gcc-ubuntu-tst1 sudo: PAM unable to dlopen(pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: No such file or directory 10:48:56 gcc-ubuntu-tst1 sudo: PAM adding faulty module: pam_winbind.so 10:48:56 gcc-ubuntu-tst1 sudo: gcc : TTY=pts/18 ; PWD=/etc/sssd ; USER=root ; COMMAND=/bin/more sssd.conf 10:48:56 gcc-ubuntu-tst1 sudo: pam_unix(sudo:session): session opened for user root by gcc(uid=0) 10:48:56 gcc-ubuntu-tst1 sudo: pam_unix(sudo:session): session closed for user root -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1644428 Title: Unable to log in with AD account after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1644428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664248] Re: Can't disable a backports pocket when deploying Ubuntu 14.04
@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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664248 Title: Can't disable a backports pocket when deploying Ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1664248/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
