[Group.of.nepali.translators] [Bug 1882770] Re: xenial/linux: 4.4.0-185.215 -proposed tracker
Kernel deb testing completes, no regressions found. Ready for Updates. Results here: https://trello.com/c/rieYTc48/580-xenial-linux- image-440-185-generic-440-185215 ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => 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/1882770 Title: xenial/linux: 4.4.0-185.215 -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: Fix Released 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-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Updates phase-changed: Friday, 03. July 2020 05:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: trusty/linux-aws: bug 1882768 trusty/linux-lts-xenial: bug 1882769 xenial/linux-aws: bug 1882759 xenial/linux-cascade: bug 1882761 xenial/linux-fips: bug 1882767 xenial/linux-kvm: bug 1882762 xenial/linux-raspi2: bug 1882764 xenial/linux-snapdragon: bug 1882766 xenial/linux/caracalla-kernel: bug 1882755 xenial/linux/pc-kernel: bug 1882756 xenial/linux/stlouis-kernel: bug 1882757 variant: debs versions: main: 4.4.0-185.215 meta: 4.4.0.185.191 signed: 4.4.0-185.215 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882770/+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 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
cat /var/lib/snapd/state.json | jq .data.auth.users ^ this would be interesting to see as my understanding is that this being "null" means managed is false whereas if it shows something, then managed is true ** Changed in: snapd Status: New => Invalid -- 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/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation Status in snapd: Invalid Status in subiquity: In Progress Status in subiquity package in Ubuntu: Invalid Status in subiquity source package in Xenial: Confirmed Status in subiquity source package in Bionic: Confirmed Bug description: when seeding appliance images with lxd, user creation gets impossible. console-conf skips the user creation, system-user assertions do not work either because there is already a user exisiting in the image. the tty screen shows instructions to log in with "lxd@" ... since the lxd user is a special case hack in Ubuntu Core images, "snap create-user ..." should probably learn to ignore its existence ... To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+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 1881588] Re: pre-seeding lxd on Core appliances breaks console-conf user creation
Let's re-open the snapd side of this then. ** Changed in: snapd Status: Invalid => 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/1881588 Title: pre-seeding lxd on Core appliances breaks console-conf user creation Status in snapd: New Status in subiquity: In Progress Status in subiquity package in Ubuntu: Invalid Status in subiquity source package in Xenial: Confirmed Status in subiquity source package in Bionic: Confirmed Bug description: when seeding appliance images with lxd, user creation gets impossible. console-conf skips the user creation, system-user assertions do not work either because there is already a user exisiting in the image. the tty screen shows instructions to log in with "lxd@" ... since the lxd user is a special case hack in Ubuntu Core images, "snap create-user ..." should probably learn to ignore its existence ... To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1881588/+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 1864233] Re: Commits to resolve high network latency
** Changed in: linux-azure-4.15 (Ubuntu)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu)
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/1864233
Title:
Commits to resolve high network latency
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-4.15 source package in Xenial:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Released
Bug description:
An issue has been identified with the NETVSC driver on Azure VMs. This
issues has been fixed by four patches, which are available in the
mainline kernel.
The issues is the following:
Outgoing traffic is sent from the guest to the Azure host over multiple
parallel channels. The issue causes the traffic to be unevenly balanced across
the channels, which results in a physical CPU on the Azure host becoming
overloaded. In turn, the network traffic on the overloaded channel experiences
significantly higher latency. This higher latency is causing issues for
customers.
This issue is resolved by the following four mainline commits:
71f21959dd55 ("hv_netvsc: Fix offset usage in netvsc_send_table()")
171c1fd98df3 ("hv_netvsc: Fix send_table offset in case of a host bug")
c39ea5cba5a2 ("hv_netvsc: Fix tx_table init in rndis_set_subchannel()")
b0689faa8efc ("hv_netvsc: Fix unwanted rx_table reset")
These four commits have been submitted to upstream stable.
We would like to request these commits in Azure kernels for Xenial and
Bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1864233/+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 1885511] Re: xenial/linux-fips: 4.4.0-1043.48 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Packaging - phase-changed: Thursday, 02. July 2020 20:31 UTC + phase: Building in ppa + phase-changed: Friday, 03. July 2020 02:27 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded - prepare-package-signed: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building variant: debs + versions: + main: 4.4.0-1043.48 + meta: 4.4.0.1043.45 + signed: 4.4.0-1043.48 -- 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/1885511 Title: xenial/linux-fips: 4.4.0-1043.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid 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: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Building in ppa phase-changed: Friday, 03. July 2020 02:27 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building variant: debs versions: main: 4.4.0-1043.48 meta: 4.4.0.1043.45 signed: 4.4.0-1043.48 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1885511/+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 1885508] Re: xenial/linux-raspi2: 4.4.0-1136.145 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Packaging - phase-changed: Wednesday, 01. July 2020 22:21 UTC + phase: Building in ppa + phase-changed: Friday, 03. July 2020 02:09 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-raspi2/pi2-kernel: bug 1885507 variant: debs + versions: + main: 4.4.0-1136.145 + meta: 4.4.0.1136.136 -- 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/1885508 Title: xenial/linux-raspi2: 4.4.0-1136.145 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: New 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Building in ppa phase-changed: Friday, 03. July 2020 02:09 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-raspi2/pi2-kernel: bug 1885507 variant: debs versions: main: 4.4.0-1136.145 meta: 4.4.0.1136.136 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1885508/+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 1840789] Re: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
This fix has already been released as part of the kernel stable updates.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu Xenial)
Status: Opinion => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => 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/1840789
Title:
bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* The bnx2x driver may cause hardware faults (leading to
panic/reboot) and other behaviors as transmit timeouts,
after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
introduced.
* This issue has been observed by an user shortly
after starting docker & kubelet, with adapters:
- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
* If options to ignore hardware faults are used
(erst_disable=1 hest_disable=1 ghes.disable=1)
the system doesn't panic/reboot and continues
on to timeout on adapter stats, then transmit
timeouts, spewing some adapter firmware dumps,
but the network interface is non-functional.
* The issue only happened when LLDP is enabled
on the network switches, and crashdump shows
the bnx2x driver is stuck/waits for firmware
to complete the stop traffic command in LLDP
handling. Workaround used is to disable LLDP
in the network switches/ports.
* Analysis of the driver and firmware dumps
didn't help significantly towards finding
the root cause.
* Upstream/mainline recently just reverted the
patch, due to similar problem reports, while
looking for the root cause/proper fix.
[Test Case]
* No reproducible test case found outside
the user's systems/cluster, where it is
enough to start docker & kubelet & wait.
* The user verified test kernels for Xenial
and Bionic - the problem does not happen;
build-tested on Disco.
[Regression Potential]
* Users who significantly use/apply the non-default
traffic class (tc) / class of service (cos) might
possibly see performance changes (if any at all)
in such applications, however that's unclear now.
* This is a recent revert upstream (v5.3-rc'ish),
so there's chance things might change in this area.
* Nonetheless, the patch is authored by the driver
vendor, and made its way into stable kernels
(e.g., v5.2.8 which made Eoan/19.10 recently).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840789/+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 1800873] Re: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-line
** Changed in: makedumpfile (Ubuntu Disco) Status: Confirmed => Won't Fix -- 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/1800873 Title: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command- line Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Trusty: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Cosmic: Confirmed Status in makedumpfile source package in Disco: Won't Fix Bug description: Currently kdump has an useful option to append parameters to the kdump kernel command-line, "KDUMP_CMDLINE_APPEND". Would be useful to have a reciprocal option which users could use to remove parameters without needing to rewrite the whole line. The option name proposed here is KDUMP_CMDLINE_REMOVE, which would tentatively "sed"-out the options from the kernel command-line before appending the new ones from KDUMP_CMDLINE_APPEND. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800873/+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 1842159] Re: Please suggest running apt update & apt upgrade in MOTD when list of available packages is old
** Changed in: update-notifier (Ubuntu Disco) Status: New => Won't Fix -- 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/1842159 Title: Please suggest running apt update & apt upgrade in MOTD when list of available packages is old Status in update-notifier package in Ubuntu: Fix Released Status in update-notifier source package in Xenial: New Status in update-notifier source package in Bionic: New Status in update-notifier source package in Disco: Won't Fix Status in update-notifier source package in Eoan: Fix Released Bug description: [Impact] * Users don't have up to date information about available updates when network connectivity or other issues prevented automated apt updates. * It is desired to give the user accurate and up to date information about available updates or warn them if the information is outdated. * The fix notifies user about stale updates information in MOTD [Test Case] * Install update-motd and the the fixed package. * Observe the output of sudo update-motd printing the usual output * "Date back" the updates information: $ sudo touch -t 01010101 /var/lib/update-notifier/updates-available * Observe the output of sudo update-motd printing warning about outdated update information. * Remove the updates information: $ sudo rm /var/lib/update-notifier/updates-available * Observe the output of sudo update-motd printing warning about outdated update information. [Regression Potential] * An error may be printed in MOTD or the warning message may appear needlessly in case of making a mistake in implementing the fix. [Original Bug Text] When logging into a system where the package list is not updated for long time (for example because is offline) I may see: ... 0 updates can be installed immediately. 0 of these updates are security updates. .. Which is true, but the user may think that there are no available updates released. Also, if the /var/lib/update-notifier/updates-available is missing (which can happen due to network connectivity issues of due to bugs) there is no mention of updates in MOTD. If the /var/lib/update-notifier/updates-available is older than a few days (weeks?) or it is missing and the packages list is older than a few days (weeks?) please recommend running apt update & upgrade in the MOTD snippet: ... The list of available updates is not refreshed in N days. Please run "sudo apt update" and then "sudo apt upgrade" to keep your system up to date. ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1842159/+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 1845162] Re: test bug
** Changed in: vis (Ubuntu Disco) Status: New => Won't Fix -- 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/1845162 Title: test bug Status in vis package in Ubuntu: Invalid Status in vis source package in Xenial: New Status in vis source package in Bionic: New Status in vis source package in Disco: Won't Fix Status in vis source package in Eoan: Invalid Bug description: test bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vis/+bug/1845162/+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 1844245] Re: Integrate Intel SGX driver into linux-azure
** Changed in: linux-azure (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux-azure source package in Eoan: Fix Released Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844245/+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 1841191] Re: "error: failed to acquire package cache lock" in sbuild
** Changed in: cargo (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1841191 Title: "error: failed to acquire package cache lock" in sbuild Status in cargo package in Ubuntu: Fix Released Status in cargo source package in Xenial: Fix Committed Status in cargo source package in Bionic: Fix Committed Status in cargo source package in Disco: Won't Fix Bug description: [Impact] All packages using cargo (rust's package manager) to build in Launchpad will FTBFS because cargo tries to acquire a lock on $HOME/.cargo, but $HOME is set to /sbuild-nonexistent in sbuild. This includes the thunderbird 60.9.1+build1 SRU tracked by bug #1850651. [Test Case] In a xenial/disco virtual machine: sudo apt install cargo cd `mktemp -d` export HOME=/nonexistent cargo init --name foobar cargo build This should succeed. With the unpatched version currently in xenial/disco, it fails with "error: failed to acquire package cache lock". [Regression Potential] Low. This cherry-picks one single upstream commit that addresses only this bug. [Original Description] Upstream issue: https://github.com/rust-lang/cargo/issues/7147 This breaks firefox and thunderbird builds in eoan: export CARGO_HOME=/<>/thunderbird-68.0+build4/third_party/cbindgen/.cargo; \ cargo install --path . --bin cbindgen --root ../../cbindgen error: failed to acquire package cache lock Caused by: failed to open: /sbuild-nonexistent/.cargo/.package-cache Caused by: Permission denied (os error 13) The following commit needs to be backported as a distro patch: https://github.com/rust- lang/cargo/commit/2b21fa68368f13b43f4c34886116df2e1b9d276e ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cargo 0.37.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Fri Aug 23 14:24:46 2019 SourcePackage: cargo UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cargo/+bug/1841191/+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 1840375] Re: groupdel doesn't support extrausers
** Changed in: shadow (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Won't Fix
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
1. install the libnss-extrausers and add "extrauers" to the passwd and shadow
line (see /usr/share/doc/libnss-extrausers/README for the modifications in
sswitch.conf)
2. run "groupadd --extrausers foo" and verify "grep foo
/var/lib/extrausers/group"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Fix Released Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure
** Changed in: linux-azure (Ubuntu Disco) Status: New => Won't Fix -- 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/1813211 Title: Allow I/O schedulers to be loaded with modprobe in linux-azure Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: Won't Fix Bug description: There was a previous request in bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit the IO scheduler to NOOP in linux-azure. The other schedulers were turned off and NOOP was made the default. However with new upstream releases, new schedulers where added and linux-azure inherited the default config value for them from the master kernel. That's why there are some IO schedulers built as modules in the extra package (mq-deadline and kyber-iosched). In order to use those two modules, one needs to install the -extra package and modprobe the modules first: # tail /sys/block/sd*/queue/scheduler ==> /sys/block/sda/queue/scheduler <== [none] ==> /sys/block/sdb/queue/scheduler <== [none] # apt install linux-modules-extra-4.15.0-1036-azure # modprobe kyber-iosched # tail /sys/block/sd*/queue/scheduler ==> /sys/block/sda/queue/scheduler <== [none] kyber ==> /sys/block/sdb/queue/scheduler <== [none] kyber # modprobe mq-deadline # tail /sys/block/sd*/queue/scheduler ==> /sys/block/sda/queue/scheduler <== [none] kyber mq-deadline ==> /sys/block/sdb/queue/scheduler <== [none] kyber mq-deadline The schedulers cfq and deadline have been completely disabled in LP bug #1671203 so they cannot be added with modprobe. This is a request to move back the cfq and deadline schedulers along with the mq-deadline and kyber-iosched schedulers to the main linux- azure package (in other words, not in the -extra package) and allow the users to be able to modprobe the schedulers when needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+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 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM kernels
** Changed in: linux-kvm (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1812176
Title:
psock_tpacket from the net test in ubuntu_kernel_selftests failed on
KVM kernels
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux-kvm source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-kvm source package in Bionic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Status in linux-kvm source package in Disco:
Won't Fix
Bug description:
The psock_tpacket in the net test from ubuntu_kernel_selftests failed with
B-KVM
$ sudo ./psock_tpacket
test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
Look into the code, it seems that this file not found error is caused
by the attempt to access /proc/kallsyms in test_kernel_bit_width():
static int test_kernel_bit_width(void)
{
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;
fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 08:05:47 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812176/+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 1885511] Re: xenial/linux-fips: 4.4.0-1043.48 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Packaging - phase-changed: Wednesday, 01. July 2020 13:50 UTC + phase: Packaging + phase-changed: Thursday, 02. July 2020 20:31 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- tag not published and package not + uploaded + prepare-package-meta: Pending -- tag not published and package not + uploaded + prepare-package-signed: Pending -- tag not published and package not + uploaded variant: debs -- 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/1885511 Title: xenial/linux-fips: 4.4.0-1043.48 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Packaging phase-changed: Thursday, 02. July 2020 20:31 UTC reason: prepare-package: Pending -- tag not published and package not uploaded prepare-package-meta: Pending -- tag not published and package not uploaded prepare-package-signed: Pending -- tag not published and package not uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1885511/+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 1815237] Re: stop shipping "update-pciids" in /usr/sbin
** Changed in: pciutils (Ubuntu Disco) Status: In Progress => Won't Fix -- 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/1815237 Title: stop shipping "update-pciids" in /usr/sbin Status in pciutils package in Ubuntu: In Progress Status in pciutils source package in Precise: Invalid Status in pciutils source package in Trusty: In Progress Status in pciutils source package in Xenial: In Progress Status in pciutils source package in Bionic: In Progress Status in pciutils source package in Cosmic: In Progress Status in pciutils source package in Disco: Won't Fix Bug description: [IMPACT] pciutils contains a script called 'update-pciids' which offer to user the possibilty to download new version of the PCI ID list from 'http:pciids.sourceforge.net/v2.2/pci.ids' and update the file '/usr/share/misc/pci.ids' accordingly. After a discussion with foundation/security about what would be the best practice between (a) simply use update-pciids script or (b) do an sru to update the list. Option (b) was unanimously judge more viable. (see the irc discussion in the [ORIG DESCRIPTION] section. That brought up another aspect, should Ubuntu keep that script available for user. Foundation/Security team ACK on moving the script to '/usr/share/doc/pciutils/examples/' The motivation behind this is the following : - Injection attack where intentionally-corrupted pci.ids data exploits something goofy in a library that reads it. - It alters a dpkg-managed file in /usr/share - Uncheck download over http - [TEST CASE] 1) Install pciutils (if not installed already) # apt-get install pciutils The package come with a pre-define pci.ids vendor list, freeze at the end time it was last SRU'd, merge, sync from Debian. If you perform a 'dmidecode' on a system with recent HW, dmidecode may not know about this new HW since the pci.ids list can have been updated before the HW exist, or got added to the upstream pci vendor list. 2) Check pci.ids (pre-update) # stat /usr/share/misc/pci.ids File: /usr/share/misc/pci.ids Size: 1062022 Blocks: 2080 IO Block: 4096 regular file Device: 10302h/66306d Inode: 8916914 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) ==> Access: 2019-03-13 16:46:34.208000193 -0400 ==> Modify: 2017-04-24 14:35:32.0 -0400 ==> Change: 2019-03-04 15:19:41.001315621 -0500 Birth: - 3) Update pci.ids # update-pciids Downloaded daily snapshot dated 2019-03-14 03:15:02 4) Check pci.ids (pre-update) # stat /usr/share/misc/pci.ids File: /usr/share/misc/pci.ids Size: 1169201 Blocks: 2288 IO Block: 4096 regular file Device: 10302h/66306d Inode: 8916466 Links: 1 Access: (0644/-rw-r--r--) Uid: (0/root) Gid: (0/root) ==> Access: 2019-03-14 03:15:02.0 -0400 ==> Modify: 2019-03-14 03:15:02.0 -0400 ==> Change: 2019-03-15 12:32:25.489581638 -0400 Birth: - At this point the pci.ids is updated. After this SRU, the above step won't be available ^. [REGRESSION POTENTIAL] User used to update their PCI vendor list using 'update-pciids' won't have it available anymore out of the box as it was before this SRU. (Unless they do the necessary manual intervention by taking the script from 'pciutils/examples' set the executable bit and run it, as user could still use that way but they have to be aware of the potential risk that may or may not come with it.) At this point, it will be at user discretion to use it or not and judge/evaluate the risk, but the package itself will no longer offer the option out of the box. We need to file a debian bug about it, but I don't know if Debian will be willing to follow our chain of thought. If not we will divert from pciutils debian package at that aspect. [OTHER INFORMATION] For more information : # man update-pciids [ORIG DESCRIPTION] [Freenode #ubuntu-release discussion] [13:51:02] vorlon, I also puzzle what would be the good practice, SRU an update of pci.ids or leave the user the decision to use update-pciids which does it automatically [13:52:13] slashd: That second option isn't a great one, for many reasons. [13:52:21] slashd: ^^ I concur [13:52:55] slashd: The two that come to mind is (a) it alters a dpkg-managed file in /usr/share and (b) it's an entirely unchecked random download over http. [13:53:17] In fact, I'm a bit shocked we even ship that script at all, or haven't at least neutered it in some way. [13:54:40] That's just begging for an injection attack where intentionally-corrupted pci.ids data exploits something goofy in a library that reads it. [13:55:00] infinity, good point [13:56:05] If we were to give that
[Group.of.nepali.translators] [Bug 1819558] Re: Snap interfaces: openvswitch interface has typo
** Changed in: gnome-software (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1819558 Title: Snap interfaces: openvswitch interface has typo Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Won't Fix Bug description: Typo'd as openvtswitch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1819558/+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 1820075] Re: [Packaging] Improve config annotations check on custom kernels
** Changed in: linux-gcp (Ubuntu Disco) Status: New => Won't Fix -- 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/1820075 Title: [Packaging] Improve config annotations check on custom kernels Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-gcp source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Released Status in linux-oracle source package in Bionic: New Status in linux-azure source package in Cosmic: Fix Released Status in linux-gcp source package in Cosmic: Fix Released Status in linux-oracle source package in Cosmic: New Status in linux-azure source package in Disco: Fix Released Status in linux-gcp source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Fix Released Bug description: [Impact] Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. The proposal is to add support for an include directive in the annotations file so custom kernels can include the annotations file from its base kernel and override policies on a config basis. [Test Case] A kernel build should complete successfully after the change. [Regression Potential] Low regression potential since that's a change on the build process that doesn't affect the final kernel that is built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+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 1817784] Re: libsas disks can have non-unique by-path names
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1817784 Title: libsas disks can have non-unique by-path names Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Bug description: [Impact] Multiple disks in a system can end up having the same BY_PATH name, making the corresponding symlinks in /dev/disk/by-path non-unique. This can result in a user performing an operation on the wrong disk, possibly resulting in data loss. [Test Case] $ ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 9 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3 Notice that there is no symlink for /dev/sdc. [Fix] ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached [Regression Risk] This may change the by-path symlinks for disks on the system. While the new name would be the correct one - users maybe relying on the incorrect version. This could result in an unbootable system, requiring manual intervention to repair. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817784/+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 1819453] Re: keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType' object
** Changed in: keystone (Ubuntu Disco)
Status: New => Won't Fix
--
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/1819453
Title:
keystone-ldap TypeError: cannot concatenate 'str' and 'NoneType'
object
Status in Ubuntu Cloud Archive:
New
Status in Ubuntu Cloud Archive mitaka series:
New
Status in Ubuntu Cloud Archive ocata series:
New
Status in Ubuntu Cloud Archive pike series:
New
Status in Ubuntu Cloud Archive queens series:
New
Status in Ubuntu Cloud Archive rocky series:
New
Status in Ubuntu Cloud Archive stein series:
New
Status in OpenStack Identity (keystone):
Incomplete
Status in keystone package in Ubuntu:
New
Status in keystone source package in Xenial:
New
Status in keystone source package in Bionic:
New
Status in keystone source package in Cosmic:
New
Status in keystone source package in Disco:
Won't Fix
Bug description:
Proposed action:
=
Key / value failed check error.
Should check key exists and warn user of bad users / continue
Bug presented by:
=
openstack user list --domain customerdata
cannot concatenate 'str' and 'NoneType' objects (HTTP 400) (Request-ID:
req-cc0e225d-d033-4dfa-aff8-7311389d4f58)
Trace:
==
(keystone.common.wsgi): 2019-03-11 12:30:47,154 ERROR cannot concatenate
'str' and 'NoneType' objects
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/keystone/common/wsgi.py", line 228,
in __call__
result = method(req, **params)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
235, in wrapper
return f(self, request, filters, **kwargs)
File "/usr/lib/python2.7/dist-packages/keystone/identity/controllers.py",
line 233, in list_users
return UserV3.wrap_collection(request.context_dict, refs, hints=hints)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
499, in wrap_collection
cls.wrap_member(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
468, in wrap_member
cls._add_self_referential_link(context, ref)
File "/usr/lib/python2.7/dist-packages/keystone/common/controller.py", line
464, in _add_self_referential_link
ref['links']['self'] = cls.base_url(context) + '/' + ref['id']
TypeError: cannot concatenate 'str' and 'NoneType' objects
Offending Data:
===
@ line 233 i put LOG.debug( pprint.pformat( refs ) )
grep -b 2 "'id': None," /varlog/keystone/keystone.log
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
--
{'domain_id': u'8ce102de5ac644288f61838f5e0f46e7',
'email': u'customerd...@cusomter.com',
'id': None,
Platform:
=
cat /etc/*-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"
NAME="Ubuntu"
VERSION="16.04.5 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.5 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/;
SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial
verions:
dpkg --list | grep keystone
ii keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Daemons
ii python-keystone 2:11.0.3-0ubuntu1~cloud0
all OpenStack identity service - Python library
ii python-keystoneauth1 2.18.0-0ubuntu2~cloud0
all authentication library for OpenStack Identity - Python 2.7
ii python-keystoneclient1:3.10.0-0ubuntu1~cloud0
all client library for the OpenStack Keystone API - Python 2.x
ii python-keystonemiddleware4.14.0-0ubuntu1.2~cloud0
all Middleware for OpenStack Identity (Keystone) - Python 2.x
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1819453/+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 1816806] Re: Update ENA driver to version 2.0.3K
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1816806
Title:
Update ENA driver to version 2.0.3K
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Bug description:
The following mainline commits are needed to update the Amazon ENA
driver to version 2.0.3K:
e76ad21d070f net: ena: fix crash during failed resume from hibernation
e1f1bd9bfbed net: ena: fix race between link up and device initalization
d9b8656da922 net: ena: update driver version from 2.0.2 to 2.0.3
All three commits are needed for {Xenial,Bionic,Cosmic}. Disco 4.19
already carries the first (e76a) so needs the other two.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816806/+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 1838796] Re: TPM event log does not contain events measured after ExitBootServices
** Changed in: linux-azure (Ubuntu Disco) Status: In Progress => Won't Fix -- 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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: In Progress Status in linux source package in Xenial: Won't Fix Status in linux-azure source package in Xenial: In Progress Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lore.kernel.org/lkml/20190520205501.177637-1-matthewgarr...@google.com/ --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+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 1832042] Re: static ip= address configuration does not end up in netplan file
** Changed in: initramfs-tools (Ubuntu Disco) Status: Confirmed => Won't Fix -- 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/1832042 Title: static ip= address configuration does not end up in netplan file Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: Confirmed Status in initramfs-tools source package in Bionic: Confirmed Status in initramfs-tools source package in Cosmic: Confirmed Status in initramfs-tools source package in Disco: Won't Fix Status in initramfs-tools source package in Eoan: Fix Released Bug description: static ip= address configuration does not end up in netplan file klibc ipconfig process ip=...:$proto and dumps the state into a file, which is then parsed to generate runtime netplan configs. For static ip configuration ipconfig parses $proto values "off" "none" "static" as the same PROTO_NONE and encodes it as PROTO="none" in the serialized state file. The function that dumps ip data (_declare_ip_info()) has keys only values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig) or "off" (as valid by the kernel). This means that netplan files generated in /run for static ip configuration are incomplete. Imho we should accept "off" "none" "static" as all valid PROTO settings for static ip configuration. [Impact] * `netplan apply` will not reapply static ip configuration as declared in ip= kernel cmdline. [Test Case] * boot with static ip configuration in the kernel cmdline, e.g. ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none Check that /run/netplan/*.yaml contains addresses stanzas. [Regression Potential] * Runtime netplan configuration will now be more complete. Meaning that static ip addresses will now persist across `netplan apply` / downing, and reupping an interface. Whilst it was intended for static ip addresses to be there, it might be unexpected that they actually work properly now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+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 1827391] Re: Japanese era Reiwa SRU
** Changed in: icu (Ubuntu Disco) Status: Confirmed => Won't Fix -- 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/1827391 Title: Japanese era Reiwa SRU Status in icu package in Ubuntu: Fix Released Status in icu source package in Precise: Confirmed Status in icu source package in Trusty: Confirmed Status in icu source package in Xenial: Confirmed Status in icu source package in Bionic: Confirmed Status in icu source package in Cosmic: Confirmed Status in icu source package in Disco: Won't Fix Status in icu source package in Eoan: Fix Released Status in icu package in Debian: Fix Released Bug description: Japanese era Reiwa SRU $ rmadison icu 4.8.1.1-3ubuntu0.7 | precise-updates 52.1-3ubuntu0.8| trusty-updates 55.1-7ubuntu0.4| xenial-updates 60.2-3ubuntu3 | bionic 60.2-6ubuntu1 | cosmic 63.1-6 | disco 63.1-6 | eoan Note reported abi break / crash of chromium at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1827391/+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 1830711] Re: If a bond interface is deleted and recreated, the gratuitous ARPs are sent with the wrong MAC address
** Changed in: keepalived (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1830711 Title: If a bond interface is deleted and recreated, the gratuitous ARPs are sent with the wrong MAC address Status in keepalived: Fix Released Status in keepalived package in Ubuntu: Triaged Status in keepalived source package in Xenial: Triaged Status in keepalived source package in Bionic: Triaged Status in keepalived source package in Disco: Won't Fix Status in keepalived source package in Eoan: Triaged Bug description: When an interface is added to a bond interface, if it is the first interface added, the MAC address of the bond interface is changed to the MAC address of the added interface. When subsequent interfaces are added, their MAC addresses are changed to that of the bond interface. Uptream issue [0] identified that if a bond interface is deleted and recreated, the gratuitous ARPs were sent with the wrong source MAC address. Upstream commit [1] updates interface MAC addresses from the netlink RTM_NEWLINK messages, so that the correct MAC address is always used. [0] https://github.com/acassen/keepalived/issues/1112 [1] https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a = Original description = As explained in the upstream bug report: https://github.com/acassen/keepalived/issues/1112 please include the fix of the commit to ubuntu LTS: https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a To manage notifications about this bug go to: https://bugs.launchpad.net/keepalived/+bug/1830711/+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 1831043] Re: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu Disco) Status: New => Won't Fix -- 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/1831043 Title: move_pages12 test from ubuntu_ltp_syscalls failed on X/B/D Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: New Status in linux source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Bug description: This is a new test case landed 8 days ago, but we already have the patch in B, and it looks like this is not failing across all the nodes: move_pages12.c:114: FAIL: move_pages failed: ENOMEM <<>> tag=move_pages12 stime=1559209337 cmdline="move_pages12" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s move_pages12.c:235: INFO: Free RAM 31883452 kB move_pages12.c:253: INFO: Increasing 2048kB hugepages pool on node 0 to 4 move_pages12.c:263: INFO: Increasing 2048kB hugepages pool on node 1 to 4 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 0 move_pages12.c:179: INFO: Allocating and freeing 4 hugepages on node 1 move_pages12.c:169: PASS: Bug not reproduced move_pages12.c:114: FAIL: move_pages failed: ENOMEM move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS move_pages12.c:81: FAIL: madvise failed: SUCCESS Summary: passed 1 failed 998 skipped 0 warnings 0 <<>> initiation_status="ok" duration=4 termination_type=exited termination_id=1 corefile=no cutime=93 cstime=474 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 30 09:29 seq crw-rw 1 root audio 116, 33 May 30 09:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu May 30 09:42:46 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1831043/+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 1832286] Re: Remote denial of service (resource exhaustion) caused by low Maximum Segment Size values
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix -- 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/1832286 Title: Remote denial of service (resource exhaustion) caused by low Maximum Segment Size values Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Won't Fix Bug description: Jonathan Looney discovered that a remote attacker could cause a denial of service (resource exhaustion) via a maliciously crafted TCP session that utilizes a low MSS value. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832286/+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 1833143] Re: CVE-2019-12816
** Changed in: znc (Ubuntu Disco) Status: Confirmed => Won't Fix -- 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/1833143 Title: CVE-2019-12816 Status in znc package in Ubuntu: Fix Released Status in znc source package in Xenial: Confirmed Status in znc source package in Bionic: Confirmed Status in znc source package in Cosmic: Confirmed Status in znc source package in Disco: Won't Fix Status in znc source package in Eoan: Fix Released Bug description: CVE-2019-12816 addresses a remote code execution and privilege escalation vulnerability. To trigger this, need to have a user already. Details on the exploit are not included here, however Upstream has a fix. Eoan has a fix in proposed (autosync). Note that this will require a No Changes Rebuild in Security for znc-backlog to go along with this, otherwise znc-backlog is not installable. Unit193 uploaded a no change rebuild for znc-backlog in Eoan. Disco is where this conflict will happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1833143/+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 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
** Changed in: linux-kvm (Ubuntu Disco)
Status: New => Won't Fix
--
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/1847816
Title:
storage autopkgtest always fails with linux-{kvm,azure,etc} kernels
that don't include scsi_debug module
Status in autopkgtest-cloud:
Fix Released
Status in linux-kvm package in Ubuntu:
New
Status in systemd package in Ubuntu:
Fix Released
Status in linux-kvm source package in Xenial:
New
Status in systemd source package in Xenial:
Fix Released
Status in linux-kvm source package in Bionic:
New
Status in systemd source package in Bionic:
Fix Released
Status in linux-kvm source package in Disco:
Won't Fix
Status in systemd source package in Disco:
Won't Fix
Status in linux-kvm source package in Eoan:
New
Status in systemd source package in Eoan:
Fix Released
Status in linux-kvm source package in Focal:
New
Status in systemd source package in Focal:
Fix Released
Bug description:
Note: this bug touches on multiple packages:
- autopkgtest-cloud: merge request open to install 'modules-extra' package
- systemd: update autopkgtest to skip test if scsi_debug module isn't
available (SRU template below is for this change)
- linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have
scsi_debug module built for this kernel
[SRU template for systemd]
[impact]
the 'storage' autopkgtest requires the 'scsi_debug' module, and if it
can't load it (and it's not built-in), the test fails. On some custom
kernels, this module is included in the new 'linux-modules-extra-*'
deb which isn't installed by default, so the test always fails when
doing a reverse-dep autopkgtest using such a kernel's meta pkg.
Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG
disabled entirely; for those kernels, it will never be possible to
load the scsi_debug module and the test should be skipped.
[test case]
run the 'storage' autopkgtest with a custom kernel that doesn't
provide the scsi_debug module in the standard linux-modules deb, or
check the autopkgtest.u.c history, for example:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz
[regression potential]
as this modifies one of the autopkgtest --setup-commands, a regression
would most likely cause immediate test failure due to failing to
install the proper linux-* debs.
For the systemd 'storage' test change, this only skips the test if the
scsi_debug module can't be loaded (and isn't already present, i.e.
loaded or built-in). Any regression potential from that is low, but
likely would involve incorrect test skips and/or missing valid
problems due to skipping the test.
[scope]
systemd in all releases needs to have its 'storage' test updated
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+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 1836987] Re: update to 18.09.8
** Changed in: docker.io (Ubuntu Disco) Status: New => Won't Fix -- 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/1836987 Title: update to 18.09.8 Status in docker.io package in Ubuntu: Fix Released Status in docker.io source package in Xenial: New Status in docker.io source package in Bionic: Fix Released Status in docker.io source package in Cosmic: New Status in docker.io source package in Disco: Won't Fix Bug description: [impact] It includes the fix for CVE-2019-13509 [test case] autopkgtests per https://wiki.ubuntu.com/DockerUpdates [regression potential] As per usual, we don't mind if the updated packages regress in some sense, that's all part of the "upstream experience" we provide for docker et al. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1836987/+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 1837823] Re: [SRU] New stable micro release 2.44
** Changed in: snapcraft (Ubuntu Disco) Status: New => Won't Fix -- 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/1837823 Title: [SRU] New stable micro release 2.44 Status in snapcraft package in Ubuntu: Fix Released Status in snapcraft source package in Xenial: New Status in snapcraft source package in Bionic: New Status in snapcraft source package in Disco: Won't Fix Status in snapcraft source package in Eoan: Fix Released Bug description: This is an SRU bug to release 2.43.1 of snapcraft which follows the guidelines defined in the wiki over at https://wiki.ubuntu.com/SnapcraftUpdates The list of bugs and features in the current release are defined at https://launchpad.net/snapcraft/+milestone/2.44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1837823/+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 1837734] Re: libnss3 reads fips_enabled flag and automatically switches to FIPS mode
** Changed in: nss (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1837734 Title: libnss3 reads fips_enabled flag and automatically switches to FIPS mode Status in nss package in Ubuntu: Fix Released Status in nss source package in Xenial: Won't Fix Status in nss source package in Bionic: Fix Committed Status in nss source package in Disco: Won't Fix Status in nss source package in Eoan: Fix Released Bug description: [IMPACT] nss is not a FIPS certified library. On a machine running FIPS enabled kernel, the library by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since libnss3 is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts libnss3 versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable libnss3 reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. libnss3 is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in standard ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nss/+bug/1837734/+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 1856949] Re: cifs: kernel NULL pointer dereference, address: 0000000000000038
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1856949
Title:
cifs: kernel NULL pointer dereference, address: 0038
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Committed
Bug description:
[Impact]
Currently when the client creates a cifsFileInfo structure for
a newly opened file, it allocates a list of byte-range locks
with a pointer to the new cfile and attaches this list to the
inode's lock list. The latter happens before initializing all
other fields, e.g. cfile->tlink. Thus a partially initialized
cifsFileInfo structure becomes available to other threads that
walk through the inode's lock list. One example of such a thread
may be an oplock break worker thread that tries to push all
cached byte-range locks. This causes NULL-pointer dereference
in smb2_push_mandatory_locks() when accessing cfile->tlink:
[598428.945633] BUG: kernel NULL pointer dereference, address:
0038
...
[598428.945749] Workqueue: cifsoplockd cifs_oplock_break [cifs]
[598428.945793] RIP: 0010:smb2_push_mandatory_locks+0xd6/0x5a0 [cifs]
...
[598428.945834] Call Trace:
[598428.945870] ? cifs_revalidate_mapping+0x45/0x90 [cifs]
[598428.945901] cifs_oplock_break+0x13d/0x450 [cifs]
[598428.945909] process_one_work+0x1db/0x380
[598428.945914] worker_thread+0x4d/0x400
[598428.945921] kthread+0x104/0x140
[598428.945925] ? process_one_work+0x380/0x380
[598428.945931] ? kthread_park+0x80/0x80
[598428.945937] ret_from_fork+0x35/0x40
[Test Case]
TBD.
[Fix]
Backport commit 6f582b273ec23332074d970a7fb25bef835df71f ("CIFS: Fix
NULL-pointer dereference in smb2_push_mandatory_locks")
[Regression Potential]
Low. The patch is fairly simple and it's tagged for stable kernels. In
fact it is already in some of the released upstream stable kernels.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949/+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 1862114] Re: pty03 from pty in ubuntu_ltp failed on Eoan
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1862114 Title: pty03 from pty in ubuntu_ltp failed on Eoan Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Bug description: == Justification == The test case pty03 from pty in ubuntu_ltp is failing with kernel NULL pointer dereference: [ 951.306823] BUG: kernel NULL pointer dereference, address: 0020 [ 951.309960] #PF: supervisor write access in kernel mode [ 951.312130] #PF: error_code(0x0002) - not-present page [ 951.314227] PGD 0 P4D 0 [ 951.315278] Oops: 0002 [#1] SMP PTI [ 951.316705] CPU: 1 PID: 39102 Comm: pty03 Not tainted 5.4.0-12-generic #15-Ubuntu [ 951.319737] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [ 951.322713] RIP: 0010:queue_work_on+0x1b/0x50 [ 951.352494] Call Trace: [ 951.353244] slip_write_wakeup+0x25/0x30 [slip] [ 951.354600] tty_wakeup+0x5b/0x70 [ 951.355539] pty_unthrottle+0x19/0x30 [ 951.356560] tty_unthrottle+0x42/0x60 [ 951.357566] __tty_perform_flush+0x87/0x90 [ 951.358768] n_tty_ioctl_helper+0xcc/0x150 [ 951.359955] n_tty_ioctl+0x2d/0x100 [ 951.360930] tty_ioctl+0x3c0/0x8e0 [ 951.361882] ? __switch_to_asm+0x34/0x70 [ 951.363049] ? __switch_to_asm+0x40/0x70 [ 951.364191] ? __switch_to_asm+0x34/0x70 [ 951.365261] ? __switch_to_asm+0x40/0x70 [ 951.366382] ? __switch_to_asm+0x34/0x70 [ 951.367452] ? __switch_to_asm+0x40/0x70 [ 951.368523] ? __switch_to_asm+0x34/0x70 [ 951.369693] ? __switch_to_asm+0x40/0x70 [ 951.370829] ? __switch_to_asm+0x34/0x70 [ 951.371923] ? __switch_to_asm+0x40/0x70 [ 951.372998] ? __switch_to_asm+0x34/0x70 [ 951.374097] ? __switch_to_asm+0x40/0x70 [ 951.375183] ? __switch_to_asm+0x34/0x70 [ 951.376288] ? __switch_to_asm+0x40/0x70 [ 951.377390] ? __switch_to+0x110/0x470 [ 951.378863] do_vfs_ioctl+0x407/0x670 [ 951.380269] ? __schedule+0x2eb/0x740 [ 951.381761] ksys_ioctl+0x67/0x90 [ 951.383076] __x64_sys_ioctl+0x1a/0x20 [ 951.384510] do_syscall_64+0x57/0x190 [ 951.385896] entry_SYSCALL_64_after_hwframe+0x44/0xa9 == Fixes == Indicated by the test case, this issue can be fixed by: * 0ace17d5 (can, slip: Protect tty->disc_data in write_wakeup and close with RCU) This patch can be cherry-picked into all of our kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1862114-pty03/ Tested on KVM nodes and the patched kernels work as expected, there will be no more kernel null pointer dereference issue, and the test can finish properly. == Regression potential == Low, changes limited to two specific drivers for serial line TTY. This issue can be reproduced quite easily and the patched kernels show positive results. == Original Bug Report == startup='Thu Feb 6 02:45:23 2020' tst_test.c:1215: INFO: Timeout per run is 0h 05m 00s pty03.c:101: INFO: Creating PTY with SLIP line discipline Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=pty03 stime=1580957123 dur=350 exit=exited stat=1 core=no cu=0 cs=0 This is a new test case, so it's not a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862114/+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 1849085] Re: netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
** Changed in: linux (Ubuntu Disco)
Status: New => Won't Fix
--
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/1849085
Title:
netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
New
Status in linux source package in Bionic:
New
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
New
Bug description:
[SRU Justification]
[Impact]
The netlink flag NLM_F_ECHO has no effect with the rtnetlink command
RTM_NEWNSID. This has been fixed in v5.4 by the upstream commit
993e4c929a07 ("netns: fix NLM_F_ECHO mechanism for RTM_NEWNSID"). The
bug is here since v4.0.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=993e4c929a07
== Fix ==
Backport the requested patches to Disco (5.0), Bionic (4.15) and
Xenial (4.4).
== Risk of Regregression ==
This patch is quite trivial and limited to the code that manage
RTM_[NEW|GET]NSID commands. Risk should be low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849085/+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 1855461] Re: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()"
** Changed in: linux-azure (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1855461
Title:
[linux-azure] SAUCE patch to "Fix skb protocol value in
tpacket_fill_skb()"
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure source package in Disco:
Won't Fix
Bug description:
The actual fix for this issue would be to backport two related patches
that were accepted upstream in Feb/March 2019. But doing a full
backport is complicated because of dependencies on other new code.
The two upstream commits are:
75c65772c3d1 ("net/packet: Ask driver for protocol if not provided by user")
18bed89107a4 ("af_packet: fix the tx skb protocol in raw sockets with
ETH_P_ALL")
Instead of a full backport of these patches, a SAUCE patch was
generated to avoid the complicated dependencies. The SAUCE patch is
attached to the bug.
Microsoft and the affected customer feel this patch is pretty small
and safe. Microsoft and the end customer have tested the backport and
confirmed that it solves the problem.
Backports are needed for both the 4.15.0 and the 5.0 azure kernels
that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure
Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04,
so getting this fix included there is fairly high priority, though not
“critical/emergency” level. Getting the fix included in the 5.0
kernel in Ubuntu 18.04 in the Azure Marketplace is low priority.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+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 1850540] Re: multi-zone raid0 corruption
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix ** Changed in: mdadm (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1850540 Title: multi-zone raid0 corruption Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in mdadm package in Ubuntu: Fix Released Status in linux source package in Precise: New Status in mdadm source package in Precise: New Status in linux source package in Trusty: Fix Committed Status in mdadm source package in Trusty: Confirmed Status in linux source package in Xenial: Fix Released Status in mdadm source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Released Status in mdadm source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in mdadm source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in mdadm source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Released Status in mdadm source package in Focal: Fix Released Status in mdadm package in Debian: Fix Released Bug description: Bug 1849682 tracks the temporarily revert of the fix for this issue, while this bug tracks the re-application of that fix once we have a full solution. [Impact] (cut & paste from https://marc.info/?l=linux-raid=157360088014027=2) An unintentional RAID0 layout change was introduced in the v3.14 kernel. This effectively means there are 2 different layouts Linux will use to write data to RAID0 arrays in the wild - the “pre-3.14” way and the “3.14 and later” way. Mixing these layouts by writing to an array while booted on these different kernel versions can lead to corruption. Note that this only impacts RAID0 arrays that include devices of different sizes. If your devices are all the same size, both layouts are equivalent, and your array is not at risk of corruption due to this issue. Unfortunately, the kernel cannot detect which layout was used for writes to pre-existing arrays, and therefore requires input from the administrator. This input can be provided via the kernel command line with the raid0.default_layout= parameter, or by setting the default_layout module parameter when loading the raid0 module. With a new enough version of mdadm (>= 4.2, or equivalent distro backports), you can set the layout version when assembling a stopped array. For example: mdadm --stop /dev/md0 mdadm --assemble -U layout-alternate /dev/md0 /dev/sda1 /dev/sda2 See the mdadm manpage for more details. Once set in this manner, the layout will be recorded in the array and will not need to be explicitly specified in the future. (The mdadm part of this SRU is for the above support ^) [Test Case] = mdadm = Confirm that a multi-zone raid0 created w/ older mdadm is able to be started on a fixed kernel by setting a layout. 1) Ex: w/ old kernel/mdadm: mdadm --create /dev/md0 --run --metadata=default \ --level=0 --raid-devices=2 /dev/vdb1 /dev/vdc1 2) Reboot onto fixed kernel & update mdadm 3) sudo mdadm --stop /dev/md0 && sudo mdadm --assemble -U layout-alternate \ /dev/md0 /dev/vdb1 /dev/vdc1 4) Confirm that the array autostarts on reboot 5) Confirm that w/ new kernel & new mdadm, a user can create and start an array in a backwards-compatible fashion (i.e. w/o an explicit layout). 6) Verify that 'mdadm --detail /dev/md0' displays the layout = linux = Similar to above, but using kernel command line options. [Regression Risk] The kernel side of things will break starting pre-existing arrays. That's intentional. The mdadm side will cause a regression in functionality where a user can no longer create multi-zone raid0s on kernels that do not yet have the raid0 layout patches. This is intentional, as such RAID arrays present a corruption risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1850540/+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 1865967] Re: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1865967 Title: xfs fill_fs test in fallocate06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Bug description: == SRU Justification == The fill_fs test for XFS in fallocate06 from ubuntu_ltp_syscalls will fail on X/B/D/E: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop1 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:153: FAIL: Unexpected return value from write(): 7680 (expected 8192) fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Fix == * e093c4be (xfs: Fix tail rounding in xfs_alloc_file_space()) This patch can be cherry-picked in D/E and needs some minor context adjustmest on X/B. == Test == Test kernels can be found here: https://people.canonical.com/~phlin/kernel/lp-1865967-xfs-fallocate06/ All patched kernels are working as expected, this issue will no longer exist on XFS: tst_test.c:1290: INFO: Testing on xfs tst_mkfs.c:90: INFO: Formatting /dev/loop5 with xfs opts='' extra opts='' tst_test.c:1229: INFO: Timeout per run is 0h 05m 00s fallocate06.c:117: INFO: Copy-on-write is not supported fallocate06.c:168: INFO: Case 1. Fill FS: no; Use copy on write: no fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range fallocate06.c:168: INFO: Case 2. Fill FS: yes; Use copy on write: no tst_fill_fs.c:32: INFO: Creating file mntpoint/file0 size 21710183 tst_fill_fs.c:32: INFO: Creating file mntpoint/file1 size 8070086 tst_fill_fs.c:32: INFO: Creating file mntpoint/file2 size 3971177 tst_fill_fs.c:32: INFO: Creating file mntpoint/file3 size 36915315 tst_fill_fs.c:32: INFO: Creating file mntpoint/file4 size 70310993 tst_fill_fs.c:32: INFO: Creating file mntpoint/file5 size 4807935 tst_fill_fs.c:32: INFO: Creating file mntpoint/file6 size 90739786 tst_fill_fs.c:32: INFO: Creating file mntpoint/file7 size 76896492 tst_fill_fs.c:32: INFO: Creating file mntpoint/file8 size 72228649 tst_fill_fs.c:32: INFO: Creating file mntpoint/file9 size 36207821 tst_fill_fs.c:32: INFO: Creating file mntpoint/file10 size 81483962 tst_fill_fs.c:32: INFO: Creating file mntpoint/file11 size 92198827 tst_fill_fs.c:59: INFO: write(): ENOSPC (28) fallocate06.c:157: PASS: write() successful fallocate06.c:201: PASS: Misaligned allocation works as expected fallocate06.c:157: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) successful fallocate06.c:237: PASS: fallocate(FALLOC_FL_PUNCH_HOLE | FALLOC_FL_KEEP_SIZE) cleared the correct file range == Regression Potential == Low, this ensures all the
[Group.of.nepali.translators] [Bug 1864092] Re: quotactl07 from ubuntu_ltp_syscalls failed
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1864092 Title: quotactl07 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Committed Bug description: == SRU Justification == This quotactl07 is a new test case added in LTP test suite, The test will fail with: <<>> incrementing stop tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-38-generic' tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop4' tst_mkfs.c:90: INFO: Formatting /dev/loop4 with xfs opts='' extra opts='' tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 == Fix == * 3dd4d40b (xfs: Sanity check flags of Q_XQUOTARM call) Focal got this patch from stable update. This patch can be cherry- picked into all the other kernels. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1864092-quotactl07/ All patched kernels are working as expected, == Regression Potential == Low, change limited to quota on XFS, and it's just adding a check for the flags. == Original Bug Report == Initially Found: Cloud: GCP Kernel: 5.0.0-1032.33 Test: ubuntu_ltp_syscalls 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:24 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_kconfig.c:62: INFO: Parsing kernel config '/boot/config-5.0.0-1032-gcp' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_device.c:244: INFO: Using test device LTP_DEV='/dev/loop2' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts='' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] quotactl07.c:34: FAIL: Q_XQUOTARM doesn't have quota type check 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] HINT: You _MAY_ be missing kernel fixes, see: 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3dd4d40b4208 02/20 15:04:55 DEBUG| utils:0153| [stdout] 02/20 15:04:55 DEBUG| utils:0153| [stdout] Summary: 02/20 15:04:55 DEBUG| utils:0153| [stdout] passed 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] failed 1 02/20 15:04:55 DEBUG| utils:0153| [stdout] skipped 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] warnings 0 02/20 15:04:55 DEBUG| utils:0153| [stdout] tag=quotactl07 stime=1582210164 dur=4 exit=exited stat=1 core=no cu=0 cs=0 02/20 15:04:55 DEBUG| utils:0153| [stdout] startup='Thu Feb 20 14:49:29 2020' 02/20 15:04:55 DEBUG| utils:0153| [stdout] tst_test.c:1217: INFO: Timeout per run is 0h 05m 00s 02/20 15:04:55 DEBUG| utils:0153| [stdout] read01.c:24: PASS: read(2) returned 512 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864092/+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 1842562] Re: AWS: Add udev rule to set Instance Store device IO timeouts
** Changed in: cloud-init (Ubuntu Disco)
Status: In Progress => Won't Fix
--
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/1842562
Title:
AWS: Add udev rule to set Instance Store device IO timeouts
Status in cloud-init package in Ubuntu:
In Progress
Status in cloud-init source package in Xenial:
In Progress
Status in cloud-init source package in Bionic:
In Progress
Status in cloud-init source package in Disco:
Won't Fix
Status in cloud-init source package in Eoan:
In Progress
Bug description:
[Impact]
AWS wish to implement per-device IO timeouts in their cloud, since
currently NVMe devices only support a single global timeout, and this
doesn't play well with EBS volumes, which have error recovery
capabilities built into the back end, and require large timeouts, and
Instance Store / ephemeral volumes, which are to be treated as local
disks, which require short timeouts.
AWS have proposed a solution which is to backport the below two
patches to the Ubuntu kernels:
commit 65cd1d13b880920054d6c750679baa80b7f9c072
Author: Weiping Zhang
Date: Thu Nov 29 00:04:39 2018 +0800
subject: block: add io timeout to sysfs
commit 4d25339e32a1b6e1f490bb78b1e5b0fa9eb3e073
Author: Weiping Zhang
Date: Tue Apr 2 21:14:30 2019 +0800
subject: block: don't show io_timeout if driver has no timeout handler
This enables a sysfs entry in /sys/block/nvmeXnX/queue/io_timeout
which gets and sets the io_timeout per device in milliseconds.
Kernel commits are being tracked in LP #1841461
EBS volumes will use the default timeout as set on the kernel command
line of 4294966296, and Instance Store volumes will need to use a
default timeout of 3.
AWS have suggested that we deploy the below udev rule to automatically
set the io_timeout of all Instance Store volumes to 3:
KERNEL=="nvme[0-9]*n[0-9]*", ENV{DEVTYPE}=="disk",
ATTRS{model}=="Amazon EC2 NVMe Instance Storage",
ATTR{queue/io_timeout}="3"
This bug is to add the above udev rule to cloud-init.
[Test Case]
This requires an AWS instance that has Instance Store volumes
configured, and I suggest using c5d.large instances.
I have built a test kernel for bionic linux-aws, version
4.15.0-1043.45+hf240347v20190828b2 which is available from here:
https://launchpad.net/~mruffell/+archive/ubuntu/sf240347-kernel
Install the kernel with the below:
1) sudo add-apt-repository ppa:mruffell/sf240347-kernel
2) sudo apt-get update
Modify grub to boot it, this kernel is 1043, and current is 1044, so
it will likely be "1>2" in grub config:
3) sudo vim /etc/default/grub
Change GRUB_DEFAULT=0 to GRUB_DEFAULT="1>2"
4) sudo update-grub
5) reboot
Once system is up, check kernel version:
6) uname -rv
4.15.0-1043-aws #45+hf240347v20190828b2-Ubuntu SMP Wed Aug 28 06:08:21 UTC
2019
Verify that we have two nvme disks, one EBS and one Instance Store:
7) lsblk
Should have two disks, normally nvme0 and nvme1.
See what device is what:
8) sudo udevadm info --attribute-walk /dev/nvme0
For me, ATTR{model} is "Amazon Elastic Block Store"
9) sudo udevadm info --attribute-walk /dev/nvme1
For me, ATTR{model} is "Amazon EC2 NVMe Instance Storage"
Look at the two timeouts (Note no udev rule yet):
10) cat /sys/block/{nvme0n1,nvme1n1}/queue/io_timeout
4294966296
4294966296
Now we deploy the udev rule:
Place the following line in /lib/udev/rules.d/66-aws-io-timeout.rules
KERNEL=="nvme[0-9]*n[0-9]*", ENV{DEVTYPE}=="disk",
ATTRS{model}=="Amazon EC2 NVMe Instance Storage",
ATTR{queue/io_timeout}="3"
Now trigger udev rules:
11) sudo udevadm trigger
Look at the timeouts now:
12) cat /sys/block/{nvme0n1,nvme1n1}/queue/io_timeout
4294966296
3
[Regression Potential]
Regression potential is low since we are adding a udev rule which
applies only to AWS instances, and only for instances which support
Instance Store devices.
The only thing being modified is the device timeout and the udev rule
is robust to device reordering as it goes by model attr information.
When the udev rule is used with unpatched kernels, nothing happens
since the sysfs entry does not exist, and no errors or the like are
reported.
[Other Info]
cloud-init appears to carry azure specific udev rules, which makes me think
that cloud-init is the right place for this requested udev rule to live.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1842562/+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 :
[Group.of.nepali.translators] [Bug 1581864] Re: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument
** Changed in: nginx (Ubuntu Disco) Status: Confirmed => Won't Fix -- 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/1581864 Title: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument Status in nginx package in Ubuntu: Fix Released Status in nginx source package in Xenial: Confirmed Status in nginx source package in Bionic: Confirmed Status in nginx source package in Cosmic: Confirmed Status in nginx source package in Disco: Won't Fix Status in nginx source package in Eoan: Fix Released Status in nginx package in Debian: New Bug description: [Description] Nginx logs an error when started on a machine with a single CPU: systemctl start nginx systemctl status nginx ● nginx.service - A high performance web server and a reverse proxy server Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2016-05-14 19:35:03 UTC; 2s ago Process: 1303 ExecStop=/sbin/start-stop-daemon --quiet --stop --retry QUIT/5 --pidfile /run/nginx.pid (code=exited, status=0/SUCCESS) Process: 1307 ExecStart=/usr/sbin/nginx -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Process: 1306 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=0/SUCCESS) Main PID: 1308 (nginx) Tasks: 5 (limit: 512) Memory: 3.1M CPU: 81ms CGroup: /system.slice/nginx.service ├─1308 nginx: master process /usr/sbin/nginx -g daemon on; master_process on ├─1309 nginx: worker process ├─1310 nginx: worker process ├─1311 nginx: worker process └─1312 nginx: worker process May 14 19:35:03 ngx systemd[1]: Starting A high performance web server and a reverse proxy server... May 14 19:35:03 ngx systemd[1]: nginx.service: Failed to read PID from file /run/nginx.pid: Invalid argument May 14 19:35:03 ngx systemd[1]: Started A high performance web server and a reverse proxy server. Bumping the number of CPU available makes the error disappear. This is reproducible on VMs and containers. Lastly, the PID file is properly created and matches the PID of the master process. [Workaround] sudo mkdir /etc/systemd/system/nginx.service.d printf "[Service]\nExecStartPost=/bin/sleep 0.1\n" | \ sudo tee /etc/systemd/system/nginx.service.d/override.conf sudo systemctl daemon-reload sudo systemctl restart nginx [Additional information] # lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 # apt-cache policy nginx-core nginx-core: Installed: 1.10.0-0ubuntu0.16.04.1 Candidate: 1.10.0-0ubuntu0.16.04.1 Version table: *** 1.10.0-0ubuntu0.16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.9.15-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nginx-core 1.10.0-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat May 14 19:35:21 2016 ProcEnviron: TERM=xterm PATH=(custom, no user) SourcePackage: nginx UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1581864/+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 1828258] Re: ldirectord systemd service fails if no /var/lock/subsys dir
** Changed in: resource-agents (Ubuntu Disco) Status: In Progress => Won't Fix -- 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/1828258 Title: ldirectord systemd service fails if no /var/lock/subsys dir Status in resource-agents package in Ubuntu: In Progress Status in resource-agents source package in Xenial: In Progress Status in resource-agents source package in Bionic: In Progress Status in resource-agents source package in Cosmic: In Progress Status in resource-agents source package in Disco: Won't Fix Status in resource-agents source package in Eoan: In Progress Bug description: [impact] ldirectord's systemd service script contains commands to touch and remove a file in the /var/lock/subsys directory; however, locks there are a SysV service serialization thing, and are unneeded with systemd. It's unclear why the ldirectord systemd service script contains the lines, but they come from upstream so we should get it fixed there and then correct debian and ubuntu. this impacts users because if no /var/lock/subsys directory exists, the systemd service will fail to start, which can impact installing or upgrading the resource-agents package. [test case] remove the /var/lock/subsys directory and try to install or upgrade ldirectord: ubuntu@lp1828258:~$ sudo rmdir /var/lock/subsys ubuntu@lp1828258:~$ sudo apt install ldirectord Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: libfreetype6 Use 'sudo apt autoremove' to remove it. The following NEW packages will be installed: ldirectord 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/62.1 kB of archives. After this operation, 233 kB of additional disk space will be used. Selecting previously unselected package ldirectord. (Reading database ... 30382 files and directories currently installed.) Preparing to unpack .../ldirectord_1%3a4.2.0-1ubuntu1_all.deb ... Unpacking ldirectord (1:4.2.0-1ubuntu1) ... Setting up ldirectord (1:4.2.0-1ubuntu1) ... ...(120 second or so delay)... Job for ldirectord.service failed because the control process exited with error code. See "systemctl status ldirectord.service" and "journalctl -xe" for details. invoke-rc.d: initscript ldirectord, action "start" failed. ● ldirectord.service - Monitor and administer real servers in a LVS cluster of load balanced virtual servers Loaded: loaded (/lib/systemd/system/ldirectord.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-05-09 11:27:53 UTC; 11ms ago Docs: man:ldirectord(8) Process: 7559 ExecStart=/usr/sbin/ldirectord start (code=exited, status=0/SUCCESS) Process: 7564 ExecStartPost=/usr/bin/touch /var/lock/subsys/ldirectord (code=exited, status=1/FAILURE) Process: 7565 ExecStopPost=/bin/rm -f /var/lock/subsys/ldirectord (code=exited, status=0/SUCCESS) Main PID: 7561 Tasks: 3 (limit: 4915) Memory: 71.7M CGroup: /system.slice/ldirectord.service ├─2547 /usr/bin/perl -w /usr/sbin/ldirectord start ├─7078 /usr/bin/perl -w /usr/sbin/ldirectord start └─7561 /usr/bin/perl -w /usr/sbin/ldirectord start May 09 11:26:22 lp1828258 systemd[1]: Starting Monitor and administer real servers in a LVS cluster of load balanced virtual servers... May 09 11:26:23 lp1828258 systemd[1]: ldirectord.service: Supervising process 7561 which is not our child. We'll most likely not notice when it exits. May 09 11:26:23 lp1828258 touch[7564]: /usr/bin/touch: cannot touch '/var/lock/subsys/ldirectord': No such file or directory [regression potential] if something internal to resource-agents actually uses the old SysV- style /var/lock/subsys lock, removing it could cause a regression. However, it shouldn't, because the lock was for use only by SysV service scripts. Also, as we should fix this upstream first, they should know if it is used for any other purpose, so if they accept the change it should be safe. [other info] this is causing autopkgtest failures, especially on arm; but the failure could happen on any arch. also note that /var/lock/subsys (where /var/lock/ is a symlink to /run/lock) is managed by systemd's tmpfiles, as a 'legacy' directory: ubuntu@lp1828258:~$ cat /usr/lib/tmpfiles.d/legacy.conf ...[snip]... # These files are considered legacy and are unnecessary on legacy-free # systems. L /var/lock - - - - ../run/lock # /run/lock/subsys is used for serializing SysV service execution, and # hence without use on SysV-less systems. d /run/lock/subsys 0755 root root - original description: -- In
[Group.of.nepali.translators] [Bug 1828192] Re: Please stop build-depending on libgnome-keyring
** Changed in: chromium-browser (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1828192 Title: Please stop build-depending on libgnome-keyring Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Xenial: Fix Released Status in chromium-browser source package in Bionic: Fix Released Status in chromium-browser source package in Disco: Won't Fix Bug description: libgnome-keyring is not maintained anymore, but chromium build-depends on it. It should be using libsecret instead. The generated binaries depend on neither library, which is a bit confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1828192/+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 1710278] Re: [2.3a1] named stuck on reload, DNS broken
** Changed in: bind9 (Ubuntu Disco) Status: In Progress => Won't Fix -- 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/1710278 Title: [2.3a1] named stuck on reload, DNS broken Status in BIND: Fix Released Status in MAAS: Fix Released Status in MAAS 2.2 series: Fix Released Status in MAAS 2.4 series: Fix Committed Status in MAAS 2.6 series: Fix Released Status in MAAS 2.7 series: Fix Released Status in bind9 package in Ubuntu: In Progress Status in maas package in Ubuntu: Confirmed Status in bind9 source package in Xenial: In Progress Status in bind9 source package in Bionic: In Progress Status in maas source package in Bionic: In Progress Status in bind9 source package in Disco: Won't Fix Status in bind9 source package in Eoan: In Progress Bug description: [Impact] * systemd thinks the service is running, but it does not respond to any commands or requests. Also, it doesn't respond to signals other than kill -9. service restarts hang, rndc hangs. * being that the deadlock is in bind9 that ships in bionic the issue needs to be backported to 2.4.3 so MAAS from the archive in bionic can handle the deadlock and get bind9 unstuck. * change in MAAS watches for this case to occur with bind9, then MAAS will force kill the service and restart it. [Test Case] * very hard to reproduce but the issue occurs when bind9 deadlocks, it response to nothing over the network or rndc. SIGTERM does not kill it only SIGKILL works to force kill the process and get systemd to restart it. [Regression Potential] * possible that bind9 will not be started correctly or possible that bind9 will be placed into a forever restart loop To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+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 1845037] Re: autopkgtest package "lxd" test has started failing
** Changed in: autopkgtest (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1845037 Title: autopkgtest package "lxd" test has started failing Status in autopkgtest package in Ubuntu: Fix Released Status in autopkgtest source package in Xenial: Fix Committed Status in autopkgtest source package in Bionic: Fix Committed Status in autopkgtest source package in Disco: Won't Fix Status in autopkgtest source package in Eoan: Fix Released Bug description: [impact] "lxd launch" behavior recently changed to parse any queued input on stdin and process it as a yaml file. Since the "autopkgtest-build-lxd" script calls "lxd launch", and input queued to stdin when calling "autopkgtest-build-lxd" will cause the internal call to lxd to fail, such as calling "autopkgtest-build-lxd" from inside a here document (see test case below). the failure is seen in (at least) the "lxd" autopkgtest from the autopkgtest package itself, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/a/autopkgtest/20190923_160817_66dbe@/log.gz [test case] root@autopkgtest:~# cat < autopkgtest-build-lxd ubuntu:bionic > echo ok done > EOF Error: yaml: unmarshal errors: line 1: cannot unmarshal !!str `echo ok...` into api.ContainerPut run the autopkgtests for the package 'autopkgtest', or check autopkgtest.ubuntu.com, e.g.: http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/amd64 http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/i386 http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/amd64 http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/i386 the autopkgtest test case is failing only for disco and eoan, and only for amd64/i386 as the 'lxd' test is skipped for non-intel archs. the autopkgtest test case does not fail on bionic or xenial, because the tests there run with the lxd deb, which is still at the older version. http://autopkgtest.ubuntu.com/packages/a/autopkgtest/bionic/amd64 However, the lxd snap can be installed in xenial or bionic, and the failure is reproducable when the lxd snap is installed, i.e.: $ sudo apt remove lxd $ sudo snap install lxd ...perform test case [regression potential] this only redirects stdin from /dev/null, for the call to 'lxc launch' inside autopkgtest-build-lxd; so the regression potential should be low. Any regressions would almost certainly involve a failure during the call to autopkgtest-build-lxd, during the creation of the lxd container. [other info] this is reproducable with the current packages from disco-updates using a local qemu vm for testing. note that the autopkgtest fails only for disco and eoan, becuase on xenial and bionic the lxd deb is used, which still has the older behavior, however the lxd snap is available to install on both xenial and bionic, so this problem still exists for both those releases, as well as disco and eoan. also, this is not just a testcase failure - this is actual new behavior that can break existing users of the "autopkgtest-build-lxd" script in the manner described in the test case. I put the 'importance' of this as low because this bug will only be reproduced when calling autopkgtest-build-lxd from inside a here document passed to a shell, or otherwise called with input queued on stdin, which seems like an unusual way to call autopkgest-build-lxd, although still a perfectly valid way to use it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1845037/+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 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
** Changed in: chrony (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Won't Fix Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- Checking last eoan merge I realized that some tests were failing for chrony: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625 But eoan ran autopkgtests okay when the trigger was chrony/3.5-2ubuntu2 (this last merge): http://autopkgtest.ubuntu.com/packages/chrony/eoan/amd64 Despite having failed for the previous 12 times (eoan). Now, for the first time, we have the same failure for disco: http://autopkgtest.ubuntu.com/packages/chrony/disco/amd64 http://bit.ly/2LpMx4G """ make: Leaving directory '/tmp/autopkgtest.pBHSAl/build.WCD/src/test/simulation/clknetsim' ... 110-chronyc PASS 111-knownclient FAIL 112-port FAIL 121-orphan PASS ... SUMMARY: TOTAL 50 PASSED 48 FAILED 2(111-knownclient 112-port) (255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 265) """ And I'm able to reproduce locally: """ (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL AND (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: non-default settings: starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking mean/min incoming/outgoing packet interval: node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK checking clock sync time, max/rms time/freq error: node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK checking port numbers in packet log: node 1: BAD node 2: BAD network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK
[Group.of.nepali.translators] [Bug 1786013] Re: Packaging resync
** Changed in: linux-azure-edge (Ubuntu Disco) Status: New => Won't Fix -- 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/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: New Status in linux source package in Precise: Fix Committed Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: New Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1801305] Re: Restore request-based mode to xen-blkfront for AWS kernels
** Changed in: linux (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1801305 Title: Restore request-based mode to xen-blkfront for AWS kernels Status in linux-aws package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux-aws source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Committed Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-aws source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Fix Released Bug description: In current Ubuntu kernels, PV blkfront drivers have blk-mq enabled by default and cannot use the old I/O scheduler. [Impact] blk-mq is not as fast as the old request-based scheduler for some workloads on HDD disks. [Fix] Amazon Linux has a commit which reintroduces the request-based mode. It disables blk-mq by default but allows it to be switched back on with a kernel parameter. For X this needs a small patch from upstream for error handling. For B/C this patchset is bigger as it includes the suspend/resume patches already in X, and a new fixup. These are desirable as the request mode patch assumes their presence. [Regression Potential] Could potentially break xen based disks on AWS. For B/C, the patches also add some code to the xen core around suspend and resume, this code is much smaller and also mirrors code already in Xenial. [Tests] Tested by AWS for Xenial, and their kernel engineers vetted the patches. I tested the Bionic and Cosmic patchsets with fio, the system appears stable and the IOPS promised for EBS Provisioned IOPS disks were met in my testing. I did an apt update/upgrade and everything worked (no hash-sum mismatches). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1801305/+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 1842479] Re: timer_create will fail with invalid error code
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1842479 Title: timer_create will fail with invalid error code Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Committed Bug description: [Impact] On some OpenPower systems, RTC does not support set_alarm, and timer_create(CLOCK_REALTIME_ALARM, ...) will fail with ENOTSUPP instead of EOPNOTSUPP. This will break some regression testing that expects the later value. [Test cases] Run LTP syscalls regression testing, which we do before releasing kernels. [Regression potential] This should not break any userspace, as none should be using/expecting ENOTSUPP for any call. In order to do so, they would have to go out of their way as it's not defined on libc headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842479/+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 1856359] Re: EFA backport is missing commit f95be3d28d89 ("RDMA: Add EFA related definitions")
** Changed in: linux-aws (Ubuntu Disco)
Status: In Progress => Won't Fix
--
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/1856359
Title:
EFA backport is missing commit f95be3d28d89 ("RDMA: Add EFA related
definitions")
Status in linux-aws package in Ubuntu:
Invalid
Status in linux-aws source package in Xenial:
Invalid
Status in linux-aws source package in Bionic:
Invalid
Status in linux-aws source package in Disco:
Won't Fix
Status in linux-aws source package in Eoan:
Invalid
Bug description:
For kernels that contain: 0ede73bc012c ("IB/uverbs: Extend
uverbs_ioctl header with driver_id"), then the EFA driver should be
integrated for enumeration with: f95be3d28d89 ("RDMA: Add EFA related
definitions")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1856359/+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 1848828] Re: report packages from security pocket
** Changed in: landscape-client (Ubuntu Disco) Status: In Progress => Won't Fix -- 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/1848828 Title: report packages from security pocket Status in landscape-client package in Ubuntu: In Progress Status in landscape-client source package in Xenial: In Progress Status in landscape-client source package in Bionic: In Progress Status in landscape-client source package in Disco: Won't Fix Status in landscape-client source package in Eoan: In Progress Status in landscape-client source package in Focal: In Progress Bug description: [Impact] I report this bug to add the necessary bit into lds-client for all affected/supported releases. [Test Case] * One must use Landscape server on-prem (version >=19.01) or hosted which already contain the necessary server side change. * Install landscape-client. * Successfully register a client against Landscape server. * Security updates will only rely on USN notices and could possibly ignore other packages found in -security pocket even if they are there simply by the fact that there was no USN notice specific for them. (e.g. systemd has an USN, systemd get updated but its derived systemd binary packages aren't updated) [Regression Potential] * The patch flags potential security updates by matching the pocket name. The server then does additional package selection from that info. If the pocket matching were to break, security updates would continue as it was previously. * False positive matching could be possible, assuming one builds a mirror which mimics security pockets and contains normal updates. In that case, landscape could mistakenly update as if they were security updates. * Landscape may apply security updates without USN data, if the update comes from a security pocket. Since this matches the behaviour of unattended-upgrades and MOTD info, this may be closer to what users expect, even though this is a change of behaviour. [Other Info] * Upstream details: https://github.com/CanonicalLtd/landscape-client/commit/93a3b47965da199785e9b3d226cb61f721e54196 https://github.com/CanonicalLtd/landscape-client/pull/57 https://github.com/CanonicalLtd/landscape-client/pull/70 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1848828/+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 1861238] Re: Root can lift kernel lockdown via USB/IP
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1861238 Title: Root can lift kernel lockdown via USB/IP Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] It's possible to turn off kernel lockdown by emulating a USB keyboard via USB/IP and sending an Alt+SysRq+X key combination through it. Ubuntu's kernels have USB/IP enabled (CONFIG_USBIP_VHCI_HCD=m and CONFIG_USBIP_CORE=m) with signed usbip_core and vhci_hcd modules provided in the linux-extra-modules-* package. See the PoC here: https://github.com/xairy/unlockdown#method-1-usbip [Test Case] $ git clone https://github.com/xairy/unlockdown.git $ cd unlockdown/01-usbip/ $ sudo ./run.sh $ dmesg # Ensure there are no log entries talking about lifting lockdown: sysrq: SysRq : Disabling Secure Boot restrictions Lifting lockdown # You should see a SysRq help log entry because the Alt+SysRq+X # combination should be disabled sysrq: SysRq : HELP : loglevel(0-9) reboot(b) crash(c) terminate-all-tasks(e) memory-full-oom-kill(f) kill-all-tasks(i) thaw-filesystems(j) sak(k) show-backtrace-all-active-cpus(l) show-memory-usage(m) nice-all-RT-tasks(n) poweroff(o) show-registers(p) show-all-timers(q) unraw(r) sync(s) show-task-states(t) unmount(u) force-fb(V) show-blocked-tasks(w) dump-ftrace-buffer(z) [Regression Potential] Some users may see a usability regression due to the Lockdown lift sysrq combination being removed. Some users are known to disable lockdown, using the sysrq combination, in order to perform some "dangerous" operation such as writing to an MSR. It is believed that this is a small number of users but it is impossible to know for sure. Users that rely on this functionality may need to permanently disable secure boot using 'mokutil --disable-validation'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861238/+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 1860231] Re: 5.4.0-11 crash on cryptsetup open
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1860231 Title: 5.4.0-11 crash on cryptsetup open Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Bug description: [Impact] An attempt to run cryptsetup open on a newly created LUKS partition on Ubuntu Core 20 causes a kernel crash. This happens in 100% of the attempts on the snapd Core 20 installation test, but on an image created to reproduce this bug it happens only when certain parameters are passed to cryptsetup. Both images are built similarly so the reason for this discrepancy is unknown. The kernel was installed from pc-kernel_374.snap. [Test Case] $ dir=$(mktemp -d /tmp/lp1860231.X) $ dmsetup create lp1860231 --notable $ mount -t ext4 \ "/dev/dm-$(dmsetup info -c -o minor --noheadings lp1860231)" "$dir" Now check the logs for a backtrace. [Regression Potential] The currently proposed fix introduces no chance of stability regressions. There is a chance of a very small performance regression since an additional pointer comparison is performed on each block layer request but this is unlikely to be noticeable. [Original Report] Linux version 5.4.0-11-generic (buildd@lgw01-amd64-021) (gcc version 9.2.1 20200104 (Ubuntu 9.2.1-22ubuntu2)) #14-Ubuntu SMP Thu Jan 9 16:14:26 UTC 2020 Version signature: Ubuntu 5.4.0-11.14-generic 5.4.8 How to reproduce the crash in 3 "easy" steps: 1. Build a Core 20 image using the attached model file: 1.1. Install the ubuntu-image from latest/edge $ sudo snap install --channel latest/edge ubuntu-image 1.2. Build the image $ sudo ubuntu-image --image-size=4G ubuntu-core-20-amd64.model 2. Boot the image in kvm 2.1. Install ovmf version 0~20190606.20d2e5a1-2ubuntu1 or newer (the stock ovmf from bionic may not work) 2.2. Boot the image $ sudo kvm -snapshot -m 2048 -smp 4 \ -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,if=virtio \ -bios /usr/share/OVMF/OVMF_CODE.ms.fd 2.3. In the grub menu, edit the default option to include parameter "systemd.debug-shell=1" in the kernel command line 2.4. Boot the kernel 3. Crash the kernel 3.1. When the system boots to the "Press enter to configure" message, press ALT-F9 to enter the debug shell. 3.2. The system should have two partitions in /dev/vda. Create a third one with fdisk. 3.3. Create a LUKS encrypted partition: # echo 123|cryptsetup luksFormat -q --type luks2 --key-file - --pbkdf argon2i --iter-time 1 /dev/vda3 (the system will complain about a missing locking directory, just ignore it.) 3.4. Open the encrypted device: # echo 123|cryptsetup open --key-file - /dev/vda name The Core 20 images contain the following udev rule which causes the new block device to be mounted automatically. This mount is what triggers the BUG: ACTION=="add", SUBSYSTEM=="block", KERNEL!="loop*", KERNEL!="ram*" \ RUN+="/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/%k" 3.5. Read the crash message The attached screenshots show these steps being executed. A few notes: - The backtrace seems very similar to the one reported in bug #1835279, however that problem was possibly caused by a race between partition creation and LUKS formatting. This time it doesn't seem to be the case, delays between commands don't help us here. - In the test case above using large values of KDF iter-time may prevent the crash. I successfully opened the device in kernel 5.4.0-9 with --iter-time larger than 100, but 5.4.0-11 seems to require values closer to 1000. Regardless of the --iter-time value used, the crash always happen when running the test in a spread-driven automated environment (same kernel with image built in the same way, some other variable seems to be disturbing the system). - All necessary modules are loaded before the LUKS partition creation (i.e. it doesn't seem to be caused by a race between dm-crypt loading and cryptsetup luksFormat for example). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to :
[Group.of.nepali.translators] [Bug 1861243] Re: Revert temporary md/raid0 layout patch
** Changed in: linux (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1861243 Title: Revert temporary md/raid0 layout patch Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Triaged Bug description: A "temporary" patch was applied to Xenial, Bionic, Disco and Eoan as part of the fix for: https://bugs.launchpad.net/bugs/1850540: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/xenial/commit/?id=faf36efcc6d6bf50c9b5a2a6d7f0efdae296e8a6 "UBUNTU: SAUCE: md/raid0: Use kernel specific layout" (this uses by default the layout for multi-zone md RAID0 arrays that the kernel was using before / instead of failing to assemble those and require the user to make a choice). Once the rollout of a fixed user-space and maybe some grace period we should revert this to be back behaving like upstream does. This bug is for tracking the reversion of the patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861243/+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 1858834] Re: ipc/sem.c : process loops infinitely in exit_sem()
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1858834
Title:
ipc/sem.c : process loops infinitely in exit_sem()
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
[Description]
Commit a97955844807 ("ipc,sem: remove uneeded sem_undo_list lock usage
in exit_sem()") removes a lock that is needed. This leads to a process
looping infinitely in exit_sem() and can also lead to a crash.
[Test case]
Using the reproducer found in [1] is fairly easy to reach a point where
one of the child processes is looping infinitely in exit_sem between
for(;;) and if (semid == -1) block, while it's trying to free its last
sem_undo structure which has already been freed by freeary().
Once commit a97955844807 ("ipc,sem: remove uneeded sem_undo_list lock
usage in exit_sem()") the issue is not reproducible any more.
[Other]
Patch submitted upstream :
https://lkml.org/lkml/2019/12/11/1718
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1694779
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1858834/+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 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files
** Changed in: isc-dhcp (Ubuntu Cosmic) Status: Triaged => Won't Fix ** Changed in: isc-dhcp (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1543799 Title: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Xenial: Triaged Status in isc-dhcp source package in Bionic: Triaged Status in isc-dhcp source package in Cosmic: Won't Fix Status in isc-dhcp source package in Disco: Won't Fix Bug description: dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is found /run/dhcp-server. Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit files specify the RuntimeDirectory 'dhcp-server', which is removed when either unit stops (and thus would wipe out the other unit's pid file, were it being successfully written). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-server 4.3.3-5ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 9 21:34:08 2016 InstallationDate: Installed on 2016-02-09 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) ProcEnviron: LANGUAGE=en_GB:en TERM=linux PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.dhcp.dhcpd.conf: [modified] mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+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 1850651] Re: [SRU] Authentication constantly re-requested for Google
** Changed in: thunderbird (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in thunderbird source package in Disco: Won't Fix Status in thunderbird source package in Eoan: Fix Released Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430
[Group.of.nepali.translators] [Bug 1831940] Re: hibernation support for linux-aws
** Changed in: linux-aws (Ubuntu Disco) Status: Fix Committed => Won't Fix -- 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/1831940 Title: hibernation support for linux-aws Status in linux-aws package in Ubuntu: Fix Released Status in linux-aws-5.0 package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Released Status in linux-aws-5.0 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-aws-5.0 source package in Bionic: Fix Released Status in linux-aws source package in Disco: Won't Fix Status in linux-aws-5.0 source package in Disco: Invalid Status in linux-aws source package in Eoan: Fix Released Status in linux-aws-5.0 source package in Eoan: Confirmed Status in linux-aws source package in Focal: Fix Released Status in linux-aws-5.0 source package in Focal: Invalid Bug description: Additional AWS-specific and mainline patches are required to support hibernation across the various types of AWS instances. The following patch sets for linux-aws-xenial and linux-aws-bionic provide the necessary functionality, and should only impact the hibernation and resume paths. [linux-aws-xenial] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. radix-tree: delete radix_tree_locate_item() mm: rid swapoff of quadratic complexity sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to wake_up() sched/wait: Avoid abort_exclusive_wait() in ___wait_event() sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock() sched/wait: Introduce init_wait_entry() sched/wait: Standardize wait_bit_queue naming sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled NVMe: Allow request merges PM / hibernate: Do not free preallocated safe pages during image restore PM / hibernate: Recycle safe pages after image restoration PM / hibernate: Simplify mark_unsafe_pages() UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on hibernate [linux-aws-bionic] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. mm: rid swapoff of quadratic complexity sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff netlink: Don't shift on 64 for ngroups [linux-aws-edge-bionic] UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing PM / hibernate: memory_bm_find_bit(): Tighten node optimisation mm: rid swapoff of quadratic complexity mm: refactor swap-in logic out of shmem_getpage_gfp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1831940/+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 1840488] Re: Disable Bluetooth in cloud kernels
** Changed in: linux-aws (Ubuntu Disco) Status: Triaged => Won't Fix ** Changed in: linux-gcp (Ubuntu Disco) Status: Triaged => Won't Fix ** Changed in: linux-oracle (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1840488 Title: Disable Bluetooth in cloud kernels Status in linux-aws package in Ubuntu: Triaged Status in linux-gcp package in Ubuntu: Triaged Status in linux-gke-4.15 package in Ubuntu: Invalid Status in linux-gke-5.0 package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Triaged Status in linux-aws source package in Xenial: Invalid Status in linux-gcp source package in Xenial: Triaged Status in linux-gke-4.15 source package in Xenial: Invalid Status in linux-gke-5.0 source package in Xenial: Invalid Status in linux-oracle source package in Xenial: Triaged Status in linux-aws source package in Bionic: Triaged Status in linux-gcp source package in Bionic: Triaged Status in linux-gke-4.15 source package in Bionic: Triaged Status in linux-gke-5.0 source package in Bionic: Triaged Status in linux-oracle source package in Bionic: Triaged Status in linux-aws source package in Disco: Won't Fix Status in linux-gcp source package in Disco: Won't Fix Status in linux-gke-4.15 source package in Disco: Invalid Status in linux-gke-5.0 source package in Disco: Invalid Status in linux-oracle source package in Disco: Won't Fix Status in linux-aws source package in Eoan: Triaged Status in linux-gcp source package in Eoan: Triaged Status in linux-gke-4.15 source package in Eoan: Invalid Status in linux-gke-5.0 source package in Eoan: Invalid Status in linux-oracle source package in Eoan: Triaged Bug description: [Impact] Some cloud-focused kernels have CONFIG_BT enabled but cloud instances shouldn't need bluetooth support. Disabling the bluetooth subsystem reduces the amount of security-sensitive code we have to worry about in the cloud kernels and also has the nice side effect of minimizing build times and kernel sizes. The cloud kernels known to have bluetooth enabled include: * [B/D/E] linux-aws (arm64 only) * [X/B/D/E] linux-gcp * [B] linux-gke-4.15 * [B] linux-gke-5.0 * [X/B/D/E] linux-oracle [Test Case] 1. Install patched kernel and reboot into it 2. Ensure that the following command does NOT display any output: $ grep CONFIG_BT=[my] /boot/config-$(uname -r) [Regression Potential] There could be an unexpected dependence on bluetooth within one of the clouds but I think it is highly unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1840488/+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 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Won't Fix -- 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/520546 Title: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Xenial: Confirmed Status in kbd source package in Xenial: Won't Fix Status in xorg-server source package in Xenial: Confirmed Status in console-setup source package in Bionic: Fix Released Status in kbd source package in Bionic: Won't Fix Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Released Status in kbd source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Released Status in kbd source package in Disco: Won't Fix Status in linux source package in Disco: Won't Fix Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Fix Released Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (kbd) [Impact] * kbd_mode -u is documented to break keyboards in modes other than xlate and unicode, while it is still called by some scripts. Those scripts are called transitively by maintainer scripts such as the one already fixed in console-setup. * To avoid accidentally breaking keyboards a -f option is added to force such breaking mode changes. Without -f only the safe mode changes are performed and an error is printed when the requested mode change is not safe. Next upstream version will also exit with error, but the cherry-picked fix makes kbd_mode return success even when the mode switch is not performed to avoid regressions of scripts. [Test case] * Verify that safe mode switches work and dangerous ones are skipped without -f. Please note that the test will temporarily break the system's keyboard and it is recommended to run the test in a VM. rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $? The keyboard is in Unicode (UTF-8) mode 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in xlate (8-bit) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in some unknown mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $? 0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in Unicode (UTF-8) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0 rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0 The keyboard is in raw (scancode) mode rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $? The keyboard is in raw (scancode) mode Changing to the requested mode may make your keyboard unusable, please use -f to force the change. 0 [Regression Potential] * kbd_mode stops performing breaking mode switches and this may make scripts ineffective when trying to perform a breaking change. This is the intention of the change and the emitter error helps in finding the offending script. The following packages found to call kbd_mode directly: console-setup xinit console-cyrillic initramfs-tools dracut console-tools xview ubiquity's embedded console-setup copy console-data vnc4 The console related packages are expected to execute only safe mode changes because they should operate on consoles only and the rest seem to be safe, too. (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7
[Group.of.nepali.translators] [Bug 1840789] Re: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Ubuntu 19.04 reached end of life on January 23, 2020. I am therefore
marking this bug 'wontfix' for that release.
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Won't Fix
--
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/1840789
Title:
bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Incomplete
Status in linux source package in Bionic:
Incomplete
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* The bnx2x driver may cause hardware faults (leading to
panic/reboot) and other behaviors as transmit timeouts,
after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
introduced.
* This issue has been observed by an user shortly
after starting docker & kubelet, with adapters:
- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
* If options to ignore hardware faults are used
(erst_disable=1 hest_disable=1 ghes.disable=1)
the system doesn't panic/reboot and continues
on to timeout on adapter stats, then transmit
timeouts, spewing some adapter firmware dumps,
but the network interface is non-functional.
* The issue only happened when LLDP is enabled
on the network switches, and crashdump shows
the bnx2x driver is stuck/waits for firmware
to complete the stop traffic command in LLDP
handling. Workaround used is to disable LLDP
in the network switches/ports.
* Analysis of the driver and firmware dumps
didn't help significantly towards finding
the root cause.
* Upstream/mainline recently just reverted the
patch, due to similar problem reports, while
looking for the root cause/proper fix.
[Test Case]
* No reproducible test case found outside
the user's systems/cluster, where it is
enough to start docker & kubelet & wait.
* The user verified test kernels for Xenial
and Bionic - the problem does not happen;
build-tested on Disco.
[Regression Potential]
* Users who significantly use/apply the non-default
traffic class (tc) / class of service (cos) might
possibly see performance changes (if any at all)
in such applications, however that's unclear now.
* This is a recent revert upstream (v5.3-rc'ish),
so there's chance things might change in this area.
* Nonetheless, the patch is authored by the driver
vendor, and made its way into stable kernels
(e.g., v5.2.8 which made Eoan/19.10 recently).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840789/+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 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
Ubuntu 19.04 reached end of life on January 23, 2020. I am therefore
marking this bug 'wontfix' for that release.
** Changed in: makedumpfile (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
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/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Won't Fix
Status in makedumpfile source package in Disco:
Won't Fix
Status in makedumpfile source package in Eoan:
In Progress
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+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 1815201] Re: mdadm checkraid cronjob runs at the same time
Ubuntu 19.04 reached end of life on January 23, 2020. I am therefore marking this bug 'wontfix' for that release. ** Changed in: mdadm (Ubuntu Disco) Status: Triaged => Won't Fix ** Changed in: mdadm (Ubuntu Cosmic) Status: New => Won't Fix -- 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/1815201 Title: mdadm checkraid cronjob runs at the same time Status in mdadm package in Ubuntu: Fix Released Status in mdadm source package in Xenial: New Status in mdadm source package in Bionic: New Status in mdadm source package in Cosmic: Won't Fix Status in mdadm source package in Disco: Won't Fix Bug description: Currently the mdadm package will install a checkraid crontab, that is the same on all installations. This is fine for a single installation, but in bigger (distributed) environments this hurts performance. E.g. having mysql clusters on softRaid all having their arrays checked at the same moment, causes problems with availability. An solution would / could be to add an option that will allow the date-time to be randomized. Then this option / question can be used where appropriate, while still retaining the option to have the static configuration as a default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1815201/+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 1824687] Re: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue
** Changed in: linux (Ubuntu Disco) Status: Triaged => Won't Fix -- 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/1824687 Title: 4.4.0-145-generic Kernel Panic ip6_expire_frag_queue Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Bug description: [SRU Justification] == Impact == Since 05c0b86b96 "ipv6: frags: rewrite ip6_expire_frag_queue()" the 16.04/4.4 kernel crashes whenever that functions gets called (on busy systems this can be every 3-4 hours). While this potentially affects Cosmic and later, too, the fix differs on later kernels (Bionic is not yet affected as it does not yet carry updates to the frags handling). == Fix == For Xenial and Cosmic, the proposed fix would be additional changes to ip6_expipre_frag_queue(), taken from follow-up changes to ip_expire(). For Disco, I would hold back because we have a backlog of stable patches there and depending on what got backported to 5.0.y there would be a simpler fix. For current development kernels, one just needs to ensure that the following upstream change is included: 47d3d7fdb10a "ip6: fix skb leak in ip6frag_expire_frag_queue()". == Testcase == Unfortunately this could not be re-created locally. But a test kernel which had the proposed fix applied was showing good testing (see comment #37 and #38). == Risk of Regression == The modified function is only called in rare cases and the positive testing in production would cover this. So I would consider it low. --- Description: Ubuntu 16.04.6 LTS Release: 16.04 After upgrading our server to this Kernel we experience frequent Kernel panics (Attachment). Every 3 hours. Our machine has a throuput of about 600 Mbits/s The Panics are around the area of ip6_expire_frag_queue. __pskb_pull_tail ip6_dst_lookup_tail _decode_session6 __xfrm_decode_session icmpv6_route_lookup icmp6_send It seems similar to Bug Report in Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922488 According to the bug finder of above bug it also occurred after using a Kernel with the change of rewrite ip6_expire_frag_queue() Intermediate solution. We disabled IPv6 on this machine to avoid further Panics. Please let me know what information is missing. The ubuntu-bug linux was send. And I hope it is attached to this report. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-145-generic 4.4.0-145.171 ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 Uname: Linux 4.4.0-145-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 14 11:40:11 2019 InstallationDate: Installed on 2018-03-18 (391 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to xenial on 2018-10-21 (174 days ago) --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 12 21:04 seq crw-rw 1 root audio 116, 33 Apr 12 21:04 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=/dev/mapper/tor3--vg-swap_1 InstallationDate: Installed on 2018-03-18 (393 days ago) InstallationMedia: Ubuntu-Server 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IwConfig: Error: [Errno 2] No such file or directory Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro X9SRE/X9SRE-3F/X9SRi/X9SRi-3F Package: linux (not installed) PciMultimedia: ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-145-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176 RelatedPackageVersions: linux-restricted-modules-4.4.0-145-generic N/A linux-backports-modules-4.4.0-145-generic N/A linux-firmware
[Group.of.nepali.translators] [Bug 1661779] Re: /usr/sbin/apache2:7:crc32_little:crc32:deflate_out_filter:filter_harness:default_handler
** Also affects: apache2 (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Also affects: apache2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu Xenial) Status: New => Triaged ** Changed in: apache2 (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: apache2 (Ubuntu Groovy) 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/1661779 Title: /usr/sbin/apache2:7:crc32_little:crc32:deflate_out_filter:filter_harness:default_handler Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Xenial: Triaged Status in apache2 source package in Groovy: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apache2. This problem was most recently seen with package version 2.4.18-2ubuntu4, the problem page at https://errors.ubuntu.com/problem/cd1f9857dc546d0691e16e8ee1e437007c719465 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1661779/+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 1660725] Re: /usr/sbin/apache2:*** Error in `/usr/sbin/apache2': munmap_chunk(): invalid pointer: ADDR ***
>From the error tracker, this crash was seen in apache versions between 2.4.6 (Ubuntu 13.10) and 2.4.27 (Ubuntu 17.10) but there have been no instances of the issue on Ubuntu 18.04 or newer. It appears to still exhibit itself in the version published for Ubuntu 16.04, apache2 2.4.18-2ubuntu3.14. There is a .15 in proposed for xenial but it doesn't sound like a fix for this crash. So the issue is still relevant for xenial at least. Indeed, the last occurrence reported was Jan 23, 2020. The fault occurs in php7.0 code, during the php module shutdown codepath, where a destructor freeing a hash tries to unmap an invalid pointer. Since this occurs during cleanup, it may not have shown noteworthy symptoms, which may be why it stayed around for so long. ** Changed in: apache2 (Ubuntu) Importance: Undecided => Medium ** Changed in: apache2 (Ubuntu) Status: New => Triaged ** Also affects: apache2 (Ubuntu Groovy) Importance: Medium Status: Triaged ** Also affects: apache2 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: apache2 (Ubuntu Groovy) Status: Triaged => Fix Released ** Changed in: apache2 (Ubuntu Xenial) Status: New => Triaged ** Changed in: apache2 (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1660725 Title: /usr/sbin/apache2:*** Error in `/usr/sbin/apache2': munmap_chunk(): invalid pointer: ADDR *** Status in apache2 package in Ubuntu: Fix Released Status in apache2 source package in Xenial: Triaged Status in apache2 source package in Groovy: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apache2. This problem was most recently seen with package version 2.4.18-2ubuntu4, the problem page at https://errors.ubuntu.com/problem/ea0e5025928fb673b88e8b0a74ec85a92629215e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1660725/+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 1885503] Re: xenial/linux-aws: 4.4.0-1111.122 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-aws meta: linux-meta-aws - phase: Packaging - phase-changed: Wednesday, 01. July 2020 16:28 UTC + phase: Building in ppa + phase-changed: Thursday, 02. July 2020 16:52 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-aws/aws-kernel: bug 1885502 variant: debs + versions: + main: 4.4.0-.122 + meta: 4.4.0..115 -- 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/1885503 Title: xenial/linux-aws: 4.4.0-.122 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New 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: New 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-aws meta: linux-meta-aws phase: Building in ppa phase-changed: Thursday, 02. July 2020 16:52 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-aws/aws-kernel: bug 1885502 variant: debs versions: main: 4.4.0-.122 meta: 4.4.0..115 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1885503/+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 1882733] Re: xenial/linux-aws-hwe: 4.15.0-1074.78~16.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1882733
Title:
xenial/linux-aws-hwe: 4.15.0-1074.78~16.04.1 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
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 promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-aws-hwe source package in Xenial:
Fix Released
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: 1885041
packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
phase: Complete
phase-changed: Thursday, 02. July 2020 15:07 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
versions:
main: 4.15.0-1074.78~16.04.1
meta: 4.15.0.1074.74
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882733/+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 1882749] Re: xenial/linux-oracle: 4.15.0-1046.50~16.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1882749
Title:
xenial/linux-oracle: 4.15.0-1046.50~16.04.1 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
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-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-oracle source package in Xenial:
Fix Released
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: 1885098
packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
phase: Complete
phase-changed: Thursday, 02. July 2020 15:08 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
versions:
main: 4.15.0-1046.50~16.04.1
meta: 4.15.0.1046.39
signed: 4.15.0-1046.50~16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882749/+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 1882743] Re: xenial/linux-gcp: 4.15.0-1078.88~16.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1882743
Title:
xenial/linux-gcp: 4.15.0-1078.88~16.04.1 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
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-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-gcp source package in Xenial:
Fix Released
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: 1882744
packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
phase: Complete
phase-changed: Thursday, 02. July 2020 15:06 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-gcp/gcp-kernel: bug 1882741
xenial/linux-gcp/gke-kernel: bug 1882742
variant: debs
versions:
main: 4.15.0-1078.88~16.04.1
meta: 4.15.0.1078.80
signed: 4.15.0-1078.88~16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882743/+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 1882753] Re: xenial/linux-hwe: 4.15.0-107.108~16.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => 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/1882753
Title:
xenial/linux-hwe: 4.15.0-107.108~16.04.1 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
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-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-hwe source package in Xenial:
Fix Released
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: 1885044
packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
phase: Complete
phase-changed: Thursday, 02. July 2020 14:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-deeplens: bug 1882752
variant: debs
versions:
main: 4.15.0-107.108~16.04.1
meta: 4.15.0.107.112
signed: 4.15.0-107.108~16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882753/+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 1882733] Re: xenial/linux-aws-hwe: 4.15.0-1074.78~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => 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: 1885041
packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
- phase: Promote to Security
- phase-changed: Thursday, 02. July 2020 13:07 UTC
+ phase: Complete
+ phase-changed: Thursday, 02. July 2020 15:07 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
- reason:
- promote-to-security: Ongoing -- packages not yet published
+ reason: {}
variant: debs
versions:
main: 4.15.0-1074.78~16.04.1
meta: 4.15.0.1074.74
--
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/1882733
Title:
xenial/linux-aws-hwe: 4.15.0-1074.78~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 promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-aws-hwe source package in Xenial:
Fix Released
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: 1885041
packages:
main: linux-aws-hwe
meta: linux-meta-aws-hwe
phase: Complete
phase-changed: Thursday, 02. July 2020 15:07 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
versions:
main: 4.15.0-1074.78~16.04.1
meta: 4.15.0.1074.74
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882733/+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 1882743] Re: xenial/linux-gcp: 4.15.0-1078.88~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => 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: 1882744
packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Promote to Security
- phase-changed: Thursday, 02. July 2020 13:06 UTC
+ phase: Complete
+ phase-changed: Thursday, 02. July 2020 15:06 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
- reason:
- promote-to-security: Ongoing -- packages not yet published
+ reason: {}
trackers:
xenial/linux-gcp/gcp-kernel: bug 1882741
xenial/linux-gcp/gke-kernel: bug 1882742
variant: debs
versions:
main: 4.15.0-1078.88~16.04.1
meta: 4.15.0.1078.80
signed: 4.15.0-1078.88~16.04.1
--
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/1882743
Title:
xenial/linux-gcp: 4.15.0-1078.88~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-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-gcp source package in Xenial:
Fix Released
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: 1882744
packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
phase: Complete
phase-changed: Thursday, 02. July 2020 15:06 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-gcp/gcp-kernel: bug 1882741
xenial/linux-gcp/gke-kernel: bug 1882742
variant: debs
versions:
main: 4.15.0-1078.88~16.04.1
meta: 4.15.0.1078.80
signed: 4.15.0-1078.88~16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882743/+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 1882749] Re: xenial/linux-oracle: 4.15.0-1046.50~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => 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: 1885098
packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
- phase: Promote to Security
- phase-changed: Thursday, 02. July 2020 13:07 UTC
+ phase: Complete
+ phase-changed: Thursday, 02. July 2020 15:08 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
- reason:
- promote-to-security: Ongoing -- packages not yet published
+ reason: {}
variant: debs
versions:
main: 4.15.0-1046.50~16.04.1
meta: 4.15.0.1046.39
signed: 4.15.0-1046.50~16.04.1
--
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/1882749
Title:
xenial/linux-oracle: 4.15.0-1046.50~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-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-oracle source package in Xenial:
Fix Released
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: 1885098
packages:
main: linux-oracle
meta: linux-meta-oracle
signed: linux-signed-oracle
phase: Complete
phase-changed: Thursday, 02. July 2020 15:08 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
variant: debs
versions:
main: 4.15.0-1046.50~16.04.1
meta: 4.15.0.1046.39
signed: 4.15.0-1046.50~16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882749/+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 1885510] Re: xenial/linux-snapdragon: 4.4.0-1140.148 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Packaging - phase-changed: Wednesday, 01. July 2020 18:36 UTC + phase: Building in ppa + phase-changed: Thursday, 02. July 2020 15:00 UTC reason: - prepare-package: Pending -- tag not published and package not - uploaded - prepare-package-meta: Pending -- tag not published and package not - uploaded + build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1885509 variant: debs + versions: + main: 4.4.0-1140.148 + meta: 4.4.0.1140.132 -- 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/1885510 Title: xenial/linux-snapdragon: 4.4.0-1140.148 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New 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: New 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon 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 -- kernel-stable-master-bug: 1885514 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Building in ppa phase-changed: Thursday, 02. July 2020 15:00 UTC reason: build-packages-ppa: Ongoing -- building in ppa main:building trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1885509 variant: debs versions: main: 4.4.0-1140.148 meta: 4.4.0.1140.132 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1885510/+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 1882753] Re: xenial/linux-hwe: 4.15.0-107.108~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security
Status: In Progress => 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: 1885044
packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
- phase: Promote to Security
- phase-changed: Thursday, 02. July 2020 13:04 UTC
+ phase: Complete
+ phase-changed: Thursday, 02. July 2020 14:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
- reason:
- promote-to-security: Ongoing -- packages not yet published
+ reason: {}
trackers:
xenial/linux-deeplens: bug 1882752
variant: debs
versions:
main: 4.15.0-107.108~16.04.1
meta: 4.15.0.107.112
signed: 4.15.0-107.108~16.04.1
--
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/1882753
Title:
xenial/linux-hwe: 4.15.0-107.108~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:
Fix Released
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-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-hwe source package in Xenial:
Fix Released
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: 1885044
packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
phase: Complete
phase-changed: Thursday, 02. July 2020 14:56 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
xenial/linux-deeplens: bug 1882752
variant: debs
versions:
main: 4.15.0-107.108~16.04.1
meta: 4.15.0.107.112
signed: 4.15.0-107.108~16.04.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1882753/+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 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
This bug was fixed in the package gnutls28 - 3.4.10-4ubuntu1.8 --- gnutls28 (3.4.10-4ubuntu1.8) xenial; urgency=medium * d/p/50_Update-session_ticket.c-to-add-support-for-zero-leng.patch: - add support for zero length session tickets returned from the server, thanks Rod for the backport and testing! (lp: #1876286) -- Sebastien Bacher Wed, 17 Jun 2020 23:06:13 +0200 ** Changed in: gnutls28 (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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls28 source package in Xenial: Fix Released Status in gnutls28 source package in Bionic: Fix Released Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Fix Released Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [Impact] Evolution and Claws email clients stopped connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers which are run by the same group. Users are unable to get to their email. The underlying problem is that GnuTLS does not support zero length session tickets. The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." [testcase] GnuTLS 3.6: $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. the error should be fixed with the update GnuTLS 3.5: $ gnutls-cli pop.verizon.net:995 GnuTLS 3.4: $ gnutls-cli -p 995 pop.verizon.net [regression potential] The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). This creates two separate execution paths: 1) If the session ticket length > 0, which is the primary use case, the original code block will be executed. 2) If the session ticket len is 0, then the original code block will be skipped. Testing will need to include connections to servers that return session ticket length > 0 as well as ones that return session ticket length of 0. Wireshark can be used to look at the NewSessionTicket handshake message to confirm the session ticket length. [Other Info] The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and approved by Daiki Ueno: https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 According to the GnuTLS project: "We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the gnutls/build-images subproject and uploads the image at the gitlab.com container registry. The compilation/test phase is on every commit to gnutls project." Here are the results of the gitlab-ci pipeline showing all 19 tests passed for merge request 1260: https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018 Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake message and indicates that a zero length session ticket is a legitimate value: https://tools.ietf.org/pdf/rfc5077.pdf -- When GnuTLS connects to servers that return zero length session tickets using older TLS versions it returns the error code GNUTLS_E_MEMORY_ERROR and the connection is closed. This prevents Evolution and Claws email clients from connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers. Evolution displays the message "Error performing TLS handshake: Internal error in memory allocation" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnutls30 3.5.18-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release
[Group.of.nepali.translators] [Bug 1576471] Re: broken link to raphael.min.js and missing settings in conf file
Zesty is eol. Re-verifying the others, and starting an SRU. ** Changed in: raphael (Ubuntu Zesty) Status: New => Won't Fix -- 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/1576471 Title: broken link to raphael.min.js and missing settings in conf file Status in nzbget package in Ubuntu: Fix Released Status in raphael package in Ubuntu: Fix Released Status in nzbget source package in Trusty: Won't Fix Status in raphael source package in Trusty: New Status in nzbget source package in Xenial: Won't Fix Status in raphael source package in Xenial: New Status in nzbget source package in Zesty: Won't Fix Status in raphael source package in Zesty: Won't Fix Bug description: After a fresh install on 16.04 the symbolic link /usr/share/nzbget/webui/lib/raphael.min.js points a broken link. it *should* point to ../../../javascript/raphael/raphael-min.js also, the default conf file /usr/share/nzbget/webui/nzbget.conf does not have certain required settings set like WebDir and ConfigTemplate also, this can be used as the systemd file /etc/systemd/system/nzbget.service [Unit] Description=NZBGet Daemon Documentation=http://nzbget.net/Documentation After=network.target [Service] User=media Group=media Type=forking ExecStart=/usr/bin/nzbget -c /home/media/.nzbget.conf -D ExecStop=/usr/bin/nzbget -Q ExecReload=/usr/bin/nzbget -O KillMode=process Restart=on-failure [Install] WantedBy=multi-user.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nzbget/+bug/1576471/+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 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
This bug was fixed in the package gnutls28 - 3.5.18-1ubuntu1.4 --- gnutls28 (3.5.18-1ubuntu1.4) bionic; urgency=medium * d/p/50_Update-session_ticket.c-to-add-support-for-zero-leng.patch: - add support for zero length session tickets returned from the server, thanks Rod for the backport and testing! (lp: #1876286) -- Sebastien Bacher Wed, 17 Jun 2020 12:03:27 +0200 ** Changed in: gnutls28 (Ubuntu Bionic) 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls28 source package in Xenial: Fix Committed Status in gnutls28 source package in Bionic: Fix Released Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Fix Released Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [Impact] Evolution and Claws email clients stopped connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers which are run by the same group. Users are unable to get to their email. The underlying problem is that GnuTLS does not support zero length session tickets. The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." [testcase] GnuTLS 3.6: $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. the error should be fixed with the update GnuTLS 3.5: $ gnutls-cli pop.verizon.net:995 GnuTLS 3.4: $ gnutls-cli -p 995 pop.verizon.net [regression potential] The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). This creates two separate execution paths: 1) If the session ticket length > 0, which is the primary use case, the original code block will be executed. 2) If the session ticket len is 0, then the original code block will be skipped. Testing will need to include connections to servers that return session ticket length > 0 as well as ones that return session ticket length of 0. Wireshark can be used to look at the NewSessionTicket handshake message to confirm the session ticket length. [Other Info] The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and approved by Daiki Ueno: https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 According to the GnuTLS project: "We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the gnutls/build-images subproject and uploads the image at the gitlab.com container registry. The compilation/test phase is on every commit to gnutls project." Here are the results of the gitlab-ci pipeline showing all 19 tests passed for merge request 1260: https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018 Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake message and indicates that a zero length session ticket is a legitimate value: https://tools.ietf.org/pdf/rfc5077.pdf -- When GnuTLS connects to servers that return zero length session tickets using older TLS versions it returns the error code GNUTLS_E_MEMORY_ERROR and the connection is closed. This prevents Evolution and Claws email clients from connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers. Evolution displays the message "Error performing TLS handshake: Internal error in memory allocation" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnutls30 3.5.18-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release
[Group.of.nepali.translators] [Bug 1876286] Re: Evolution reports "Error performing TLS handshake: Internal error in memory allocation."
This bug was fixed in the package gnutls28 - 3.6.13-2ubuntu1.2 --- gnutls28 (3.6.13-2ubuntu1.2) focal; urgency=medium * d/p/50_Update-session_ticket.c-to-add-support-for-zero-leng.patch Handle zero length session tickets, fixing connection errors on TLS1.2 sessions to some big hosting providers. (LP: #1876286) -- Sebastien Bacher Mon, 15 Jun 2020 17:10:12 +0200 ** Changed in: gnutls28 (Ubuntu Focal) 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/1876286 Title: Evolution reports "Error performing TLS handshake: Internal error in memory allocation." Status in Gnutls: Unknown Status in claws-mail package in Ubuntu: Invalid Status in evolution package in Ubuntu: Invalid Status in gnutls28 package in Ubuntu: Fix Released Status in gnutls28 source package in Xenial: Fix Committed Status in gnutls28 source package in Bionic: Fix Released Status in claws-mail source package in Focal: Invalid Status in evolution source package in Focal: Invalid Status in gnutls28 source package in Focal: Fix Released Status in claws-mail source package in Groovy: Invalid Status in evolution source package in Groovy: Invalid Status in gnutls28 source package in Groovy: Fix Released Status in gnutls28 package in CentOS: Unknown Bug description: [Impact] Evolution and Claws email clients stopped connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers which are run by the same group. Users are unable to get to their email. The underlying problem is that GnuTLS does not support zero length session tickets. The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). Nominating for SRU, fulfills: "Updates that need to be applied to Ubuntu packages to adjust to changes in the environment, server protocols, web services, and similar, i. e. where the current version just ceases to work." [testcase] GnuTLS 3.6: $ gnutls-cli --priority=NORMAL:-VERS-TLS1.3 pop.verizon.net:995 [...] - Status: The certificate is trusted. *** Fatal error: Internal error in memory allocation. the error should be fixed with the update GnuTLS 3.5: $ gnutls-cli pop.verizon.net:995 GnuTLS 3.4: $ gnutls-cli -p 995 pop.verizon.net [regression potential] The fix works by checking that that ticket_len > 0 prior to calling gnutls_realloc_fast(). This creates two separate execution paths: 1) If the session ticket length > 0, which is the primary use case, the original code block will be executed. 2) If the session ticket len is 0, then the original code block will be skipped. Testing will need to include connections to servers that return session ticket length > 0 as well as ones that return session ticket length of 0. Wireshark can be used to look at the NewSessionTicket handshake message to confirm the session ticket length. [Other Info] The GnuTLS project's merge request 1260 fixes this bug. It was reviewed and approved by Daiki Ueno: https://gitlab.com/gnutls/gnutls/-/merge_requests/1260 According to the GnuTLS project: "We utilize two continuous integration systems, the gitlab-ci and travis. Gitlab-CI is used to test most of the Linux systems (see .gitlab-ci.yml), and is split in two phases, build image creation and compilation/test. The build image creation is done at the gnutls/build-images subproject and uploads the image at the gitlab.com container registry. The compilation/test phase is on every commit to gnutls project." Here are the results of the gitlab-ci pipeline showing all 19 tests passed for merge request 1260: https://gitlab.com/rrivers2/gnutls/-/pipelines/149155018 Page 8, section 3.3 of RFC5077 describes the NewSessionTicket handshake message and indicates that a zero length session ticket is a legitimate value: https://tools.ietf.org/pdf/rfc5077.pdf -- When GnuTLS connects to servers that return zero length session tickets using older TLS versions it returns the error code GNUTLS_E_MEMORY_ERROR and the connection is closed. This prevents Evolution and Claws email clients from connecting to Yahoo, AOL, Verizon, AT, Bell South, etc email servers. Evolution displays the message "Error performing TLS handshake: Internal error in memory allocation" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgnutls30 3.5.18-1ubuntu1.3 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri May 1 07:03:51 2020 InstallationDate: Installed on 2017-12-12 (870 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
[Group.of.nepali.translators] [Bug 827151] Re: Annoying log message "DIGEST-MD5 common mech free"
There's a "new" (2015) Debian bug for this issue, which I linked to the cyrus-sasl2 task. Apparently the regexp in /etc/logcheck/ignore.d.server/libsasl2-modules which is used to ignore the annoying log message doesn't match the log message format of the newer releases. The Debian bug has a patch for it, however it would be better for this change to land in the Debian package. Ubuntu will then pick it up with the next package sync. The Debian bug has seen no activity since 2018. I'll try to poke the maintainers. ** Changed in: cyrus-sasl2 (Debian) Status: Fix Released => Unknown ** Changed in: cyrus-sasl2 (Debian) Remote watch: Debian Bug tracker #631932 => Debian Bug tracker #805310 ** Changed in: cyrus-sasl2 (Ubuntu) Status: Fix Released => Triaged ** Also affects: cyrus-sasl2 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: cyrus-sasl2 (Ubuntu Focal) Status: New => Triaged ** Changed in: cyrus-sasl2 (Ubuntu Focal) Importance: Undecided => Low -- 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/827151 Title: Annoying log message "DIGEST-MD5 common mech free" Status in Cyrus-sasl2: New Status in cyrus-sasl2 package in Ubuntu: Triaged Status in cyrus-sasl2 source package in Trusty: Won't Fix Status in cyrus-sasl2 source package in Xenial: Incomplete Status in cyrus-sasl2 source package in Yakkety: Fix Released Status in cyrus-sasl2 source package in Focal: Triaged Status in cyrus-sasl2 package in Debian: Unknown Bug description: I recently updated the libsasl2-modules to 2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric. That triggered the bug also described in Debian here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932 The annoying message is logged in auth.log. In my case, it is associated with svnserve: svnserve: DIGEST-MD5 common mech free I'm not exactly sure what action triggers the message, but I can investigate more if required. $ lsb_release -rd Description:Ubuntu oneiric (development branch) Release:11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
This bug was fixed in the package openssh - 1:7.2p2-4ubuntu2.10
---
openssh (1:7.2p2-4ubuntu2.10) xenial; urgency=medium
* Fix deadlock when AuthorizedKeysCommand produces a large output.
(LP: #1877454)
- d/p/authkeyscommand-deadlock-01.patch: Make sure to call fclose(2)
and assign NULL to the file handler used to read
"Authorized{Keys,Principal}Command" directives.
- d/p/authkeyscommand-deadlock-02.patch: Consume entire output
generated by the command pointed by
"Authorized{Keys,Principal}Command" in order to avoid sending a
SIGPIPE to the process.
openssh (1:7.2p2-4ubuntu2.9) xenial; urgency=medium
* Apply upstream patch to stop using 2020 as a future date in regress
tests. LP: #1859013
-- Sergio Durigan Junior Wed, 13 May
2020 10:12:28 -0400
** Changed in: openssh (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/1859013
Title:
openssh tests use "not valid yet" certificate from 2020, which is now
valid
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Precise:
New
Status in openssh source package in Trusty:
New
Status in openssh source package in Xenial:
Fix Released
Status in openssh source package in Bionic:
Fix Committed
Status in openssh source package in Disco:
Won't Fix
Status in openssh source package in Eoan:
Fix Committed
Status in openssh source package in Focal:
Fix Released
Bug description:
[Impact]
* regression testsuite uses 1st of January 2020 as the date in the
future, however that is now in the past making autpkgtests fail.
[Test Case]
* Autopkgtest must pass
[Regression Potential]
* Testsuite assertion update only
[Other Info]
This is a staged update to be rolled up with any other openssh update
in the future.
fixed in debian https://tracker.debian.org/news/1092767/accepted-
openssh-181p1-4-source-into-unstable/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+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 1877454] Re: openssh-server hangs with AuthorizedKeysCommand
This bug was fixed in the package openssh - 1:7.2p2-4ubuntu2.10
---
openssh (1:7.2p2-4ubuntu2.10) xenial; urgency=medium
* Fix deadlock when AuthorizedKeysCommand produces a large output.
(LP: #1877454)
- d/p/authkeyscommand-deadlock-01.patch: Make sure to call fclose(2)
and assign NULL to the file handler used to read
"Authorized{Keys,Principal}Command" directives.
- d/p/authkeyscommand-deadlock-02.patch: Consume entire output
generated by the command pointed by
"Authorized{Keys,Principal}Command" in order to avoid sending a
SIGPIPE to the process.
openssh (1:7.2p2-4ubuntu2.9) xenial; urgency=medium
* Apply upstream patch to stop using 2020 as a future date in regress
tests. LP: #1859013
-- Sergio Durigan Junior Wed, 13 May
2020 10:12:28 -0400
** Changed in: openssh (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/1877454
Title:
openssh-server hangs with AuthorizedKeysCommand
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Xenial:
Fix Released
Bug description:
[Impact]
On a default Xenial install, when sshd is configured to obtain the
list of allowed keys using AuthorizedKeysCommand (or the list of
allowed certificate principals using AuthorizedPrincipalsCommand), and
if the command pointed by Authorized{Keys,Principals}Command generates
a lot of output, sshd will hang while reading this same output. In a
nutshell, the problem happens when the subprocess generates enough
data to fill the pipe's buffer; in this scenario, sshd will wait(2) on
the subprocess, which will be blocked trying to write the rest of the
output.
[Test Case]
In order to reproduce the bug, one can:
$ lxc launch ubuntu-daily:xenial openssh-server-bug1877454
$ lxc shell openssh-server-bug1877454
# ssh-keygen
(no need to choose a passphrase for the key, just hit ENTER on all prompts)
# cat > authkeyscommand.sh << __EOF__
#!/bin/bash
cat /root/.ssh/id_rsa.pub
echo
head -c 1M < /dev/urandom
__EOF__
# chmod +x authkeyscommand.sh
# cat >> /etc/ssh/sshd_config << __EOF__
AuthorizedKeysCommand /root/authkeyscommand.sh
AuthorizedKeysCommandUser root
__EOF__
# systemctl reload sshd.service
# ssh root@127.0.0.1
You will notice that ssh will stay there waiting for sshd's reply,
which won't come. The expected result would be for ssh to succeed.
[Regression Potential]
Since the affected code deals with executing a subprocess, reading its
output through a pipe, and then relying on wait(2) to determine
whether the subprocess exited correctly; and considering that this
code is written in C without the help of features like RAII and with
the use of goto statements, we are not able to disconsider the chances
of making a mistake and forgetting to free a resource or to properly
read/write from/to pipes, for example. This is, after all, the reason
the bug happened in the first place.
Having said that, openssh contains extensive tests and the code is
well organized and relatively easy to follow. Upon close inspection,
there doesn't seem to be an evident problem with the backported fixes.
As usual when dealing with a somewhat older distribution, there is
always the possibility of encountering problems because we will be
recompiling openssh using the most recent versions of its build
dependencies.
[Original Description]
Please consider applying this change to openssh-server distributed in Xenial
(16.04).
Without it, sshd can sporadically hang when making use of the
`AuthorizedKeysCommand` option.
https://github.com/openssh/openssh-
portable/commit/ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1877454/+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 1879752] Re: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210
** Changed in: ubuntu-kernel-tests 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/1879752 Title: test_bpf of ubuntu_kernel_selftests.net ADT test failure with linux 4.4.0-180.210 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Bug description: [Impact] Testcase test_bpf of ubuntu_kernel_selftests.net regressed on xenial/linux 4.4.0-180.210. What the test_bpf testcase does is only loading the test_bpf module, which reports the following error: May 20 16:57:21 autopkgtest kernel: [ 88.143826] test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop jited:1 ret -12 != 3055 FAIL (1 times) This is cased by upstream commit 636c2628086e "net: skbuff: Remove errornous length validation in skb_vlan_pop()" which we applied from stable upstream v4.4.223. [Fix] The fix is upstream commit 0d906b1e8d40 "bpf, test: fix ld_abs + vlan push/pop stress test" from v4.9 which can cherry-picked to xenial. [Test case] Load the test_bpf module, it should return no errors. [Regression potential] Low. The fix changes only a bpf test module and was tested to fix the reported issue. Original bug report: - Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20200520_161352_2051b@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20200520_160450_cdd7c@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20200520_152728_5aa07@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20200520_151052_5aa07@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1879752/+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
