[Touch-packages] [Bug 1575779] Re: hostnamectl fails under lxd unpriv container
** Merge proposal unlinked: https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Triaged Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575779] Re: hostnamectl fails under lxd unpriv container
** Merge proposal unlinked: https://code.launchpad.net/~wesley-wiedenmeier/cloud-init/+git/cloud-init/+merge/321029 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1575779 Title: hostnamectl fails under lxd unpriv container Status in apparmor package in Ubuntu: Triaged Bug description: 1. % lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 2. % apt-cache policy apparmor apparmor: Installed: 2.10.95-0ubuntu2 Candidate: 2.10.95-0ubuntu2 Version table: *** 2.10.95-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy lxd lxd: Installed: 2.0.0-0ubuntu4 Candidate: 2.0.0-0ubuntu4 Version table: *** 2.0.0-0ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status 3. lxc launch ubuntu-daily:xenial x1 lxc exec x1 /bin/bash root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 4. hostnamectl status hangs indefinitely On the host, there are some audit messages for each invocation of hostnamectl [411617.032274] audit: type=1400 audit(1461695563.731:100): apparmor="DENIED" operation="file_lock" profile="lxd- x1_" pid=17100 comm="(ostnamed)" family="unix" sock_type="dgram" protocol=0 addr=none It's related to socket activation. One can workaround this by running systemd-hostnamed in the background first root@x1:~# /lib/systemd/systemd-hostnamed & [1] 2462 root@x1:~# hostnamectl status Static hostname: x1 Icon name: computer-container Chassis: container Machine ID: 833b8548c7ce4118b4c9c5c3ae4f133d Boot ID: 9d5fbb053cf7494589c0863a0a4cf0ca Virtualization: lxc Operating System: Ubuntu 16.04 LTS Kernel: Linux 4.4.0-18-generic Architecture: x86-64 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10.95-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Wed Apr 27 11:19:27 2016 InstallationDate: Installed on 2016-01-01 (117 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=e0b8b294-f364-4ef5-aa70-1916cdd37192 ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582767] Re: apparmor permissions missing for winbind
** Changed in: ntp (Ubuntu) Assignee: Wesley Wiedenmeier (wesley-wiedenmeier) => (unassigned) ** Changed in: ntp (Ubuntu) Assignee: (unassigned) => ChristianEhrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1582767 Title: apparmor permissions missing for winbind Status in ntp package in Ubuntu: Triaged Bug description: When using Winbind, ntpd needs to access the Winbind pipe: May 17 16:23:15 bo kernel: [ 27.598551] type=1400 audit(1463494995.048:18): apparmor="DENIED" operation="connect" profile="/usr/sbin/ntpd" name="/run/samba/winbindd/pipe" pid=1517 comm="ntpd" requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Would there be any reason not to allow this ? I added the following line to /etc/apparmor/init/network-interface-security/usr.sbin.ntpd: /run/samba/winbindd/pipe rw, Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1582767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1519120] Re: Xenial: VLAN interfaces don't work until after a reboot
Since it looks like network-manager needs to pull in 'vlan' by default, here is a debdiff that adds it to recommends. It may make sense to write a patch that grays out menu entries for network types which do not have the required deps installed, but this may have to wait until later. ** Patch added: "add_vlan.debdiff" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1519120/+attachment/4688034/+files/add_vlan.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1519120 Title: Xenial: VLAN interfaces don't work until after a reboot Status in network-manager package in Ubuntu: Confirmed Status in vlan package in Ubuntu: Invalid Bug description: I tried to use the network manager UI to define a VLAN interface, and nothing happened. There are a few bugs here: (1) When creating a VLAN interface through the UI, the "vlan interface name" must be filled in. This should just default to ., rather than being a required field. (I typed in "vlan100" to get the "Save" button to activate.) (2) After creating my VLAN interface, nothing happened. No new interface appeared. I then realized that I had not installed the "vlan" package, and assumed that NetworkManager therefore could not complete configuration of the interface. (3) After installing the 'vlan' package (and then telling NetworkManager to disconnect and reconnect my Ethernet interface from the UI, just for good measure), still no VLAN interfaces were present on my system. I also tried editing the VLAN interface in the UI, and specifying "enp4s0f1.100", but still no VLAN interface came online. # apt-cache policy network-manager network-manager: Installed: 1.0.4-0ubuntu6 Candidate: 1.0.4-0ubuntu6 Version table: *** 1.0.4-0ubuntu6 0 500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages 100 /var/lib/dpkg/status # apt-cache policy vlan vlan: Installed: 1.9-3.2ubuntu1 Candidate: 1.9-3.2ubuntu1 Version table: *** 1.9-3.2ubuntu1 0 500 http://172.16.42.88/ubuntu/ xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1519120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Thank you for sponsoring, I will open a bug report on their tracker and link to this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
We should get sign off on this from the ubuntu-devel mailing list before making this change, as it changes behaviour. The new behaviour makes sense, as there does not seem to be an advantage to blanking the screen like this, but there might be some people who object -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: In Progress Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
** Changed in: console-setup (Ubuntu) Assignee: (unassigned) = Wesley Wiedenmeier (wesley-wiedenmeier) ** Changed in: console-setup (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in console-setup package in Ubuntu: In Progress Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Disabled blank screen in /etc/kbd/config ** Attachment added: patch https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/869017/+attachment/4439243/+files/patch ** Package changed: console-setup (Ubuntu) = kbd (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: In Progress Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
