[Group.of.nepali.translators] [Bug 1822780] Re: dependency issues in the pymacaroons stack
** Changed in: pymacaroons (Ubuntu Xenial)
Status: Triaged => Invalid
** Changed in: pymacaroons (Ubuntu Xenial)
Assignee: Andreas Hasenack (ahasenack) => (unassigned)
** Changed in: pymacaroons (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1822780
Title:
dependency issues in the pymacaroons stack
Status in pymacaroons package in Ubuntu:
Fix Released
Status in pymacaroons source package in Trusty:
In Progress
Status in pymacaroons source package in Xenial:
Invalid
Bug description:
[Impact]
* The pymacaroons stack has dependency issues identified when further
testing the backport to trusty (currently in proposed)
* Ensure that the pymacaroons stack works well in Trusty (for Ubuntu
Advantage client) but also fix the issues that matter for Xenial in
Xenial as well.
[Test Case]
* install python3-pymacaroons. This will pull in python3-libnacl 1.4.5 as
well (expected)
* Without the latest fix from proposed, this command will backtrace as shown:
$ python3 -c "__requires__ = 'pymacaroons';from pkg_resources import
load_entry_point"
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 444, in
_build_master
ws.require(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 725, in require
needed = self.resolve(parse_requirements(requirements))
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 632, in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (libnacl 1.4.5
(/usr/lib/python3/dist-packages), Requirement.parse('libnacl>=1.3.6,<1.4'))
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 2749, in
working_set = WorkingSet._build_master()
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 446, in
_build_master
return cls._build_from_requirements(__requires__)
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 459, in
_build_from_requirements
dists = ws.resolve(reqs, Environment())
File "/usr/lib/python3/dist-packages/pkg_resources.py", line 628, in resolve
raise DistributionNotFound(req)
pkg_resources.DistributionNotFound: libnacl>=1.3.6,<1.4
* the python3-six dependency check isn't reached, because the check
stops at the first unsatisfied dependency and that happened to be
libnacl. But when testing the fixed packages, there must be no
backtrace like above.
[Fix]
* Changes
- Trusty: drop python2 binaries in trusty (was not released there yet)
Xenial has those already published, we are not gonna take them away.
see [1]
- Trusty: adapt python-six dependency to match what is really needed
and available in Trusty. Xenial has a version higher than that so
don't bother modifying it there.
see [2]
- Trusty and Xenial: adapt python-libnacl dependency by backporting
upstream fix on a too struct version requirement.
see [3]
[1]:
https://git.launchpad.net/~paelzer/ubuntu/+source/pymacaroons/commit/?id=6746ad32b4d785919e849a4bef5685bf0bec6be2
[2]:
https://git.launchpad.net/~paelzer/ubuntu/+source/pymacaroons/commit/?id=f94ac40aeb354c008c4764853b877991003ae429
[3]:
https://git.launchpad.net/~paelzer/ubuntu/+source/pymacaroons/commit/?id=1987dffcffae29c63ea71635db1cfe19badc145f
[Regression Potential]
* Lets split this section for Trusty and Xenial.
a) Xenial only gets slightly relaxed version dependencies, those should
allow pymacaroons to run, but actually never cause any additional
issues.
b) Trusty this isn't released in trusty at all yet (still in proposed
intentionally). Therefore this is one of the few cases I'd call
regression risk next to zero. If anything then issues out of the py2
removal not working as expected, but it seems to be ok in build and
tests.
[Other Info]
* This is related to the SRU in bug 1817665
* Furthermore it is related to the MIR extension to Trusty in
bug 1746772 bug 1817327 and bug 1621386
---
On the extended testing for the SRU in bug 1817665 we found that there
are a few dependency issues that need to be fixed.
Affects X&T:
python-libnacl - depends on <1.4 but xenial (and trusty soon) have 1.4.5
Fix by importing
https://github.com/ecordell/pymacaroons/commit/3924d5b56c42234d0bff3820bc4cb6c4d3f74d8d
Affects T:
python-six - depends on >=1.8.0 - but trusty is on 1.5.2 still
We evaluated if we need to backport six as well (a lot or reverse deps).
We found that the usage of pymacaroon
[Group.of.nepali.translators] [Bug 1822834] Re: linux: 4.4.0-146.172 -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 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- - phase: Packaging - phase-changed: Wednesday, 03. April 2019 03:33 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 03. April 2019 09:31 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 -- builds not complete -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1822834 Title: linux: 4.4.0-146.172 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: 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-signing-to-proposed series: Invalid 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable 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 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- phase: Holding before Promote to Proposed phase-changed: Wednesday, 03. April 2019 09:31 UTC reason: promote-to-proposed: Holding -- builds not complete To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+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 1818880] Re: Deadlock when detaching network interface
** Changed in: cloud-archive/pike Status: Triaged => 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/1818880 Title: Deadlock when detaching network interface Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive mitaka series: New Status in Ubuntu Cloud Archive ocata series: Triaged Status in Ubuntu Cloud Archive pike series: Fix Released Status in Ubuntu Cloud Archive queens series: Fix Released Status in Ubuntu Cloud Archive rocky series: Won't Fix Status in Ubuntu Cloud Archive stein series: Fix Released Status in qemu package in Ubuntu: Fix Released Status in qemu source package in Xenial: Fix Released Status in qemu source package in Bionic: Fix Released Status in qemu source package in Cosmic: Fix Released Status in qemu source package in Disco: Fix Released Bug description: [Impact] Qemu guests hang indefinitely [Description] When running a Qemu guest with VirtIO network interfaces, detaching an interface that's currently being used can result in a deadlock. The guest instance will hang and become unresponsive to commands, and the only option is to kill -9 the instance. The reason for this is a dealock between a monitor and an RCU thread, which will fight over the BQL (qemu_global_mutex) and the critical RCU section locks. The monitor thread will acquire the BQL for detaching the network interface, and fire up a helper thread to deal with detaching the network adapter. That new thread needs to wait on the RCU thread to complete the deletion, but the RCU thread wants the BQL to commit its transactions. This bug is already fixed upstream (73c6e4013b4c rcu: completely disable pthread_atfork callbacks as soon as possible) and included for other series (see below), so we don't need to backport it to Bionic onwards. Upstream commit: https://git.qemu.org/?p=qemu.git;a=commit;h=73c6e4013b4c $ git describe --contains 73c6e4013b4c v2.10.0-rc2~1^2~8 $ rmadison qemu ===> qemu | 1:2.5+dfsg-5ubuntu10.34 | xenial-updates/universe | amd64, ... qemu | 1:2.11+dfsg-1ubuntu7| bionic/universe | amd64, ... qemu | 1:2.12+dfsg-3ubuntu8| cosmic/universe | amd64, ... qemu | 1:3.1+dfsg-2ubuntu2 | disco/universe| amd64, ... [Test Case] Being a racing condition, this is a tricky bug to reproduce consistently. We've had reports of users running into this with OpenStack deployments and Windows Server guests, and the scenario is usually like this: 1) Deploy a 16vCPU Windows Server 2012 R2 guest with a virtio network interface 2) Stress the network interface with e.g. Windows HLK test suite or similar 3) Repeatedly attach/detach the network adapter that's in use It usually takes more than ~4000 attach/detach cycles to trigger the bug. [Regression Potential] Regressions for this might arise from the fact that the fix changes RCU lock code. Since this patch has been upstream and in other series for a while, it's unlikely that it would regressions in RCU code specifically. Other code that makes use of the RCU locks (MMIO and some monitor events) will be thoroughly tested for any regressions with use-case scenarios and scripted runs. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1818880/+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 1821662] Re: [SRU] xfce4-weather-plugin 0.8.11
This bug was fixed in the package xfce4-weather-plugin - 0.8.11-0ubuntu0.18.10.1 --- xfce4-weather-plugin (0.8.11-0ubuntu0.18.10.1) cosmic; urgency=medium * The Sunrise 1.1 API is deprecated, use 2.0 (LP: #1821662) -- Sean Davis Tue, 26 Mar 2019 06:20:57 -0400 ** Changed in: xfce4-weather-plugin (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/1821662 Title: [SRU] xfce4-weather-plugin 0.8.11 Status in xfce4-weather-plugin package in Ubuntu: Fix Released Status in xfce4-weather-plugin source package in Xenial: Fix Committed Status in xfce4-weather-plugin source package in Bionic: Fix Released Status in xfce4-weather-plugin source package in Cosmic: Fix Released Status in xfce4-weather-plugin source package in Disco: Fix Released Bug description: [Impact] * Downstream bug: https://bugzilla.xfce.org/show_bug.cgi?id=14972 * The met.no sunrise API version 1.1, used by xfce4-weather-plugin versions prior to 0.8.11, expired on 2019-02-15. As with previous expirations, this is expected to make the plugin stop working entirely at some point. * Ubuntu 19.04 is unaffected, as xfce4-weather-plugin 0.9.1 includes the newer API * Affected supported releases include: 16.04, 18.04, 18.10 [Test Case] * Add the weather plugin to the Xfce panel. * Right-click on the plugin and select Preferences to configure it. * After configuring the plugin, click on it to show the Weather Report dialog. * Click on the details tab. * With version 0.8.10 and older, the following message is displayed on the weather details: Met.no sunrise API states that this version of the webservice is deprecated, and the plugin needs to be adapted to use a newer version, or it will stop working within a few months. Please file a bug on https://bugzilla.xfce.org if no one else has done so yet. * Alternatively, ~/.xsession-errors will be littered with this message: (wrapper-1.0:1828): weather-WARNING **: 20:09:40.088: Download of astronomical data failed with HTTP Status Code 404, Reason phrase: Not Found * With version 0.8.11 and 0.9.1, the notice and error messages are no longer displayed. Additionally, "Moon phase" should be populated under "Astronomical Data". * Verify that the weather forecast works with the newer version by right-clicking on the plugin and selecting "Refresh". [Regression Potential] * Along with the updated API, this release now uses alternate https connections. If SSL certificates expire (unlikely and rare), these connections will fail: http://geoip.xfce.org/ -> https://geoip.xfce.org/ http://api.geonames.org -> https://secure.geonames.org * Other regression potential is minimal. [0.8.11 Release Notes] - Use the latest sunrise API (2.0) (bug #14972) - Use https for all connections - Fix link to the met.no logo - Translation updates: Albanian, Belarusian, Catalan, Chinese (China), Danish, Dutch, French, Hungarian, Korean, Lithuanian, Russian, Swedish https://git.xfce.org/panel-plugins/xfce4-weather- plugin/log/?h=master-0.8 [ Other Notes ] For those reviewing the code/commits, the API replacement consists of 3 commits: 1. API replacement (not including moonphase): https://git.xfce.org /panel-plugins/xfce4-weather- plugin/commit/?h=master-0.8&id=3653203bd4ac03ee3c6bee7d0e35144a94cc27bb 2. Code improvements: https://git.xfce.org/panel-plugins/xfce4 -weather- plugin/commit/?h=master-0.8&id=f2e44941a70dd92c6e0858b1358b9e3eb148da85 3. Fixing the moonphase integration with the 2.0 API: https://git.xfce.org/panel-plugins/xfce4-weather- plugin/commit/?h=master-0.8&id=1cc55b7fc509a1ccb98b686b1b102b38fe68348d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1821662/+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 1821662] Re: [SRU] xfce4-weather-plugin 0.8.11
This bug was fixed in the package xfce4-weather-plugin - 0.8.11-0ubuntu0.18.04.1 --- xfce4-weather-plugin (0.8.11-0ubuntu0.18.04.1) bionic; urgency=medium * The Sunrise 1.1 API is deprecated, use 2.0 (LP: #1821662) -- Sean Davis Tue, 26 Mar 2019 06:36:43 -0400 ** Changed in: xfce4-weather-plugin (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/1821662 Title: [SRU] xfce4-weather-plugin 0.8.11 Status in xfce4-weather-plugin package in Ubuntu: Fix Released Status in xfce4-weather-plugin source package in Xenial: Fix Committed Status in xfce4-weather-plugin source package in Bionic: Fix Released Status in xfce4-weather-plugin source package in Cosmic: Fix Released Status in xfce4-weather-plugin source package in Disco: Fix Released Bug description: [Impact] * Downstream bug: https://bugzilla.xfce.org/show_bug.cgi?id=14972 * The met.no sunrise API version 1.1, used by xfce4-weather-plugin versions prior to 0.8.11, expired on 2019-02-15. As with previous expirations, this is expected to make the plugin stop working entirely at some point. * Ubuntu 19.04 is unaffected, as xfce4-weather-plugin 0.9.1 includes the newer API * Affected supported releases include: 16.04, 18.04, 18.10 [Test Case] * Add the weather plugin to the Xfce panel. * Right-click on the plugin and select Preferences to configure it. * After configuring the plugin, click on it to show the Weather Report dialog. * Click on the details tab. * With version 0.8.10 and older, the following message is displayed on the weather details: Met.no sunrise API states that this version of the webservice is deprecated, and the plugin needs to be adapted to use a newer version, or it will stop working within a few months. Please file a bug on https://bugzilla.xfce.org if no one else has done so yet. * Alternatively, ~/.xsession-errors will be littered with this message: (wrapper-1.0:1828): weather-WARNING **: 20:09:40.088: Download of astronomical data failed with HTTP Status Code 404, Reason phrase: Not Found * With version 0.8.11 and 0.9.1, the notice and error messages are no longer displayed. Additionally, "Moon phase" should be populated under "Astronomical Data". * Verify that the weather forecast works with the newer version by right-clicking on the plugin and selecting "Refresh". [Regression Potential] * Along with the updated API, this release now uses alternate https connections. If SSL certificates expire (unlikely and rare), these connections will fail: http://geoip.xfce.org/ -> https://geoip.xfce.org/ http://api.geonames.org -> https://secure.geonames.org * Other regression potential is minimal. [0.8.11 Release Notes] - Use the latest sunrise API (2.0) (bug #14972) - Use https for all connections - Fix link to the met.no logo - Translation updates: Albanian, Belarusian, Catalan, Chinese (China), Danish, Dutch, French, Hungarian, Korean, Lithuanian, Russian, Swedish https://git.xfce.org/panel-plugins/xfce4-weather- plugin/log/?h=master-0.8 [ Other Notes ] For those reviewing the code/commits, the API replacement consists of 3 commits: 1. API replacement (not including moonphase): https://git.xfce.org /panel-plugins/xfce4-weather- plugin/commit/?h=master-0.8&id=3653203bd4ac03ee3c6bee7d0e35144a94cc27bb 2. Code improvements: https://git.xfce.org/panel-plugins/xfce4 -weather- plugin/commit/?h=master-0.8&id=f2e44941a70dd92c6e0858b1358b9e3eb148da85 3. Fixing the moonphase integration with the 2.0 API: https://git.xfce.org/panel-plugins/xfce4-weather- plugin/commit/?h=master-0.8&id=1cc55b7fc509a1ccb98b686b1b102b38fe68348d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-weather-plugin/+bug/1821662/+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 1823037] [NEW] amd_iommu possible data corruption
Public bug reported: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* ** Affects: linux (Ubuntu) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Jeff Lane (bladernr) Status: New ** Affects: linux (Ubuntu Cosmic) Importance: Undecided Assignee: Jeff Lane (bladernr) Status: New ** Affects: linux (Ubuntu Disco) Importance: Medium Assignee: Jeff Lane (bladernr) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Xenial) -- 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/1823037 Title: amd_iommu possible data corruption Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: In Progress Bug description: [Impact] If a device has an exclusion range specified in the IVRS table, this region needs to be reserved in the iova-domain of that device. This hasn't happened until now and can cause data corruption on data transfered with these devices. Treat exclusion ranges as reserved regions in the iommu-core to fix the problem. This is a clean cherry pick from mainline of 8aafaaf2212192012f5bae305bb31cdf7681d777 [Test Case] [Fixes] Cherry pick the following from Mainline fd3b3448cf5adc2a2f09b70eaad03c27fe79e7a6 iommu/amd: Reserve exclusion range in iova-domain [Regression Risk] Only affects the amd_iommu driver: drivers/iommu/amd_iommu* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823037/+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 1823045] [NEW] Please ship modules nvme, nvmem_core as built-in
Public bug reported: Built-in nvme is required for support of hibernation to nvme devices; This change is needed only for linux-aws-xenial (bionic and up already have these as built-in). +CONFIG_BLK_DEV_NVME=y +CONFIG_NVMEM=y ** Affects: linux-aws (Ubuntu) Importance: High Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: - Built-in nvme is required for support of hibernation to nvme devices. + Built-in nvme is required for support of hibernation to nvme devices; + This change is needed only for linux-aws-xenial (bionic and up already + have these as built-in). +CONFIG_BLK_DEV_NVME=y +CONFIG_NVMEM=y -- 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/1823045 Title: Please ship modules nvme, nvmem_core as built-in Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Xenial: New Bug description: Built-in nvme is required for support of hibernation to nvme devices; This change is needed only for linux-aws-xenial (bionic and up already have these as built-in). +CONFIG_BLK_DEV_NVME=y +CONFIG_NVMEM=y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823045/+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 1823098] [NEW] /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf
Public bug reported: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-0:~$ cat /etc/*release | DISTRIB_RELEASE=16.04 | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" | VERSION_ID="16.04" | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp | ntp: /etc/init.d/ntp | ubuntu@juju-453c71-0:~$ apt-cache policy ntp | ntp: | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 | Version table: | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages Thanks, Haw ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. + | ubuntu@juju-453c71-0:~$ cat /etc/*release + | DISTRIB_RELEASE=16.04 + | DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS" + | VERSION_ID="16.04" + + | ubuntu@juju-453c71-0:~$ dpkg-query -S /etc/init.d/ntp + | ntp: /etc/init.d/ntp + + | ubuntu@juju-453c71-0:~$ apt-cache policy ntp + | ntp: + | Installed: 1:4.2.8p4+dfsg-3ubuntu5.9 + | Candidate: 1:4.2.8p4+dfsg-3ubuntu5.9 + | Version table: + | *** 1:4.2.8p4+dfsg-3ubuntu5.9 500 + | 500 http://us-central1.gce.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + | 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages + Thanks, Haw ** Also affects: ntp (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1823098 Title: /etc/init.d/ntp prefers DHCP over configured /etc/ntp.conf Status in ntp package in Ubuntu: New Status in ntp source package in Xenial: New Bug description: Hi, On a few instances in a public cloud, mostly seen in GCE, ntp seems incorrectly set up with: | ubuntu@juju-453c71-0:~$ ntpq -pn | remote refid st t when poll reach delay offset jitter | == | *169.254.169.254 71.79.79.71 2 u 737 1024 3770.6570.136 0.147 We have /etc/ntp.conf configured to use ntp.ubuntu.com as a 'pool' host. Turns out, it seems the /etc/init.d/ntp prefers the DHCP version over our configured ntp.conf: | if [ /var/lib/ntp/ntp.conf.dhcp -nt /etc/ntp.conf ]; then | NTPD_OPTS="$NTPD_OPTS -c /var/lib/ntp/ntp.conf.dhcp" | fi | ubuntu@juju-453c71-0:/etc$ ls -la /var/lib/ntp/ntp.conf.dhcp /etc/ntp.conf | -rw-r--r-- 1 root root 626 Feb 25 08:54 /etc/ntp.conf | -rw-r--r-- 1 root root 897 Mar 29 21:00 /var/lib/ntp/ntp.conf.dhcp I think this is wrong, if /etc/ntp.conf is configured, it should use that over what DHCP/dhclient provides. | ubuntu@juju-453c71-
[Group.of.nepali.translators] [Bug 1820326] Re: linux-fips: 4.4.0-1007.9 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 - phase: Ready for Testing - phase-changed: Tuesday, 02. April 2019 10:00 UTC + phase: Holding before Release + phase-changed: Thursday, 04. April 2019 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress + promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present -- 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/1820326 Title: linux-fips: 4.4.0-1007.9 -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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1821724 phase: Holding before Release phase-changed: Thursday, 04. April 2019 03:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- kernel-block/kernel-block-proposed tag present To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820326/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
** Changed in: xserver-xorg-video-intel (Ubuntu) Assignee: josep maso (jmaso) => (unassigned) ** Also affects: xserver-xorg-video-intel (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: xserver-xorg-video-intel-lts-xenial (Ubuntu Trusty) Importance: Undecided Status: New ** No longer affects: xserver-xorg-video-intel-lts-xenial (Ubuntu) -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Trusty: Won't Fix Status in xserver-xorg-video-intel-lts-xenial source package in Trusty: Won't Fix Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
** Changed in: xserver-xorg-video-intel (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: xserver-xorg-video-intel-lts-xenial (Ubuntu Trusty) Status: New => Won't Fix ** Changed in: xserver-xorg-video-intel (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: xserver-xorg-video-intel-lts-xenial (Ubuntu Trusty) Importance: Undecided => Medium ** Bug watch removed: Xfce Bugzilla #5927 https://bugzilla.xfce.org/show_bug.cgi?id=5927 -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Trusty: Won't Fix Status in xserver-xorg-video-intel-lts-xenial source package in Trusty: Won't Fix Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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
