[Group.of.nepali.translators] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
This bug was fixed in the package resolvconf - 1.79ubuntu13 --- resolvconf (1.79ubuntu13) disco; urgency=medium * bin/resolvconf: use flock so resolvconf can be called in parallel safely (LP: #1825194). -- Alfonso Sanchez-Beato (email Canonical) Wed, 17 Apr 2019 16:53:53 +0200 ** Changed in: resolvconf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: Fix Released Status in resolvconf source package in Xenial: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825194] Re: resolvconf is racy, which leads to broken resolv.conf in parallel calls
I assume this is primarily an issue for UC16, since in UC18 we no longer use resolvconf at all, and have targeted the bug accordingly. Do you want to prepare a corresponding debdiff for xenial, and adjust the bug description to include a complete SRU template per https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template ? ** Also affects: resolvconf (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: resolvconf (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825194 Title: resolvconf is racy, which leads to broken resolv.conf in parallel calls Status in resolvconf package in Ubuntu: Fix Committed Status in resolvconf source package in Xenial: New Bug description: It has been found that simultaneous calls to resolvconf can lead to inconsistent content in resolv.conf. For instance, no nameservers while NetworkManager has one in its record (see LP: #1824395): $ cat /run/resolvconf/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN $ cat /run/resolvconf/interface/NetworkManager nameserver 192.168.1.6 nameserver 192.168.1.2 This can happen easily when calling "netplan apply", which can re- start both networkd and NM. resolvconf is called at that point by the "systemd-networkd-resolvconf-update.service" service, and also directly by NetworkManager, which leads to the situation described above. This is not surprising as there is nothing preventing different instances of resolvconf to access the same files. This sort of situation can be reproduced by running in a loop commands like: $ printf "\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd $ printf "nameserver 80.58.61.250\n" | sudo resolvconf -a NetworkManager & printf "\n" | sudo resolvconf -a networkd Eventually, this leads to a resolv.conf that is not consistent with the last run command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1825194/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822807] Re: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822808 - phase: Testing - phase-changed: Thursday, 11. April 2019 12:13 UTC + phase: Signoff + phase-changed: Thursday, 18. April 2019 05:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822807 Title: linux-gcp: 4.15.0-1030.32~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822808 phase: Signoff phase-changed: Thursday, 18. April 2019 05:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- nvidia GCP object not found -- 4.15.0-1030 security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822807/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1824073] Re: USB stick isn't mounted automatically
** Also affects: udisks2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: udisks2 (Ubuntu) Status: New => Fix Released ** Changed in: udisks2 (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1824073 Title: USB stick isn't mounted automatically Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in udisks2 package in Ubuntu: Fix Released Status in udisks2 source package in Xenial: New Bug description: [Impact] USB stick isn't mounted automatically. Auto-mount function fails. [Test Case] 1) Plug USB stick and check if USB stick is mounted automatically. 2) Umount USB stick 3) Unplug USB stick 4) Go to 1) --- If the error message below appears, auto-mount function will fail. systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory Error Message: 1. when auto-mount fails: kernel: [ 175.661572] usb 2-2.3.3: USB disconnect, device number 6 systemd-udevd[2690]: inotify_add_watch(9, /dev/sda, 10) failed: No such file or directory org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 kernel: [ 222.843326] usb 2-2.3.3: new SuperSpeed USB device number 7 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c470 2. when auto-mount works: kernel: [ 124.313084] usb 2-2.3.3: USB disconnect, device number 5 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_disconnected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b9dea0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_removed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c330 kernel: [ 136.531496] usb 2-2.3.3: new SuperSpeed USB device number 6 using xhci_hcd org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_changed org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: drive_connected org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1bd6810 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: volume_added org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: emit_signal: 0x1b8c3d0 org.gtk.vfs.UDisks2VolumeMonitor[2116]: ### debug: in handle_volume_mount udisksd[2274]: Mounted /dev/sda1 at /media/u/U on behalf of uid 1001 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824073/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825250] Re: ethmonitor does not list interfaces without assigned IP address
** Bug watch added: Debian Bug tracker #927311 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927311 ** Also affects: resource-agents (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927311 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825250 Title: ethmonitor does not list interfaces without assigned IP address Status in resource-agents package in Ubuntu: Confirmed Status in resource-agents source package in Xenial: Confirmed Status in resource-agents source package in Bionic: Confirmed Status in resource-agents source package in Cosmic: Confirmed Status in resource-agents package in Debian: Unknown Bug description: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f1 [Test Case] 1) Ensure there's a network interface without an assigned IP address. For example, virbr0-nic will be created automatically by uvt-kvm: # ip addr show dev virbr0-nic 11: virbr0-nic: mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e9:5e:af brd ff:ff:ff:ff:ff:ff 2) Install pcs+arping and create a new ethmonitor resource with the target interface: # sudo apt update && sudo apt install pcs arping -y # pcs resource create p_nic ocf:heartbeat:ethmonitor interface=virbr0-nic op monitor timeout="10s" 3) Debug-start ethmonitor resource and check for "Interface does not exist messages" # pcs resource debug-start p_nic Operation start for p_nic (ocf:heartbeat:ethmonitor) returned: 'ok' (0) > stderr: WARNING: Interface virbr0-nic does not exist > stderr: NOTICE: link_status: DOWN [Regression Potential] The regression potential is low, since we are relaxing the monitoring conditions for interfaces without an assigned IP address. The patches have been tested against Travis-CI before being merged upstream, and will be tested against autopkgtest for each target distro. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1825250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1825250] [NEW] ethmonitor does not list interfaces without assigned IP address
Public bug reported: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f1 [Test Case] 1) Ensure there's a network interface without an assigned IP address. For example, virbr0-nic will be created automatically by uvt-kvm: # ip addr show dev virbr0-nic 11: virbr0-nic: mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:e9:5e:af brd ff:ff:ff:ff:ff:ff 2) Install pcs+arping and create a new ethmonitor resource with the target interface: # sudo apt update && sudo apt install pcs arping -y # pcs resource create p_nic ocf:heartbeat:ethmonitor interface=virbr0-nic op monitor timeout="10s" 3) Debug-start ethmonitor resource and check for "Interface does not exist messages" # pcs resource debug-start p_nic Operation start for p_nic (ocf:heartbeat:ethmonitor) returned: 'ok' (0) > stderr: WARNING: Interface virbr0-nic does not exist > stderr: NOTICE: link_status: DOWN [Regression Potential] The regression potential is low, since we are relaxing the monitoring conditions for interfaces without an assigned IP address. The patches have been tested against Travis-CI before being merged upstream, and will be tested against autopkgtest for each target distro. ** Affects: resource-agents (Ubuntu) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Affects: resource-agents (Ubuntu Xenial) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Affects: resource-agents (Ubuntu Bionic) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Affects: resource-agents (Ubuntu Cosmic) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Affects: resource-agents (Debian) Importance: Unknown Status: Unknown ** Tags: sts ** Also affects: resource-agents (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: resource-agents (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: resource-agents (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: resource-agents (Ubuntu Xenial) Status: New => Confirmed ** Changed in: resource-agents (Ubuntu Bionic) Status: New => Confirmed ** Changed in: resource-agents (Ubuntu Cosmic) Status: New => Confirmed ** Changed in: resource-agents (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: resource-agents (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: resource-agents (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: resource-agents (Ubuntu Xenial) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: resource-agents (Ubuntu Cosmic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: resource-agents (Ubuntu Bionic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1825250 Title: ethmonitor does not list interfaces without assigned IP address Status in resource-agents package in Ubuntu: Confirmed Status in resource-agents source package in Xenial: Confirmed Status in resource-agents source package in Bionic: Confirmed Status in resource-agents source package in Cosmic: Confirmed Status in resource-agents package in Debian: Unknown Bug description: [Impact] Some network interfaces will not be monitored by ethmonitor [Description] The is_interface() function in ethmonitor tries to match an interface to a list obtained from the 'ip' tool. It lists interfaces using the 'inet' family, which omits interfaces that don't have an IP address assigned. If the interface that we're looking for is e.g. a VLAN bridge that does not have an IP address, it won't show up in the listing and is_interface() will return false. ethmonitor will miss that interface, and it won't be available for monitoring. Upstream commits: - https://github.com/ClusterLabs/resource-agents/commit/40d05029ce0b - https://github.com/ClusterLabs/resource-agents/commit/c0ac191c73f
[Group.of.nepali.translators] [Bug 1821250] Re: Drop setuid bit from /bin/ntfs-3g
This bug was fixed in the package ntfs-3g - 1:2017.3.23-2ubuntu0.18.10.2 --- ntfs-3g (1:2017.3.23-2ubuntu0.18.10.2) cosmic-security; urgency=medium * Fix LP: #1821250 - Don't install /bin/ntfs-3g as setuid root. If administrators want to allow unprivileged users to be able to mount NTFS images, they can restore this functionality by changing the permissions of /bin/ntfs-3g with dpkg-statoverride - update debian/ntfs-3g.postinst -- Chris Coulson Thu, 21 Mar 2019 21:23:27 + ** Changed in: ntfs-3g (Ubuntu Cosmic) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1821250 Title: Drop setuid bit from /bin/ntfs-3g Status in ntfs-3g package in Ubuntu: Fix Released Status in ntfs-3g source package in Xenial: Fix Released Status in ntfs-3g source package in Bionic: Fix Released Status in ntfs-3g source package in Cosmic: Fix Released Bug description: /bin/ntfs-3g has been installed as setuid-root since xenial, but this is discouraged upstream (see https://www.tuxera.com/community/ntfs-3g- faq/#useroption) and recently contributed to CVE-2019-9755 (https://usn.ubuntu.com/3914-1/). As a hardening improvement, this should not be setuid. [ Test case ] Upgrade ntfs-3g and then mount, use and unmount your NTFS volumes as usual. [ Regression potential ] This does break one use-case - unprivileged users will not be able to mount NTFS image files. Based on discussions offline, we think this is an edge case and consider it to be an acceptable trade-off. As far as I'm aware, there are no other use-cases that are broken by this change. It doesn't affect automounting of removable volumes or mounting of NTFS block devices (which unprivileged users can't mount anyway). Administrators that want to allow unprivileged users to mount NTFS image files can change the permissions of /bin/ntfs-3g using dpkg-statoverride. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1821250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1821250] Re: Drop setuid bit from /bin/ntfs-3g
This bug was fixed in the package ntfs-3g - 1:2017.3.23-2ubuntu0.18.04.2 --- ntfs-3g (1:2017.3.23-2ubuntu0.18.04.2) bionic-security; urgency=medium * Fix LP: #1821250 - Don't install /bin/ntfs-3g as setuid root. If administrators want to allow unprivileged users to be able to mount NTFS images, they can restore this functionality by changing the permissions of /bin/ntfs-3g with dpkg-statoverride - update debian/ntfs-3g.postinst -- Chris Coulson Thu, 21 Mar 2019 21:33:01 + ** Changed in: ntfs-3g (Ubuntu Bionic) Status: New => Fix Released ** Changed in: ntfs-3g (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1821250 Title: Drop setuid bit from /bin/ntfs-3g Status in ntfs-3g package in Ubuntu: Fix Released Status in ntfs-3g source package in Xenial: Fix Released Status in ntfs-3g source package in Bionic: Fix Released Status in ntfs-3g source package in Cosmic: Fix Released Bug description: /bin/ntfs-3g has been installed as setuid-root since xenial, but this is discouraged upstream (see https://www.tuxera.com/community/ntfs-3g- faq/#useroption) and recently contributed to CVE-2019-9755 (https://usn.ubuntu.com/3914-1/). As a hardening improvement, this should not be setuid. [ Test case ] Upgrade ntfs-3g and then mount, use and unmount your NTFS volumes as usual. [ Regression potential ] This does break one use-case - unprivileged users will not be able to mount NTFS image files. Based on discussions offline, we think this is an edge case and consider it to be an acceptable trade-off. As far as I'm aware, there are no other use-cases that are broken by this change. It doesn't affect automounting of removable volumes or mounting of NTFS block devices (which unprivileged users can't mount anyway). Administrators that want to allow unprivileged users to mount NTFS image files can change the permissions of /bin/ntfs-3g using dpkg-statoverride. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1821250/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1821760] Re: CVE-2019-9917 - Invalid encoding crash
This bug was fixed in the package znc - 1.7.1-2ubuntu0.1 --- znc (1.7.1-2ubuntu0.1) cosmic-security; urgency=medium * SECURITY UPDATE: Fix DoS while using an invalid encoding (LP: #1821760) - debian/patches/CVE-2019-9917.patch: Don't crash if user specified invalid encoding. - CVE-2019-9917 -- Paulo Flabiano Smorigo Mon, 08 Apr 2019 10:56:22 -0300 ** Changed in: znc (Ubuntu Cosmic) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-9917 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1821760 Title: CVE-2019-9917 - Invalid encoding crash Status in znc package in Ubuntu: Fix Released Status in znc source package in Xenial: New Status in znc source package in Bionic: New Status in znc source package in Cosmic: Fix Released Status in znc source package in Disco: Fix Released Bug description: Hello. ZNC is affected by CVE-2019-9917, in which the use of an invalid encoding can cause a crash. This is fixed upstream in the following code commit: https://github.com/znc/znc/commit/64613bc8b6b4adf1e32231f9844d99cd512b8973 This has not yet been released into a stable ZNC version, but the fix is made available in Debian as 1.7.2-2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1821760/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822692] Re: Please ship the ib_uverbs driver module in the main modules package
** Also affects: linux-aws (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822692 Title: Please ship the ib_uverbs driver module in the main modules package Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws source package in Trusty: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Cosmic: Fix Committed Status in linux-aws source package in Disco: Fix Released Bug description: Please include the module drivers/infiniband/core/ib_uverbs.ko and its companion ib_umad.ko in the main linux-modules-*-aws package, in order to support upcoming Amazon features. +++ b/debian.aws/control.d/aws.inclusion-list +drivers/infiniband/core/ib_umad.ko +drivers/infiniband/core/ib_uverbs.ko To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1822692/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Testing phase-changed: Wednesday, 17. April 2019 09:09 UTC reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected channel(s): - arch=amd64:channel=latest/candidate:rev=67' -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1824774 Title: linux-aws: 4.4.0-1081.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Fix Released Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Testing phase-changed: Wednesday, 17. April 2019 09:09 UTC reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824774/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Testing phase-changed: Wednesday, 17. April 2019 09:09 UTC reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/beta' - snap-release-to-edge: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/edge' + snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected channel(s): + arch=amd64:channel=latest/candidate:rev=67' -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1824774 Title: linux-aws: 4.4.0-1081.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Testing phase-changed: Wednesday, 17. April 2019 09:09 UTC reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-candidate: 'Pending -- snap aws-kernel not in expected channel(s): arch=amd64:channel=latest/candidate:rev=67' To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824774/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker
4.4.0-146.172 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) svm (bug 1821903) debug (bug 1821906) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) sync_file_range02 (bug 1819116) xfstests - xfs generic/475 timed out 48 / 49 tests were run, missing: xfstests Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2-ipi and gicv2-active on starmie ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) sync_file_range02 (bug 1819116) Issue to note in i386: ubuntu_btrfs_kernel_fixes - aa9ddcd4 on 4.4 i386 (bug 1821913) e755f780 on 4.4 i386 (bug 1822560) ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) sync_file_range02 (bug 1819116) xfstests - xfs generic/308 timed out (bug 1738152) Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) ubuntu_lxc - xfstests - btrfs generic/176 timed out Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) sync_file_range02 (bug 1819116) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) Issue to note in s390x (zVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - unable to insert test_bpf on Xenial s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1812189) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify07/fanotify08 timeouted (bug 1775165) fanotify09 timeouted (bug 1775153) fanotify10 timeouted (bug 1802454) fanotify11 timeouted (bug 1808107) sync_file_range02 (bug 1819116) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) Note: Missing s390x KVM test result due to bug 1825099 ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822834 Title: linux: 4.4.0-146.172 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-t
[Group.of.nepali.translators] [Bug 1816642] Re: SRU of LXC 2.0.11
This bug was fixed in the package lxc - 2.0.11-0ubuntu1~16.04.3 --- lxc (2.0.11-0ubuntu1~16.04.3) xenial; urgency=medium * Cherry-pick upstream bugfix (fixes regression on attach with uid/gid): - attach: improve id switching - utils: make id switching functions return bool lxc (2.0.11-0ubuntu1~16.04.2) xenial; urgency=medium * Use clean LDFLAGS when building the static init.lxc, otherwise we end up with broken binaries on some architectures. lxc (2.0.11-0ubuntu1~16.04.1) xenial; urgency=medium * New upstream bugfix release (2.0.11) (LP: #1816642) - Security fix for CVE-2018-6556 (affecting 2.0.9+) - Mitigation for CVE-2019-5736 - Full changelog available at: https://discuss.linuxcontainers.org/t/lxc-2-0-11-has-been-released/4238 -- Stéphane Graber Tue, 09 Apr 2019 13:58:10 -0400 ** Changed in: lxc (Ubuntu Xenial) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-6556 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-5736 -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: Fix Released Status in lxc source package in Xenial: Fix Released Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc
[Group.of.nepali.translators] [Bug 1816642] Re: SRU of LXC 2.0.11
This bug was fixed in the package golang-gopkg-lxc-go-lxc.v2 - 0.0~git20161126.1.82a07a6-0ubuntu1~ubuntu16.04.2 --- golang-gopkg-lxc-go-lxc.v2 (0.0~git20161126.1.82a07a6-0ubuntu1~ubuntu16.04.2) xenial; urgency=medium * Cherry-pick fixes from recent go-lxc (LP: #1816642): - Actually start the container in shutdown test - Make sure the container has a config when calling Execute() -- Stéphane Graber Tue, 09 Apr 2019 14:14:00 -0400 ** Changed in: golang-gopkg-lxc-go-lxc.v2 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1816642 Title: SRU of LXC 2.0.11 Status in golang-gopkg-lxc-go-lxc.v2 package in Ubuntu: Fix Released Status in lxc package in Ubuntu: Fix Released Status in golang-gopkg-lxc-go-lxc.v2 source package in Trusty: Triaged Status in lxc source package in Trusty: Triaged Status in golang-gopkg-lxc-go-lxc.v2 source package in Xenial: Fix Released Status in lxc source package in Xenial: Fix Released Bug description: LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch. This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the changelog for both of them can be found below: LXC 2.0.11: - autotools: handle getgrgid_r on bionic - autotools: add memory_utils.h to Makefile.am - change version to 2.0.11 in configure.ac LXC 2.0.10: - tools: allow lxc-attach to undefined containers - utils: move memfd_create() definition - utils: add lxc_cloexec() - utils: add lxc_make_tmpfile() - utils: add lxc_getpagesize() - utils: add lxc_safe_long_long() - utils: parse_byte_size_string() - utils: add lxc_find_next_power2() - namespace: use lxc_getpagesize() - lxc-debian: allow creating `testing` and `unstable` - Call lxc_config_define_load from lxc_execute again - Fix typo in lxc-net script - Add missing lxc_container_put - lxc-debian: don't write C.* locales to /etc/locale.gen - attach: correctly handle namespace inheritance - cgfsng: fix cgroup2 detection - cgroups: enable container without CAP_SYS_ADMIN - lxc-start: remove unnecessary checks - start: close non-needed file descriptors - handler: make name argument const - start: close data socket in parent - monitor: do not log useless warnings - network: reap child in all cases - conf: reap child in all cases - storage: switch to ext4 as default filesystem - tools: fix help output of lxc-create - attach: handle namespace inheritance - cgroups/cgfsng: keep mountpoint intact - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown() - cgroups/cgfsng: support MS_READONLY with cgroup ns - log: check for i/o error with vsnprintf() - cgroupfs/cgfsng: tweak logging - cgroups/cgfsng: remove is_lxcfs() - cgroups/cgfsng: fix get_controllers() for cgroup2 - cgroupfs/cgfsng: improve cgroup2 handling - config: remove SIGRTMIN+14 as lxc.signal.stop - commands: non-functional changes - console: non-functional changes - console: non-functional changes - lxc-test-unpriv: fix the overlayfs mount error - attach: allow attach with empty conf - tools/lxc_attach: removed api logging - console: fix console info message - Add missing dependency libunistring - cgroups/cgfsng: adapt to new cgroup2 delegation - console: report detach message on demand - lxccontainer: enable daemonized app containers - console: use correct escape sequence check - console: prepare for generic signal handler - console: exit mainloop on SIGTERM - commands: non-functional changes - lxccontainer: non-functional changes - commands: fix state socket implementation - lxc_init: set the control terminal in the child session - lxc-test-unpriv: check user existence before removing it - Fixed typo on lxc.spec.in - conf: move CAP_SYS_* definitions to utils.h - start.c: always switch uid and gid - Use AX_PTHREAD config script to detect pthread api - utils.h: Avoid duplicated sethostname implementation - tools/lxc_cgroup: remove internal logging - tools/lxc_autostart: remove internal logging - tools/lxc_clone: remove internal logging - tools/lxc_console: remove internal logging - tools/lxc_create: remove internal logging - tools/lxc_destroy: remove internal logging - tools/lxc_device: remove internal logging - tools/lxc_execute: removed internal logging - tools/lxc_freeze: remove internal logging - tools/lxc_info: removed internal logging - criu: detect veth name - lxccontainer: various container creation fixes - storage: remove unused declaration - tools/lxc_ls: remove internal logging - tools/lxc_copy: remove internal logging - tools/lxc_monitor: removed internal logging - tools/lxc_snapshot: rem
[Group.of.nepali.translators] [Bug 1824774] Re: linux-aws: 4.4.0-1081.91 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1824774 Title: linux-aws: 4.4.0-1081.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822834 phase: Promote to Proposed phase-changed: Tuesday, 16. April 2019 16:32 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1824774/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
