[Group.of.nepali.translators] [Bug 1827727] Re: All plugins disabled due to expired cert
** Changed in: firefox 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/1827727 Title: All plugins disabled due to expired cert Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Status in firefox source package in Xenial: Fix Released Status in firefox source package in Bionic: Fix Released Status in firefox source package in Cosmic: Fix Released Status in firefox source package in Disco: Fix Released Bug description: See https://bugzilla.mozilla.org/show_bug.cgi?id=1548973 Due to expiration of an intermediate cert, all plugins were disabled. Firefox pushed a fix via 'Studies' option, but this seems to be disabled by default in Ubuntu builds? When this is disabled, no update is getting pushed! Think we need to get a fix into repositories asap :) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1827727/+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 1757422] Re: Fix Runtime PM for r8169
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (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/1757422 Title: Fix Runtime PM for r8169 Status in HWE Next: New Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Status in linux-oem source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0, 1.8W when r8169 is in D3. The power saved is substantial. [Fix] Improved rumtime PM logic to let the device gets suspended (D3) when the port is not in used and the link is down. [Test Case] The chip version is 8168h/8111h. Test when no ethernet gets plugged. Powertop shows power consumption is roughly 5.5W. lspci shows the device is in D0. With the patch, The power consumption is reduced to 1.8W. lspci shows the device is in D3, PME# is correctly enabled. Plug ethernet cable can corretly wake up the device. Unplug the cable, the device gets suspended to D3 correctly. [Regression Potential] Medium. - r8169 is so ubiquitous, with lots of different chip versions. It's hard to test all of them. - PCI D3 needs system firmware (ACPI) support, this might hit some plaform bugs. - the code is still in v4.16-rc*, so it's not well tested by end users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1757422/+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 1832576] Re: linux-hwe-edge: 4.15.0-53.57~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta 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: 1832577 - phase: Packaging - phase-changed: Thursday, 13. June 2019 13:37 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:42 UTC reason: - prepare-package-meta: Pending -- package not yet uploaded + promote-to-proposed: Holding -- master bug not ready for proposed 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/1832576 Title: linux-hwe-edge: 4.15.0-53.57~16.04.1 -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: Invalid 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-hwe-edge package in Ubuntu: Invalid Status in linux-hwe-edge source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832577 phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:42 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832576/+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 1832577] Re: linux-hwe: 4.15.0-53.57~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed 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 derivatives: bug 1832576 (linux-hwe-edge) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1832578 - phase: Packaging - phase-changed: Thursday, 13. June 2019 13:05 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:39 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- master bug not ready for proposed 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/1832577 Title: linux-hwe: 4.15.0-53.57~16.04.1 -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 prepare-package-signed 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-hwe package in Ubuntu: Invalid Status in linux-hwe 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 derivatives: bug 1832576 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1832578 phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:39 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832577/+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 1832593] Re: linux: 4.4.0-152.179 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed 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 backports: bug 1832591 (trusty/linux-aws), bug 1832592 (trusty/linux-lts-xenial) derivatives: bug 1832580 (pc-kernel), bug 1832582 (linux-aws), bug 1832583 (linux-kvm), bug 1832585 (linux-raspi2), bug 1832589 (linux-snapdragon), bug 1832590 (linux-fips) -- swm properties -- - phase: Packaging - phase-changed: Thursday, 13. June 2019 10:00 UTC + boot-testing-requested: true + phase: Holding before Promote to Proposed + phase-changed: Monday, 17. June 2019 22:32 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present 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/1832593 Title: linux: 4.4.0-152.179 -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 prepare-package-signed 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 package in Ubuntu: Invalid 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 backports: bug 1832591 (trusty/linux-aws), bug 1832592 (trusty/linux-lts-xenial) derivatives: bug 1832580 (pc-kernel), bug 1832582 (linux-aws), bug 1832583 (linux-kvm), bug 1832585 (linux-raspi2), bug 1832589 (linux-snapdragon), bug 1832590 (linux-fips) -- swm properties -- boot-testing-requested: true phase: Holding before Promote to Proposed phase-changed: Monday, 17. June 2019 22:32 UTC reason: promote-to-proposed: Holding -- manual kernel-block/kernel-block-ppa present variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1832593/+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 1824474] Re: Is Vcs-Git line correct?
This bug was fixed in the package linux-meta-raspi2 - 4.4.0..111 --- linux-meta-raspi2 (4.4.0..111) xenial; urgency=medium * Bump ABI 4.4.0- * Is Vcs-Git line correct? (LP: #1824474) - Vcs-Git: Fix raspi2 branch checkout -- Stefan Bader Thu, 06 Jun 2019 17:41:11 +0200 ** Changed in: linux-meta-raspi2 (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/1824474 Title: Is Vcs-Git line correct? Status in linux-meta-raspi2 package in Ubuntu: In Progress Status in linux-meta-raspi2 source package in Xenial: Fix Released Status in linux-meta-raspi2 source package in Bionic: Fix Released Status in linux-meta-raspi2 source package in Cosmic: Fix Committed Status in linux-meta-raspi2 source package in Disco: Fix Committed Status in linux-meta-raspi2 source package in Eoan: In Progress Bug description: Impact: apt-get source suggets the wrong instructions when inquiring for linux-meta-raspi2: $ apt-get source linux-meta-raspi2 ... NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. which, if executed, result in a checkout of the master branch in a raspi2 subdirectory (instead of a checkout of the raspi2 branch). Fix: Fix the Vcs-Git line in linux-meta-raspi2/debian/control.common. How to test: Check the output of `apt-get source linux-meta-raspi2`, a fixed version will suggest: ... git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic -b raspi2 ... Regression potential: Very low, trivial modification. -- The control file for the latest version of this package contains: Vcs-Git: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- meta/+git/disco raspi2 This cauases `apt-get source` to suggest: NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. ...which checks out the sources to the raspi2 subdirectory, instead of checking out the raspi2 branch. Is this supposed to be "-b raspi2" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi2/+bug/1824474/+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 1757422] Re: Fix Runtime PM for r8169
This bug was fixed in the package linux-oem - 4.15.0-1043.48 --- linux-oem (4.15.0-1043.48) bionic; urgency=medium [ Ubuntu: 4.15.0-52.56 ] * Remote denial of service (resource exhaustion) caused by TCP SACK scoreboard manipulation (LP: #1831638) - SAUCE: tcp: tcp_fragment() should apply sane memory limits * Remote denial of service (system crash) caused by integer overflow in TCP SACK handling (LP: #1831637) - SAUCE: tcp: limit payload size of sacked skbs -- Stefan Bader Fri, 14 Jun 2019 10:39:16 +0200 ** Changed in: linux-oem (Ubuntu Bionic) 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/1757422 Title: Fix Runtime PM for r8169 Status in HWE Next: New Status in linux-oem package in Ubuntu: New Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Triaged Status in linux-oem source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] r8169 stays in D0 even when no ethernet cable is plugged in. This drains lots of power (~3W). The tested laptop uses 5.5W when r8169 is in D0, 1.8W when r8169 is in D3. The power saved is substantial. [Fix] Improved rumtime PM logic to let the device gets suspended (D3) when the port is not in used and the link is down. [Test Case] The chip version is 8168h/8111h. Test when no ethernet gets plugged. Powertop shows power consumption is roughly 5.5W. lspci shows the device is in D0. With the patch, The power consumption is reduced to 1.8W. lspci shows the device is in D3, PME# is correctly enabled. Plug ethernet cable can corretly wake up the device. Unplug the cable, the device gets suspended to D3 correctly. [Regression Potential] Medium. - r8169 is so ubiquitous, with lots of different chip versions. It's hard to test all of them. - PCI D3 needs system firmware (ACPI) support, this might hit some plaform bugs. - the code is still in v4.16-rc*, so it's not well tested by end users. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1757422/+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 1824474] Re: Is Vcs-Git line correct?
This bug was fixed in the package linux-meta-raspi2 - 4.15.0.1038.36 --- linux-meta-raspi2 (4.15.0.1038.36) bionic; urgency=medium * Bump ABI 4.15.0-1038 * Is Vcs-Git line correct? (LP: #1824474) - Vcs-Git: Fix raspi2 branch checkout -- Thadeu Lima de Souza Cascardo Wed, 05 Jun 2019 15:51:57 -0300 ** Changed in: linux-meta-raspi2 (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/1824474 Title: Is Vcs-Git line correct? Status in linux-meta-raspi2 package in Ubuntu: In Progress Status in linux-meta-raspi2 source package in Xenial: Fix Committed Status in linux-meta-raspi2 source package in Bionic: Fix Released Status in linux-meta-raspi2 source package in Cosmic: Fix Committed Status in linux-meta-raspi2 source package in Disco: Fix Committed Status in linux-meta-raspi2 source package in Eoan: In Progress Bug description: Impact: apt-get source suggets the wrong instructions when inquiring for linux-meta-raspi2: $ apt-get source linux-meta-raspi2 ... NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. which, if executed, result in a checkout of the master branch in a raspi2 subdirectory (instead of a checkout of the raspi2 branch). Fix: Fix the Vcs-Git line in linux-meta-raspi2/debian/control.common. How to test: Check the output of `apt-get source linux-meta-raspi2`, a fixed version will suggest: ... git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic -b raspi2 ... Regression potential: Very low, trivial modification. -- The control file for the latest version of this package contains: Vcs-Git: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- meta/+git/disco raspi2 This cauases `apt-get source` to suggest: NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. ...which checks out the sources to the raspi2 subdirectory, instead of checking out the raspi2 branch. Is this supposed to be "-b raspi2" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi2/+bug/1824474/+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 1735420] Re: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x
Since we already reached the stabilization phase of xenial/16.04 with .5 (and .6), with the focus on stability and security, and because this is not a really bug, rather than 'nice to have' to _not_ show /dev/kvm in case already running virtualized on KVM (because nested KVM is not supported on s390x), I'm now going to change this Bug to Won't Fix. In anybody objects please leave a comment ... ** Changed in: ubuntu-z-systems 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/1735420 Title: Avoid creation of /dev/kvm in Xenial KVM virtual machines on s390x Status in Ubuntu on IBM z Systems: Won't Fix Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: Since nested virtualization with KVM is not supported on s390x, please disable this in Xenial - in case it's doable with reasonable effort. (I think it was already disabled for later Ubuntu releases ... was also discussed on IRC) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1735420/+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 1830635] Re: Regression: xenial: Uses apt_pkg.Error, which is only available in later versions
This bug was fixed in the package python-apt -
1.1.0~beta1ubuntu0.16.04.5
---
python-apt (1.1.0~beta1ubuntu0.16.04.5) xenial; urgency=medium
* Fix erronous use of apt_pkg.Error
apt_pkg.Error was introduced in later versions, and accidentally
used when backporting fixes in the previous SRU. (LP: #1830635)
* Update mirror lists
-- Julian Andres Klode Mon, 27 May 2019 18:05:12
+0200
** Changed in: python-apt (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/1830635
Title:
Regression: xenial: Uses apt_pkg.Error, which is only available in
later versions
Status in python-apt source package in Xenial:
Fix Released
Bug description:
[Impact]
The last SRU introduced a regression in error handling, where apt_pkg.Error
is being caught - but that class is not available in xenial - it still uses
SystemError
[Test case]
Run python3 -c "import apt; apt.Cache().update()" while running apt
update.
You should see:
#
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 468, in update
raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/lib/apt/lists/lock
Currently you see:
#
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apt/cache.py", line 63, in __enter__
return self._lock.__enter__()
SystemError: E:Could not get lock /var/lib/apt/lists/lock - open (11:
Resource temporarily unavailable)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/apt/cache.py", line 481, in update
with _WrappedLock(apt_pkg.config.find_dir("Dir::State::Lists")):
File "/usr/lib/python3/dist-packages/apt/cache.py", line 64, in __enter__
except apt_pkg.Error as e:
AttributeError: module 'apt_pkg' has no attribute 'Error'
[Regression potential]
It really can't get worse than this. But FWIW: This only affects code paths
where we could not lock the lists/ or archives/ directory - they currently
throw the AttributeError, and will then throw LockFailedException again - as
they did before the SRU.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/xenial/+source/python-apt/+bug/1830635/+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 1822204] Re: open-vm-tools 10.3.10 released
This bug was fixed in the package open-vm-tools - 2:10.3.10-1~ubuntu0.18.10.1 --- open-vm-tools (2:10.3.10-1~ubuntu0.18.10.1) cosmic; urgency=medium * Backport recent open-vm-tools (LP: #1822204) open-vm-tools (2:10.3.10-1) unstable; urgency=high * [122e511] Update upstream source from tag 'upstream/10.3.10' Update to upstream version '10.3.10' with Debian dir fb12c7cfc99a9497795475c29306e78d08cc3712 - Closes: #925940 - Bugfix release for the 10.3 series. - Correct and/or improve handling of certain quiesced snapshot failures (shipped as patch in 2:10.3.5-6). - Fix some bad derefs in primary NIC gather code - Fix possible security issue with the permissions of the intermediate staging directory and path. Closes: #925959 - CONSTANT_EXPRESSION_RESULT in TimeUtil_StringToDate() Found by coverity. - Deploypkg log files of linux should not be world readable. They might contain sensitive data. - General code clean-up: - Treat local variables "len" consistently as "size_t" type in Posix_Getmntent_r() - Improve readability of error handling logic in ShrinkDoWipeAndShrink() and remove another line of dead code. - Setting "errno" to ENOENT when there is no passwd entry for the user. - Fix NULL pointer dereference and remove three lines of dead code. - Other changes/fixes, not related to Debian: - Update copyright years - Fix CentOS 7.6 detection - Include vmware/tools/log.h to define g_info (fix for SLES) - Special-case profile loading for StartProgram (Win32 only) - Changes to common source files not applicable to open-vm-tools. (Code used by other vmware tools, unrelated to open-vm-tools). - Bump up the SYSIMAGE_VERSION for VMware tools 10.3.10 * [18de70f] Removing backported patches, shipped in 10.3.10. open-vm-tools (2:10.3.5-8) unstable; urgency=medium [ Jean-Baptiste Lallement ] * [0f35aee] Add modaliases to open-vm-tools-desktop. Added Modaliases to open-vm-tools-desktop to auto-discover and auto-install the driver on Ubuntu via ubuntu-drivers. The driver is then installed at installation time and available on first boot for an improved user experience (LP: #1819207) [ Bernd Zeimetz ] * [dc4e1ce] Load vmwgfx module before vmtoolsd starts. As discussed on github in vmware/open-vm-tools#214 we need to load the vmwgfx module before starting vmtoolsd for desktop users. Otherwise it is not able to retrieve the KMS resolutions and resizing the VM desktop fails. Thanks to @thomashvmw @rhertzog (Closes: #924518) -- Christian Ehrhardt Tue, 14 May 2019 09:05:46 +0200 ** Changed in: open-vm-tools (Ubuntu Cosmic) 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/1822204 Title: open-vm-tools 10.3.10 released Status in open-vm-tools package in Ubuntu: Fix Released Status in open-vm-tools source package in Xenial: Won't Fix Status in open-vm-tools source package in Bionic: Fix Released Status in open-vm-tools source package in Cosmic: Fix Released Status in open-vm-tools package in Debian: Fix Released Bug description: [Impact] * Without SRUing the newer version users get issues running on more recent hypervisors - this is a case of [1] in the SRU policy. * Furthermore Upstream releases this as a collection of fixes which is usually worth to pick up. * This is not backporting a single fix, but the version of a latter Ubuntu release [Test Case] * TL;DR is "use open-vm-tools" but that can be quite complex for the variety of potential Host versions. * VMWare itself took ownership of verifying these backports and will test the same bits from a PPA and the SRU for the official "ack" * We tried upgrading and the setup that I had available, everybody that has different setups is invited to test theirs. * In general I recommend to give this some extra time in -proposed to see if anybody comes up with issues on this. [Regression Potential] * It is a new version which might contain new issues. This time a bit safer than the last one thou, as we have already backported some bigger changes between 10.3.5 -> 10.3.10 with individual SRUs so the remaining changes should be rather safe. [Other Info] * This time this is only the MRE, no extra bugs (with extra test/verification descriptions) are associated. * As agreed back when processing bug 1741390 the real verification of open-vm-tools for having the proper test matrix and project ownership is on VMWare. [1]:
[Group.of.nepali.translators] [Bug 1822204] Re: open-vm-tools 10.3.10 released
This bug was fixed in the package open-vm-tools - 2:10.3.10-1~ubuntu0.18.04.1 --- open-vm-tools (2:10.3.10-1~ubuntu0.18.04.1) bionic; urgency=medium * Backport recent open-vm-tools (LP: #1822204) open-vm-tools (2:10.3.10-1) unstable; urgency=high * [122e511] Update upstream source from tag 'upstream/10.3.10' Update to upstream version '10.3.10' with Debian dir fb12c7cfc99a9497795475c29306e78d08cc3712 - Closes: #925940 - Bugfix release for the 10.3 series. - Correct and/or improve handling of certain quiesced snapshot failures (shipped as patch in 2:10.3.5-6). - Fix some bad derefs in primary NIC gather code - Fix possible security issue with the permissions of the intermediate staging directory and path. Closes: #925959 - CONSTANT_EXPRESSION_RESULT in TimeUtil_StringToDate() Found by coverity. - Deploypkg log files of linux should not be world readable. They might contain sensitive data. - General code clean-up: - Treat local variables "len" consistently as "size_t" type in Posix_Getmntent_r() - Improve readability of error handling logic in ShrinkDoWipeAndShrink() and remove another line of dead code. - Setting "errno" to ENOENT when there is no passwd entry for the user. - Fix NULL pointer dereference and remove three lines of dead code. - Other changes/fixes, not related to Debian: - Update copyright years - Fix CentOS 7.6 detection - Include vmware/tools/log.h to define g_info (fix for SLES) - Special-case profile loading for StartProgram (Win32 only) - Changes to common source files not applicable to open-vm-tools. (Code used by other vmware tools, unrelated to open-vm-tools). - Bump up the SYSIMAGE_VERSION for VMware tools 10.3.10 * [18de70f] Removing backported patches, shipped in 10.3.10. open-vm-tools (2:10.3.5-8) unstable; urgency=medium [ Jean-Baptiste Lallement ] * [0f35aee] Add modaliases to open-vm-tools-desktop. Added Modaliases to open-vm-tools-desktop to auto-discover and auto-install the driver on Ubuntu via ubuntu-drivers. The driver is then installed at installation time and available on first boot for an improved user experience (LP: #1819207) [ Bernd Zeimetz ] * [dc4e1ce] Load vmwgfx module before vmtoolsd starts. As discussed on github in vmware/open-vm-tools#214 we need to load the vmwgfx module before starting vmtoolsd for desktop users. Otherwise it is not able to retrieve the KMS resolutions and resizing the VM desktop fails. Thanks to @thomashvmw @rhertzog (Closes: #924518) -- Christian Ehrhardt Tue, 14 May 2019 09:07:32 +0200 ** Changed in: open-vm-tools (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/1822204 Title: open-vm-tools 10.3.10 released Status in open-vm-tools package in Ubuntu: Fix Released Status in open-vm-tools source package in Xenial: Won't Fix Status in open-vm-tools source package in Bionic: Fix Released Status in open-vm-tools source package in Cosmic: Fix Committed Status in open-vm-tools package in Debian: Fix Released Bug description: [Impact] * Without SRUing the newer version users get issues running on more recent hypervisors - this is a case of [1] in the SRU policy. * Furthermore Upstream releases this as a collection of fixes which is usually worth to pick up. * This is not backporting a single fix, but the version of a latter Ubuntu release [Test Case] * TL;DR is "use open-vm-tools" but that can be quite complex for the variety of potential Host versions. * VMWare itself took ownership of verifying these backports and will test the same bits from a PPA and the SRU for the official "ack" * We tried upgrading and the setup that I had available, everybody that has different setups is invited to test theirs. * In general I recommend to give this some extra time in -proposed to see if anybody comes up with issues on this. [Regression Potential] * It is a new version which might contain new issues. This time a bit safer than the last one thou, as we have already backported some bigger changes between 10.3.5 -> 10.3.10 with individual SRUs so the remaining changes should be rather safe. [Other Info] * This time this is only the MRE, no extra bugs (with extra test/verification descriptions) are associated. * As agreed back when processing bug 1741390 the real verification of open-vm-tools for having the proper test matrix and project ownership is on VMWare. [1]:
[Group.of.nepali.translators] [Bug 1830268] Re: Use changed nested VMX attribute as trigger to refresh libvirt capability cache
This bug was fixed in the package libvirt - 4.6.0-2ubuntu3.6
---
libvirt (4.6.0-2ubuntu3.6) cosmic; urgency=medium
* d/p/ubuntu/lp-1830268-refresh-capabilities-on-KVM-nesting.patch: fix
consideration of VMX flag (LP: #1830268)
-- Christian Ehrhardt Tue, 28 May
2019 07:59:48 +0200
** Changed in: libvirt (Ubuntu Cosmic)
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/1830268
Title:
Use changed nested VMX attribute as trigger to refresh libvirt
capability cache
Status in libvirt package in Ubuntu:
Fix Released
Status in libvirt source package in Xenial:
Invalid
Status in libvirt source package in Bionic:
In Progress
Status in libvirt source package in Cosmic:
Fix Released
Bug description:
[impact]
libvirt caches the 'nested vmx' capability of the host and does not
update that even if the host's capability to handle nested vmx
changes. Having this domcapability missing means no guests are able
to start any nested, kvm-accelerated, guests. Additionally, since
openstack live migration requires matching cpu features, this makes
migrating guests that do have vmx enabled impossible to hosts where
libvirt thinks nested vmx is disabled.
Once the kernel module (kvm_intel) is reloaded with 'nested' enabled,
libvirt does not update its domcapabilities cache, even over a
libvirtd restart, or even over an entire system reboot. Only certain
conditions cause libvirt to update its capabilities cache (possibly
libvirt upgrade, or qemu upgrade, or kernel upgrade...I haven't
verified any of those yet)
libvirt creates caches for its domcapabilities at
/var/cache/libvirt/qemu/capabilities/.
removing the cache xml files there and restarting libvirtd will cause the
caches to be recreated with the correct current values.
The fix backports the upstream fix:
https://libvirt.org/git/?p=libvirt.git;a=commit;h=b183a753
Which makes it always check the current vs the last stored attribute.
[test case]
check the kvm_intel module nested parameter:
$ cat /sys/module/kvm_intel/parameters/nested
Y
it can be Y or N. make sure libvirt agrees with the current setting:
$ virsh domcapabilities | grep vmx
if 'nested' is Y, domcapabilities should include a vmx feature line;
if 'nested' is N, it should have no output (i.e. vmx not supported in
guests).
Then, change the kernel nested setting, and re-check domcapabilities.
Restarting libvirtd doesn't update the cache, and even rebooting the
entire system doesn't update the cache.
$ virsh domcapabilities | grep vmx
$ cat /sys/module/kvm_intel/parameters/nested
N
$ sudo rmmod kvm_intel
$ sudo modprobe kvm_intel nested=1
$ cat /sys/module/kvm_intel/parameters/nested
Y
$ virsh domcapabilities | grep vmx
$ sudo systemctl restart libvirtd
$ virsh domcapabilities | grep vmx
$
Not only should it work, but further configurung libvirt debug [1] the fix
should leave a message like this when triggering:
VIR_DEBUG("Outdated capabilities for '%s': kvm kernel nested "
"value changed from %d",)
Test #2:
- restart libvirtd
- call `virsh domcapabilities`
- repeat the above
- this should later on use the cache (faster)
- If it always regenerates the cache (see spawned qemu's and new file
dates) the detection is wrong
Test #3:
- some arches (e.g. s390x) don't have this attribute, check on one of those
how their behavior changes.
[regression potential]
This will make libvirt refresh the capability cache more often. This is a
quite expensive tasks (depending on the number of qemu's installed which can be
anything from none to all arch emulators and the kvm based ones ~10. Those will
be forked and probed again. The new code now adds a rather safe detection as
the nested attribute would usually only change on a reboot or a module reload.
So it should be rather safe. The one real regression would be if the detection
would be wrong and always trigger.
I added Test #2 above to check for that.
[other info]
related RH bugs, though no changes appear to have resulted from either:
https://bugzilla.redhat.com/show_bug.cgi?id=1474874
https://bugzilla.redhat.com/show_bug.cgi?id=1650950
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1830268/+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
