[Group.of.nepali.translators] [Bug 1703995] Re: linux: 4.4.0-86.109 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 kernel-stable-phase-changed:Friday, 14. July 2017 05:33 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1703995 Title: linux: 4.4.0-86.109 -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: Confirmed 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 kernel-stable-phase-changed:Friday, 14. July 2017 05:33 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703995/+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 1703998] Re: linux-raspi2: 4.4.0-1063.71 -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 ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 + kernel-stable-phase-changed:Friday, 14. July 2017 05:34 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 - kernel-stable-phase-changed:Friday, 14. July 2017 05:34 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1703998 Title: linux-raspi2: 4.4.0-1063.71 -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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703998/+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 1704003] Re: linux-gke: 4.4.0-1020.20 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 + kernel-stable-phase-changed:Friday, 14. July 2017 05:30 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 - kernel-stable-phase-changed:Friday, 14. July 2017 05:30 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1704003 Title: linux-gke: 4.4.0-1020.20 -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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gke package in Ubuntu: Invalid Status in linux-gke source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704003/+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 1703995] Re: linux: 4.4.0-86.109 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 + kernel-stable-phase-changed:Friday, 14. July 2017 05:33 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 kernel-stable-phase-changed:Friday, 14. July 2017 05:33 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- 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/1703995 Title: linux: 4.4.0-86.109 -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: Confirmed 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1703996 derivatives: 1703998,1703999,1704001,1704003,1704004 kernel-stable-phase-changed:Friday, 14. July 2017 05:33 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703995/+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 1703999] Re: linux-snapdragon: 4.4.0-1065.70 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 + kernel-stable-phase-changed:Friday, 14. July 2017 05:31 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 - kernel-stable-phase-changed:Friday, 14. July 2017 05:31 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1703999 Title: linux-snapdragon: 4.4.0-1065.70 -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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1703999/+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 1704001] Re: linux-aws: 4.4.0-1024.33 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 + kernel-stable-phase-changed:Friday, 14. July 2017 05:30 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 - kernel-stable-phase-changed:Friday, 14. July 2017 05:30 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1704001 Title: linux-aws: 4.4.0-1024.33 -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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704001/+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 1684034] Re: Some Dell and Lenovo systems do not work after BIOS Capsule Update
Yakkety is EOL in a week, so there's closing the Yakkety tasks given that no one has uploaded a package yet (which would likely take a week or more to get through the verification pipe). ** Changed in: fwupdate (Ubuntu Yakkety) Status: In Progress => Won't Fix ** Changed in: fwupdate-signed (Ubuntu Yakkety) 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/1684034 Title: Some Dell and Lenovo systems do not work after BIOS Capsule Update Status in fwupdate package in Ubuntu: Fix Released Status in fwupdate-signed package in Ubuntu: Fix Released Status in fwupdate source package in Xenial: Fix Committed Status in fwupdate-signed source package in Xenial: Fix Committed Status in fwupdate source package in Yakkety: Won't Fix Status in fwupdate-signed source package in Yakkety: Won't Fix Status in fwupdate source package in Zesty: Fix Released Status in fwupdate-signed source package in Zesty: Fix Released Bug description: [Impact] This bug is found on Ubuntu 16.04 with fwupdate 0.5-2ubuntu4, but not found on Ubuntu 17.04 with fwupdate 9-1. The newer version of capsule flashing tools in Ubuntu 17.04 supports the reset type from some querycapsuleinfo call： https://github.com/rhinstaller/fwupdate/commit/f1cc489783d2054e90fa6bebc3732e7ea8bb3722 [Test Case] == fwupdate == On a system with a capsule update available, perform capsule update using fwupdate. Verify the system works properly after the update. == efivar == We avoided the upgrade of efivar so we don't need to validate its reverse-dependencies. [Regression Potential] Any vendors that relied upon the previous functionality (hardcoded to warm reset rather than querying for reset types) may have problems. This is actually a BIOS problem in those situations. It's unlikely that this should happen though because querying for reset types more closely aligns to the implementations that other OSes use when applying capsule updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1684034/+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 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades
An upload of shim-signed to trusty-proposed has been rejected from the upload queue for the following reason: "needs adjusted versioned dep on grub2-common; drop ref to LP: #1624096 from changelog". ** Changed in: unattended-upgrades (Ubuntu Trusty) Status: New => Invalid ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Invalid ** Changed in: unattended-upgrades (Ubuntu Yakkety) 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/1673817 Title: update-secure-boot-policy behaving badly with unattended-upgrades Status in shim-signed package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in shim-signed source package in Trusty: New Status in unattended-upgrades source package in Trusty: Invalid Status in shim-signed source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Invalid Status in shim-signed source package in Yakkety: Fix Released Status in unattended-upgrades source package in Yakkety: Invalid Bug description: [Impact] Any user with unattended upgrades enabled and DKMS packages in a Secure Boot environment might be prompted to change Secure Boot policy, which will fail and crash in unattended-upgrades. [Test case] = unattended upgrade = 1) Create /var/lib/dkms/TEST-DKMS 2) Install new package 3) Trigger unattended-upgrades: unattended-upgrades -d Upgrade should run smoothly for all the processing but fail to complete; shim-signed should end the unattended upgrade with a error as unattended change of the Secure Boot policy can not be done. Upgrade should not hang in high CPU usage. = standard upgrade = 1) Create /var/lib/dkms/TEST-DKMS 2) install new package. 3) Verify that the upgrade completes normally. [Regression Potential] Any failure to prompt for or change Secure Boot policy in mokutil while in an *attended* upgrade scenario would constitute a regression of this SRU. Any other issues related to booting in Secure Boot mode should instead be directed to bug 1637290 (shim update). --- Currently, unattended-upgrades will automatically install all updates for those running development releases of Ubuntu (LP: #1649709) Today, my computer was acting very sluggish. Looking at my process list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU. I killed the process. I have a /var/crash/shim-signed.0.crash but since it's 750 MB, I didn't bother submitting it or looking at it more. Maybe it crashed because I killed the process. Also, I see that unattended-upgrades-dpkg.log is 722 MB. Today's update included both VirtualBox and the linux kernel. I am attaching an excerpt of /var/log/unattended-upgrades/unattended- upgrades-dpkg.log This message was repeated a very large number of times (but I only included it once in the attachment: "Invalid password The Secure Boot key you've entered is not valid. The password used must be between 8 and 16 characters." ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 17 11:15:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-23 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219) SourcePackage: shim-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673817/+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 1704151] Re: Security Advisory - July 11 2017: CVE-2017-7529
** Changed in: nginx (Ubuntu Zesty) Status: Confirmed => Fix Released ** Changed in: nginx (Ubuntu Yakkety) Status: Confirmed => Fix Released ** Changed in: nginx (Ubuntu Xenial) Status: Confirmed => Fix Released ** Changed in: nginx (Ubuntu Trusty) Status: Confirmed => Won't Fix ** Changed in: nginx (Ubuntu Trusty) Status: Won't Fix => 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/1704151 Title: Security Advisory - July 11 2017: CVE-2017-7529 Status in nginx package in Ubuntu: In Progress Status in nginx source package in Trusty: Fix Released Status in nginx source package in Xenial: Fix Released Status in nginx source package in Yakkety: Fix Released Status in nginx source package in Zesty: Fix Released Status in nginx source package in Artful: In Progress Bug description: It was reported by NGINX that there was a security vulnerability. Specifically that: A specially crafted request might result in an integer overflow and incorrect processing of ranges in the range filter, potentially resulting in sensitive information leak. -- Refer to original notice here: http://mailman.nginx.org/pipermail /nginx-announce/2017/000200.html Copy of the message contents below: Hello! A security issue was identified in nginx range filter. A specially crafted request might result in an integer overflow and incorrect processing of ranges, potentially resulting in sensitive information leak (CVE-2017-7529). When using nginx with standard modules this allows an attacker to obtain a cache file header if a response was returned from cache. In some configurations a cache file header may contain IP address of the backend server or other sensitive information. Besides, with 3rd party modules it is potentially possible that the issue may lead to a denial of service or a disclosure of a worker process memory. No such modules are currently known though. The issue affects nginx 0.5.6 - 1.13.2. The issue is fixed in nginx 1.13.3, 1.12.1. For older versions, the following configuration can be used as a temporary workaround: max_ranges 1; Patch for the issue can be found here: http://nginx.org/download/patch.2017.ranges.txt -- Maxim Dounin http://nginx.org/ -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1704151/+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 1448164] Re: runit cannot be installed (Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused)
** Also affects: xpl-perl 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/1448164 Title: runit cannot be installed (Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused) Status in xpl-perl: New Status in runit package in Ubuntu: Fix Released Status in runit source package in Xenial: Triaged Bug description: In Ubuntu 15.04 "runit" cannot be installed. postinst fails with the following message: start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused Due to this error, packages depending on runit, like git-daemon-run, cannot be installed as well. To manage notifications about this bug go to: https://bugs.launchpad.net/xpl-perl/+bug/1448164/+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 1494992] Re: 100% CPU when the History or Wallpaper Selector panels are open
** Changed in: variety (Ubuntu Yakkety) 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/1494992 Title: 100% CPU when the History or Wallpaper Selector panels are open Status in Variety: Fix Committed Status in variety package in Ubuntu: Fix Released Status in variety source package in Xenial: Incomplete Status in variety source package in Yakkety: Won't Fix Status in variety source package in Zesty: Fix Committed Status in variety source package in Artful: Fix Released Bug description: Version:0.5.4 DE:Cinnamon 2.6.13 OS:Linux Mint 17.2 When you chnage the backgroud in the history panel or scroll in it the CPU utilisation goes up to 100% and stay there. I need to close the panel and reopen it to restore the utilisation back to normal. The problem seem also to be in the download history panel and the selection of background too. Below is the SRU information by James Lu (https://launchpad.net/~tacocat) [Impact] * The autoscroll feature in Variety's Wallpaper Selector dialog before commit https://bazaar.launchpad.net/~variety/variety/trunk/revision/592 consumes excessive amounts of CPU after leaving the autoscroll area. This affects both the "History" and "Wallpaper Selector" options found in Variety's menu. * Although this bug doesn't cause any serious damage, pegging a machine's CPU is quite annoying and users will notice whirring fans and reduced battery life as a result. * The proposed fix adds a missing line to clear the autoscroll state when leaving the wallpaper selector. This way, the code in _autoscroll_thread() (which polls for whether the mouse is over the wallpaper selector) doesn't instantly succeed and create an infinite loop. [Test Case] 1) Select one or more wallpaper sources so that in the Wallpaper Selector, scrolling is needed to show all items. 2) Open the wallpaper selector, either by focusing on a wallpaper source in the preferences dialog, or by choosing the "Wallpaper Selector" option in Variety's tray menu. 3) Move the mouse over any of the images in the wallpaper selector. 4) Move the mouse away from the wallpaper selector. A CPU spike in Variety should appear now. - Note that this CPU spike is different from any initial CPU spikes when the wallpaper selector first opens, as that is due to Variety generating all the thumbnails on the spot. The CPU spike mentioned in this bug lasts as long as the wallpaper selector is open and the mouse is not over it, while the initial spikes are temporary (they always last less than 5 seconds for me) [Regression Potential] * This patch affects the autoscroll portion of the wallpaper selector. Should this patch be erroneous, some symptoms could include autoscroll or the entire wallpaper selector not working entirely. * Syntax or variable name errors will, on the other hand, raise Python exceptions and possibly cause Variety to fail to start entirely. [Other Info] * The original patch fixing this bug was included in Debian release 0.6.3-5, which has been in Debian stretch for about 2 months and artful for a similar time (I don't remember the exact date of the relevant sync). No new bugs related to this issue have been opened since in Debian and Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/variety/+bug/1494992/+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 1602813] Re: openvpn-auth-ldap causing segfault on network timeout
Hello Foxpass, or anyone else affected, Accepted openvpn-auth-ldap into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openvpn- auth-ldap/2.0.3-6.1ubuntu0.17.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: openvpn-auth-ldap (Ubuntu Yakkety) Status: In Progress => Won't Fix ** Changed in: openvpn-auth-ldap (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-zesty ** Changed in: openvpn-auth-ldap (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-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/1602813 Title: openvpn-auth-ldap causing segfault on network timeout Status in openvpn-auth-ldap package in Ubuntu: Fix Released Status in openvpn-auth-ldap source package in Trusty: Fix Committed Status in openvpn-auth-ldap source package in Xenial: Fix Committed Status in openvpn-auth-ldap source package in Yakkety: Won't Fix Status in openvpn-auth-ldap source package in Zesty: Fix Committed Status in openvpn-auth-ldap package in Debian: New Bug description: [Impact] There is a timeout bug in the openvpn-auth-ldap package that causes OpenVPN to crash when the network timeout is exceeded. The openvpn-auth-ldap plugin is not correctly checking the error codes from ldap_result. As a result, it is not catching timeouts, and proceeds as if ldap_result was successful. This results in a segfault when access to the result (which is set to Null) is attempted. Network timeouts are somewhat common and services should be resilient to it. Having a service as a whole crash because of such an occurrence is not acceptable. This upload fixes the problem by simply including the timeout error case in an existing check. It was clearly just an oversight in that one call, as the remainder of the code does handle timeout errors. It was just never reached. [Test Case] To reproduce the problem in an openvpn server: * install openvpn and openvpn-auth-ldap: $ sudo apt install openvpn openvpn-auth-ldap * expand the attached openvpn-test-server.tar.gz tarball inside /etc: $ sudo tar -C /etc -xzf openvpn-test-server.tar.gz * start nc on port 389: $ sudo nc -l -p 389 * In another terminal, start the openvpn server: $ cd /etc/openvpn $ sudo openvpn --config server.conf Next you will need an openvpn client, also configured with the SSL certs as usual, plus "auth-user-pass". This client can be the same for all server tests, if you are testing multiple Ubuntu releases, since what crashes is the server. It also doesn't have to be the fixed package from proposed. * Install openvpn: $ sudo apt install openvpn * Expand the client tarball in /etc: $ sudo tar -C /etc -xzf openvpn-test-client.tar.gz * Edit /etc/openvpn/client.conf and change the "remote " line to point to your openvpn server's hostname * Start the client: $ cd /etc/openvpn $ sudo openvpn --config client.conf * It will prompt you for username and password. The values you provide are irrelevant: (...) Enter Auth Username: asd Enter Auth Password: *** The vulnerable server will crash: root@trusty-openvpn-1602813:/etc/openvpn$ sudo openvpn --config server.conf Tue Jun 20 13:56:55 2017 OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Dec 1 2014 Tue Jun 20 13:56:55 2017 TUN/TAP device tun0 opened Tue Jun 20 13:56:55 2017 Note: Cannot set tx queue length on tun0: Operation not permitted (errno=1) Tue Jun 20 13:56:55 2017 do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 Tue Jun 20 13:56:55 2017 /sbin/ip link set dev tun0 up mtu 1500 Tue Jun 20 13:56:55 2017 /sbin/ip addr add dev tun0 local 10.8.0.1 peer 10.8.0.2 Tue Jun 20 13:56:55 2017 UDPv4 link local (bound): [undef] Tue Jun 20 13:56:55 2017 UDPv4 link remote: [undef] Tue Jun 20 13:56:55 2017 Initialization Sequence Completed openv
[Group.of.nepali.translators] [Bug 1673481] Re: "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau that supports hevc
This bug was fixed in the package mythtv - 2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.10.1 --- mythtv (2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.10.1) yakkety; urgency=medium * Include e4f6e011b6 from upstream mythtv to fix yakkety ftbfs. "error: call of overloaded ‘abs(double)’ is ambiguous" * Fix for error "Failed to initialize A/V Sync" when trying to play hevc/h265 content with vdpau acceleration. (LP: #1673481) -- Dave Chiluk Sun, 02 Jul 2017 22:37:54 -0500 ** Changed in: mythtv (Ubuntu Yakkety) Status: Fix Committed => Fix Released ** Changed in: mythtv (Ubuntu Zesty) 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/1673481 Title: "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau that supports hevc Status in mythtv package in Ubuntu: Fix Released Status in mythtv source package in Xenial: Fix Released Status in mythtv source package in Yakkety: Fix Released Status in mythtv source package in Zesty: Fix Released Status in mythtv source package in Artful: Fix Released Bug description: When trying to play HEVC / h265 / x265 video, frontend fails and reports "Failed to initialize A/V Sync" error when using vdpau. This is identical to upstream https://code.mythtv.org/trac/ticket/12992 [Impact] * When trying to play HEVC / h265 / x265 video, frontend fails and reports "Failed to initialize A/V Sync" error when using vdpau. * Log shows vv mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:5855 (StartPlayer) TV::StartPlayer(): Created player. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2532 (HandleStateChange) TV::HandleStateChange(): Changing from None to WatchingVideo mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:649 (DrawSlice) VidOutVDPAU: Codec is not supported. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2632 (HandleStateChange) TV::HandleStateChange(): Main UI disabled. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:424 (StartTV) TV::StartTV(): Entering main playback loop. mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 (DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice mythfrontend.real: mythfrontend[19461]: I CoreContext screensaver-dbus.cpp:82 (Inhibit) ScreenSaverDBus: Successfully inhibited screensaver via org.freedesktop.ScreenSaver. cookie 1810861299. nom nom mythfrontend.real: mythfrontend[19461]: W CoreContext screensaver-dbus.cpp:87 (Inhibit) ScreenSaverDBus: Failed to disable screensaver: Type of message, '(ss)', does not match expected type '(susu)' mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 (DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice mythfrontend.real: mythfrontend[19461]: I CoreContext screensaver-x11.cpp:149 (DisableDPMS) ScreenSaverX11Private: DPMS Deactivated 1 mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 (DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice mythfrontend.real: mythfrontend[19461]: E CoreContext mythplayer.cpp:1838 (AVSync) Player(0): AVSync: Unknown error in videoOutput, aborting playback. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2275 (HandleStateChange) TV::HandleStateChange(): Attempting to change from WatchingVideo to None ^ * This is identical to upstream https://code.mythtv.org/trac/ticket/12992 [Test Case] 1. Set up mythtv 2. Configure mythtv vdpau video decoder with de-interlacing 3. On frontend play h265/hevc encoded media, with nvidia-375+ and a pascal or newer nvidia card. 4. See error [Regression Potential] * Fix is narrowly applied to hevc/h265 decoding in the vdpau decoder. * Possible but unlikely regressions may be deinterlacing being broken, or vdpau ceasing to function. [Other Info] * https://en.wikipedia.org/wiki/Nvidia_PureVideo . This will only affect video cards that have hevc decoding which is VDPAU Feature set E,F,G,H. * https://code.mythtv.org/trac/ticket/12992 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mythtv-frontend 2:0.28.0+fixes.20160413.15cf421-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 16 09:44:08 2017 InstallationDate: Installed on 2016-01-15 (425 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115) Installed_m
[Group.of.nepali.translators] [Bug 1673481] Re: "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau that supports hevc
This bug was fixed in the package mythtv - 2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.04.1 --- mythtv (2:0.28.0+fixes.20160413.15cf421-0ubuntu2.16.04.1) xenial; urgency=medium * Fix for error "Failed to initialize A/V Sync" when trying to play hevc/h265 content with vdpau acceleration. (LP: #1673481) -- Dave Chiluk Sun, 02 Jul 2017 22:37:54 -0500 ** Changed in: mythtv (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/1673481 Title: "Failed to initialize A/V Sync" error trying to play HEVC h.265 with vdpau that supports hevc Status in mythtv package in Ubuntu: Fix Released Status in mythtv source package in Xenial: Fix Released Status in mythtv source package in Yakkety: Fix Released Status in mythtv source package in Zesty: Fix Released Status in mythtv source package in Artful: Fix Released Bug description: When trying to play HEVC / h265 / x265 video, frontend fails and reports "Failed to initialize A/V Sync" error when using vdpau. This is identical to upstream https://code.mythtv.org/trac/ticket/12992 [Impact] * When trying to play HEVC / h265 / x265 video, frontend fails and reports "Failed to initialize A/V Sync" error when using vdpau. * Log shows vv mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:5855 (StartPlayer) TV::StartPlayer(): Created player. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2532 (HandleStateChange) TV::HandleStateChange(): Changing from None to WatchingVideo mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:649 (DrawSlice) VidOutVDPAU: Codec is not supported. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2632 (HandleStateChange) TV::HandleStateChange(): Main UI disabled. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:424 (StartTV) TV::StartTV(): Entering main playback loop. mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 (DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice mythfrontend.real: mythfrontend[19461]: I CoreContext screensaver-dbus.cpp:82 (Inhibit) ScreenSaverDBus: Successfully inhibited screensaver via org.freedesktop.ScreenSaver. cookie 1810861299. nom nom mythfrontend.real: mythfrontend[19461]: W CoreContext screensaver-dbus.cpp:87 (Inhibit) ScreenSaverDBus: Failed to disable screensaver: Type of message, '(ss)', does not match expected type '(susu)' mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 (DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice mythfrontend.real: mythfrontend[19461]: I CoreContext screensaver-x11.cpp:149 (DisableDPMS) ScreenSaverX11Private: DPMS Deactivated 1 mythfrontend.real: mythfrontend[19461]: E Decoder videoout_vdpau.cpp:559 (DrawSlice) VidOutVDPAU: IsErrored() in DrawSlice mythfrontend.real: mythfrontend[19461]: E CoreContext mythplayer.cpp:1838 (AVSync) Player(0): AVSync: Unknown error in videoOutput, aborting playback. mythfrontend.real: mythfrontend[19461]: I CoreContext tv_play.cpp:2275 (HandleStateChange) TV::HandleStateChange(): Attempting to change from WatchingVideo to None ^ * This is identical to upstream https://code.mythtv.org/trac/ticket/12992 [Test Case] 1. Set up mythtv 2. Configure mythtv vdpau video decoder with de-interlacing 3. On frontend play h265/hevc encoded media, with nvidia-375+ and a pascal or newer nvidia card. 4. See error [Regression Potential] * Fix is narrowly applied to hevc/h265 decoding in the vdpau decoder. * Possible but unlikely regressions may be deinterlacing being broken, or vdpau ceasing to function. [Other Info] * https://en.wikipedia.org/wiki/Nvidia_PureVideo . This will only affect video cards that have hevc decoding which is VDPAU Feature set E,F,G,H. * https://code.mythtv.org/trac/ticket/12992 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mythtv-frontend 2:0.28.0+fixes.20160413.15cf421-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-34.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 16 09:44:08 2017 InstallationDate: Installed on 2016-01-15 (425 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160115) Installed_mythtv_dbg: 2:0.28.0+fixes.20160413.15cf421-0ubuntu2 MythTVDirectoryPermissions: total 4 drwxr-xr-x 2 root root 4096 Jan 7 2016 videos SourcePackage: mythtv UpgradeStatus: No upgrade log present (pr
[Group.of.nepali.translators] [Bug 1679488] Re: Thunar freezes when left inactive for a while
This bug was fixed in the package thunar - 1.6.11-1ubuntu0.17.04.1 --- thunar (1.6.11-1ubuntu0.17.04.1) zesty; urgency=medium * No change backport to zesty - Fixes process hang after inactivity (LP: #1679488) -- Sean Davis Wed, 24 May 2017 21:35:20 -0400 ** Changed in: thunar (Ubuntu Zesty) 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/1679488 Title: Thunar freezes when left inactive for a while Status in thunar package in Ubuntu: Fix Released Status in thunar source package in Xenial: Fix Released Status in thunar source package in Yakkety: Fix Committed Status in thunar source package in Zesty: Fix Released Status in thunar source package in Artful: Fix Released Bug description: [Impact] * Thunar freezes after a period of inactivity. * The process has to completely stopped so the user can resume usage. * Users have reported the issue to happen more frequently when files have been modified in the current directory. * Several affected users have reported the issue resolved with this patch. [Test Case] * Open Thunar and wait. * Use another application to create files in the current directory. * After some time, the application will become unresponsive. [Regression Potential] * The patch eliminates a deadlock in Thunar's file monitor mechanism, so regression potential is small. * Since Thunar will no longer freeze over time with this fix, other bugs could become more pronounced. [Original Report] Thunar keeps constantly freezing when I leave it inactive for a while. I haven't seen it freeze while using it, but when I use some other application for a while and switch back to Thunar window it is often completely frozen and I have to kill it. Zero CPU usage, window not responding. This started to happen a couple of weeks ago. I have the exact same problem in two different installations, one on virtual machine on Windows, other on a Asus Zenbook laptop. Ubuntu 16.04.1 LTS Thunar 1.6.10-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488/+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 1679488] Re: Thunar freezes when left inactive for a while
This bug was fixed in the package thunar - 1.6.11-0ubuntu0.16.04.2 --- thunar (1.6.11-0ubuntu0.16.04.2) xenial; urgency=medium * d/p/02_fix-deadlock-in-mutex-causing-thunar-to-hang.patch: - Fixes process hang after inactivity (LP: #1679488) -- Sean Davis Wed, 24 May 2017 21:40:29 -0400 ** Changed in: thunar (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/1679488 Title: Thunar freezes when left inactive for a while Status in thunar package in Ubuntu: Fix Released Status in thunar source package in Xenial: Fix Released Status in thunar source package in Yakkety: Fix Committed Status in thunar source package in Zesty: Fix Released Status in thunar source package in Artful: Fix Released Bug description: [Impact] * Thunar freezes after a period of inactivity. * The process has to completely stopped so the user can resume usage. * Users have reported the issue to happen more frequently when files have been modified in the current directory. * Several affected users have reported the issue resolved with this patch. [Test Case] * Open Thunar and wait. * Use another application to create files in the current directory. * After some time, the application will become unresponsive. [Regression Potential] * The patch eliminates a deadlock in Thunar's file monitor mechanism, so regression potential is small. * Since Thunar will no longer freeze over time with this fix, other bugs could become more pronounced. [Original Report] Thunar keeps constantly freezing when I leave it inactive for a while. I haven't seen it freeze while using it, but when I use some other application for a while and switch back to Thunar window it is often completely frozen and I have to kill it. Zero CPU usage, window not responding. This started to happen a couple of weeks ago. I have the exact same problem in two different installations, one on virtual machine on Windows, other on a Asus Zenbook laptop. Ubuntu 16.04.1 LTS Thunar 1.6.10-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1679488/+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 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
This bug was fixed in the package gdm3 - 3.24.2-1ubuntu9 --- gdm3 (3.24.2-1ubuntu9) artful; urgency=medium * debian/default.pa - Added new file to disable Bluetooth audio devices in PulseAudio from gdm3. (LP: #1703415) (LP: #1489651) * debian/gdm3.install - Added details of the default.pa file * debian/gdm3.postinst - Added installation of default.pa and creation of dir if it doesn't exist. -- Will Cooke Thu, 13 Jul 2017 12:14:34 +0100 ** Changed in: gdm3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 source package in Xenial: Triaged Status in pulseaudio source package in Xenial: Triaged Status in gdm3 source package in Zesty: Triaged Status in pulseaudio source package in Zesty: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+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 1700551] Re: linux-joule: 4.4.0-1005.10 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/joule/4.4.0-1005.10/joule-4.4-proposed-published.html ** Tags added: certification-testing-passed ** 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/1700551 Title: linux-joule: 4.4.0-1005.10 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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 promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-joule package in Ubuntu: Invalid Status in linux-joule source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1700541 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1700551/+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 1701027] Re: linux-snapdragon: 4.4.0-1064.69 -proposed tracker
*** This bug is a duplicate of bug 1703999 *** https://bugs.launchpad.net/bugs/1703999 ** This bug is no longer a duplicate of bug 1702107 linux-snapdragon: 4.4.0-1064.69 -proposed tracker ** This bug has been marked a duplicate of bug 1703999 linux-snapdragon: -proposed tracker -- 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/1701027 Title: linux-snapdragon: 4.4.0-1064.69 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1701024 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701027/+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 1702107] Re: linux-snapdragon: 4.4.0-1064.69 -proposed tracker
*** This bug is a duplicate of bug 1703999 *** https://bugs.launchpad.net/bugs/1703999 ** This bug has been marked a duplicate of bug 1703999 linux-snapdragon: -proposed tracker -- 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/1702107 Title: linux-snapdragon: 4.4.0-1064.69 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1702103 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702107/+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 1702110] Re: linux-joule: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => 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/1702110 Title: linux-joule: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-joule package in Ubuntu: Invalid Status in linux-joule source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1702103 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702110/+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 1584485] Re: Upgrading samba to latest security fixes together with winbind in nsswitch.conf can harm entire OS
Revised fix-1584485.patch that includes a missing library in the static build to fix bug #1677329. Patch submitted upstream to samba-technical awaiting feedback. ** Patch added: "fix-1584485-take2.patch" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/+attachment/4914111/+files/fix-1584485-take2.patch ** Changed in: samba (Ubuntu) Status: Fix Released => Triaged -- 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/1584485 Title: Upgrading samba to latest security fixes together with winbind in nsswitch.conf can harm entire OS Status in samba package in Ubuntu: Incomplete Status in samba source package in Trusty: Fix Released Status in samba source package in Xenial: Fix Committed Status in samba source package in Yakkety: Fix Committed Status in samba package in Debian: New Bug description: [Impact] * Upgrading samba when using winbind as NSS service can break OS. * Probably not triggered if "compat" is BEFORE "winbind" in nsswitch.conf. * Huge impact due to big version different between winbind and libraries. [Test Case 1] Verify that the regression reported in bug 1644428 has not recurred. [Test Case 2] 1) Start an ubuntu Trusty container 2) cp /etc/apt/sources.list /etc/apt/sources.list.back 3) Disable the trusty-updates and trusty-security archives in /etc/apt/sources.list 4) sudo apt-get update 5) sudo apt-get install samba winbind libnss-winbind libpam-winbind 6) Set /etc/nsswitch.conf to : passwd: winbind compat 7) Restart the services 7.1) sudo restart smbd 7.2) sudo restart nmbd 7.3) sudo restart winbind 8) cp /etc/apt/sources.list.back /etc/apt/sources.list 9) sudo apt-get update 7) sudo apt-get install samba winbind libnss-winbind libpam-winbind While installing, you will see things similar to this : > Unpacking libnss-winbind:amd64 (2:4.3.11+dfsg-0ubuntu0.14.04.1) over (2:4.1.6+dfsg-1ubuntu2) ... > dpkg-deb: error: subprocess tar was killed by signal (Segmentation fault), core dumped > dpkg: error processing archive /var/cache/apt/archives/libpam-winbind_2%3a4.3.11+dfsg-0ubuntu0.14.04.1_amd64.deb (- > -unpack): > subprocess dpkg-deb --control returned error exit status 2 > dpkg-deb: error: subprocess tar was killed by signal (Segmentation fault), core dumped [Regression Potential] * "preinst" and "postrm" maintainer scripts are acting only in "upgrade" * uninstalling packages and reinstalling would bypass this change [Other Info] * Original Bug Description: It was brought to my attention that, because of latest security fixes for samba: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1577739 samba (2:4.3.9+dfsg-0ubuntu0.14.04.1) trusty-security; urgency=medium samba (2:4.3.8+dfsg-0ubuntu0.14.04.2) trusty-security; urgency=medium samba (2:4.1.6+dfsg-1ubuntu2.14.04.13) trusty-security; urgency=medium when library symbols changed, a samba upgrade MAY jeopardize an entire Ubuntu OS installation IF /etc/nsswitch.conf uses winbind as a service (specially if used before compat mechanism). How to reproduce easily: $ cat /etc/nsswitch.conf passwd: winbind compat shadow: compat group: winbind compat (winbind is usually used after compat, in this case it was used before) to have samba version "4.1.6+dfsg-1ubuntu2.14.04.13" installed and do a: $ sudo apt-get update and FINALLY: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/1 Leading into an unusable system in the following state: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/comments/2 ## state Workaround: DO REMOVE winbind from /etc/nsswitch.conf (and possibly from pam.d with "pam-auth-update") before ANY attempt of upgrading samba to latest version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1584485/+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 1704004] Re: linux-joule: -proposed tracker
** Changed in: kernel-sru-workflow Status: In Progress => Invalid ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package Status: New => Invalid ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Invalid ** Changed in: kernel-sru-workflow/regression-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Changed in: kernel-sru-workflow/upload-to-ppa Status: New => Invalid ** Changed in: kernel-sru-workflow/verification-testing Status: New => Invalid ** Changed in: linux-joule (Ubuntu Xenial) Status: Confirmed => 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/1704004 Title: linux-joule: -proposed tracker Status in Kernel SRU Workflow: Invalid 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: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Invalid Status in linux-joule package in Ubuntu: Invalid Status in linux-joule source package in Xenial: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1703995 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1704004/+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 1698264] Re: Processes in "D" state due to zap_pid_ns_processes kernel call with Ubuntu + Docker
Marked Xenial series as 'Fix Released' since the fix, commit
b9a985db98961ae1ba0be169f19df1c567e4ffe0 upstream (pid_ns: Sleep in
TASK_INTERRUPTIBLE in zap_pid_ns_processes), has been included as part
of update to 4.4.70 stable release (bug #1694621).
** Changed in: linux (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/1698264
Title:
Processes in "D" state due to zap_pid_ns_processes kernel call with
Ubuntu + Docker
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Committed
Status in linux source package in Zesty:
Fix Committed
Bug description:
SRU Justification
Impact: In some cases some docker processes can be stuck in the D
state after a container has terminated. They will remain in this state
until reboot.
Fix: Cherry pick upstream commit
b9a985db98961ae1ba0be169f19df1c567e4ffe0, which has already been
included as a stable commit in maintained upstream stable kernels.
Test case: See below.
Regression potential: Low, this is a simple change and as stated above
the patch has already been shipped out in upstream stable kernels.
---
(please refer to
https://github.com/moby/moby/issues/31007#issuecomment-308877825 for
context)
Precondition: Ubuntu 16.04.2 with Docker 17.03 (kernel 4.4)
Steps to reproduce:
- Install latest Docker
- Run 300 containers with health check (for i in {1..300}; do docker run -d
-it --restart=always --name poc_$i talves/health_poc; done)
- Send termination signal to the containers (docker kill -s TERM $(docker ps
-q)
- A few processes are going to be stuck in "uninterruptible sleep" ("D"
state). The only know way to recover from this is host reboot
Expected behavior:
- All containers should be terminated without any dangling process
Actual behavior:
- Some processes are left in "D" state. In our production environment this
leads over time to performance degradation and maintenance issues due to
containers that cannot be stopped / removed.
A fix is provided on kernel 4.12 - it would be nice if it could be
backported and included in the next Ubuntu release within the
supported kernel.
Thanks in advance
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 29 16:54 seq
crw-rw 1 root audio 116, 33 May 29 16:54 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.6
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: Cannot stat file /proc/11652/fd/4: Stale file handle
Cannot stat file /proc/11652/fd/5: Stale file handle
Cannot stat file /proc/11652/fd/6: Stale file handle
Cannot stat file /proc/11652/fd/7: Stale file handle
Cannot stat file /proc/11652/fd/11: Stale file handle
DistroRelease: Ubuntu 16.04
Ec2AMI: ami-45b69e52
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: t2.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Xen HVM domU
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic
root=UUID=9b05a884-ac72-4bd2-8660-3bfa5cb22246 ro net.ifnames=0 biosdevname=0
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
RelatedPackageVersions:
linux-restricted-modules-4.4.0-78-generic N/A
linux-backports-modules-4.4.0-78-generic N/A
linux-firmware1.157.10
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial ec2-images
Uname: Linux 4.4.0-78-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/16/2017
dmi.bios.vendor: Xen
dmi.bios.version: 4.2.amazon
dmi.chassis.type: 1
dmi.chassis.vendor: Xen
dmi.modalias:
dmi:bvnXen:bvr4.2.amazon:bd02/16/2017:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
dmi.product.name: HVM domU
dmi.product.version: 4.2.amazon
dmi.sys.vendor: Xen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698264/+subscriptions
___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad
[Group.of.nepali.translators] [Bug 1701026] Re: linux-raspi2: 4.4.0-1062.70 -proposed tracker
*** This bug is a duplicate of bug 1703998 *** https://bugs.launchpad.net/bugs/1703998 ** This bug is no longer a duplicate of bug 1702106 linux-raspi2: 4.4.0-1062.70 -proposed tracker ** This bug has been marked a duplicate of bug 1703998 linux-raspi2: 4.4.0-1063.71 -proposed tracker -- 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/1701026 Title: linux-raspi2: 4.4.0-1062.70 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1701024 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701026/+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 1702106] Re: linux-raspi2: 4.4.0-1062.70 -proposed tracker
*** This bug is a duplicate of bug 1703998 *** https://bugs.launchpad.net/bugs/1703998 Sorry, version for this tracking should not have been changing. Was my fault of running some tools without properly duplicating tbs. ** Summary changed: - linux-raspi2: 4.4.0-1063.71 -proposed tracker + linux-raspi2: 4.4.0-1062.70 -proposed tracker ** This bug has been marked a duplicate of bug 1703998 linux-raspi2: 4.4.0-1063.71 -proposed tracker -- 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/1702106 Title: linux-raspi2: 4.4.0-1062.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: In Progress 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1702103 phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702106/+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 1703742] Re: Transparent hugepages should default to enabled=madvise
** Also affects: linux (Ubuntu Artful) Importance: High Assignee: Colin Ian King (colin-king) Status: In Progress ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1703742 Title: Transparent hugepages should default to enabled=madvise Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: New Status in linux source package in Yakkety: New Status in linux source package in Zesty: New Status in linux source package in Artful: Fix Committed Bug description: Ubuntu kernels should default transparent_hugepages to enabled=madvise, not enabled=always (this corresponds to TRANSPARENT_HUGEPAGE_MADVISE=y in .config). I've blogged about this at some length here: https://blog.nelhage.com/post/transparent-hugepages/ but here is a summary: Transparent Hugepages are a feature that allows the kernel to attempt to automatically back any anonymous maps with "huge" 2MiB page tables, instead of the normal 4k entries. It can produce small net performance gains in certain benchmarks, but also has numerous downsides, in the form of apparent memory leaks and 30% slowdowns or worse for some applications. Many popular pieces of software now refuse to run with hugepages enabled because of known performance issues. Examples of problem reports: MongoDB: https://docs.mongodb.com/manual/tutorial/transparent-huge-pages/ Oracle: https://blogs.oracle.com/linux/entry/performance_issues_with_transparent_huge Splunk: https://docs.splunk.com/Documentation/Splunk/6.5.2/ReleaseNotes/SplunkandTHP Go runtime: https://github.com/golang/go/issues/8832 jemalloc: https://blog.digitalocean.com/transparent-huge-pages-and-alternative-memory-allocators/ node.js: https://github.com/nodejs/node/issues/11077 Setting `enabled=madvise` enables applications that know they benefit from transparent huge pages to opt-in to this feature, while eliminating all the problematic behavior for other applications. Note also that transparent hugepage settings don't affect the use of explicit hugepages via hugetlbfs or mmap(…, MAP_HUGETLB, …) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703742/+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 1099947] Re: driver unable to connect to CyberPower UPS using usbhid-ups driver
I don't even know how much pardon to beg on this one ... a lot for sure.
I'm coming by trying to clear bugs that are dormant for too long - and this one
is really way too long :-/
Anyway forget the past and work on it ...
Now this is fixed in Zesty and later due to merging 2.7.4.
Updating tasks and consider backporting
https://github.com/networkupstools/nut/commit/040c800efad46ead9670077c9764360802d7aaf5
** Also affects: nut (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: nut (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: nut (Ubuntu Trusty)
Status: New => Triaged
** Changed in: nut (Ubuntu Xenial)
Status: New => Triaged
** Changed in: nut (Ubuntu)
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/1099947
Title:
driver unable to connect to CyberPower UPS using usbhid-ups driver
Status in nut package in Ubuntu:
Fix Released
Status in nut source package in Trusty:
Triaged
Status in nut source package in Xenial:
Triaged
Status in nut package in Debian:
New
Status in nut package in Fedora:
Unknown
Bug description:
I hooked my new CyberPower UPS: CP685AVR-G on my Lucid server and got
this error:
Jan 15 12:06:33 xeon upsd[5441]: Can't connect to UPS [cyberpower]
(usbhid-ups-cyberpower): No such file or directory
Jan 15 12:06:38 xeon upsmon[5445]: Poll UPS [cyberpower@127.0.0.1] failed -
Driver not connected
After trying many things, I found
https://bugzilla.redhat.com/show_bug.cgi?id=488368 that hint me in the
right direction. The required change was to rename the udev rule like
this:
mv /lib/udev/rules.d/{5,6}2-nut-usbups.rules
Now, everything works well, without requiring "user = root" in
/etc/nut/ups.conf because the udev rule now ensures the device file is
owned by the group "nut":
# find /dev/bus/usb/ -ls
15360 drwxr-xr-x 10 root root 200 Jan 15 12:40
/dev/bus/usb/
15790 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/008
15800 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/008/001
15730 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/007
15740 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/007/001
15670 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/006
15680 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/006/001
15610 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/005
15620 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/005/001
15550 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/004
15560 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/004/001
15490 drwxr-xr-x 2 root root 80 Jan 15 12:40
/dev/bus/usb/003
21630 crw-rw-r-- 1 root nut Jan 15 12:49
/dev/bus/usb/003/002
15500 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/003/001
15430 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/002
15440 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/002/001
15370 drwxr-xr-x 2 root root 60 Jan 15 12:40
/dev/bus/usb/001
15380 crw-rw-r-- 1 root root Jan 15 12:41
/dev/bus/usb/001/001
Generic information:
# lsb_release -rd
Description: Ubuntu 10.04.4 LTS
Release: 10.04
# apt-cache policy nut
nut:
Installed: 2.4.3-1ubuntu3.2
Candidate: 2.4.3-1ubuntu3.2
Version table:
*** 2.4.3-1ubuntu3.2 0
500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
500 http://archive.ubuntu.com/ubuntu/ lucid-security/main Packages
100 /var/lib/dpkg/status
2.4.3-1ubuntu3 0
500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: nut 2.4.3-1ubuntu3.2
ProcVersionSignature: Ubuntu 2.6.32-45.102-server 2.6.32.60+drm33.26
Uname: Linux 2.6.32-45-server x86_64
Architecture: amd64
Date: Tue Jan 15 12:43:46 2013
ProcEnviron:
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
SourcePackage: nut
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1099947/+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 1701306] Re: linux-hwe: 4.10.0-27.30~16.04.2 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/xenial/4.10.0-27.30~16.04.2/xenial-4.10-proposed-published.html ** Tags added: certification-testing-passed ** 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/1701306 Title: linux-hwe: 4.10.0-27.30~16.04.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1701306/+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 1702107] Re: linux-snapdragon: 4.4.0-1064.69 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/snapdragon/4.4.0-1064.69/snapdragon-4.4-proposed-published.html ** Tags added: certification-testing-passed ** 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/1702107 Title: linux-snapdragon: 4.4.0-1064.69 -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 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1702103 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702107/+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 1702106] Re: linux-raspi2: 4.4.0-1063.71 -proposed tracker
** Summary changed: - linux-raspi2: 4.4.0-1062.70 -proposed tracker + linux-raspi2: 4.4.0-1063.71 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Released => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Thadeu Lima de Souza Cascardo (cascardo) => Stefan Bader (smb) -- 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/1702106 Title: linux-raspi2: 4.4.0-1063.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: In Progress 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: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1702103 phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1702106/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug was fixed in the package hw-detect - 1.117ubuntu2.2 --- hw-detect (1.117ubuntu2.2) xenial; urgency=medium * disk-detect.sh: unconditionally modprobe dm-service-time and dm-queue-length multipath path selector modules alongside dm-round-robin. (LP: #1673350) -- Mathieu Trudel-Lapierre Wed, 14 Jun 2017 16:15:14 -0400 ** Changed in: hw-detect (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/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in multipath-tools source package in Xenial: Fix Released Status in hw-detect source package in Yakkety: Fix Committed Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Status in multipath-tools source package in Yakkety: Fix Released Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO
This bug was fixed in the package libepoxy - 1.3.1-1ubuntu0.16.04.2 --- libepoxy (1.3.1-1ubuntu0.16.04.2) xenial; urgency=medium * Disable patch 8d58c890646fc1f43bcab702bb9ed6bae94daefe: - this patch is causing some troubles on proprietary drivers. LP: #1698233 -- Gianfranco Costamagna Sat, 24 Jun 2017 00:02:18 +0200 ** Changed in: libepoxy (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/1698233 Title: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO Status in libepoxy package in Ubuntu: Fix Released Status in libepoxy source package in Xenial: Fix Released Status in libepoxy source package in Zesty: Fix Released Bug description: [Impact] * Updating libepoxy with the updates pocket (xenial) and the -proposed pocket (zesty) breaks systems with AMDGPU-PRO proprietary drivers [Test Case] * Have that driver/card [Regression Potential] * None, I'm disabling a patch that I introduced in the last SRU. * Debian opened an RC bug and will fix the same in the next point release, and I'm discussing with upstream to revert that patch (they should have already reverted it) * I just updated it to artful and Debian will follow in a few hours I guess [Other info] When updating my Xubuntu 16.04.2 system today the upgrade from libepoxy0 1.3.1-1 to libepoxy0 1.3.1-1ubuntu0.16.04.1 caused my system to hang right before the login screen. Unfortunately since this was a complete system lock up I can't provide any logs as I had to restore the entire root partition from backup. Since I can't get system recovery mode to work (it's been broken for a few years and times out within two minutes) it doesn't give me enough time gather any logs before it exits. I understand the system recovery problem is known, but I've tried all the solutions I could over the years, on multiple systems, and just can't get it to work without timing out anymore. In any case I verified the problem was libepoxy0 by applying all the available updates except libexpoxy0 and rebooting without any problems. I then allowed the upgrade of libepoxy0, libepoxy0:i386, and libeepoxy-dev and the system hung at boot as previously described. I went through the same procedure twice to confirm. I'm running kernel 4.9.31-040931-lowlatency with AMDGPU-PRO 16.50 patched drivers, with all system updates. If you need more information please contact me and I'll get you anything I can. But as I said, since the system locks up I'm not sure what else I can garner. lsb_release -rd: Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy libepoxy0: libepoxy0: Installed: 1.3.1-1 Candidate: 1.3.1-1ubuntu0.16.04.1 Version table: 1.3.1-1ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.3.1-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1698233/+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 1698233] Re: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO
This bug was fixed in the package libepoxy - 1.3.1-1ubuntu1.17.04.2 --- libepoxy (1.3.1-1ubuntu1.17.04.2) zesty; urgency=medium * Disable patch 8d58c890646fc1f43bcab702bb9ed6bae94daefe: - this patch is causing some troubles on proprietary drivers. LP: #1698233 -- Gianfranco Costamagna Sat, 24 Jun 2017 00:00:55 +0200 ** Changed in: libepoxy (Ubuntu Zesty) 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/1698233 Title: [SRU] New libepoxy0 causes hang at boot for AMDGPU-PRO Status in libepoxy package in Ubuntu: Fix Released Status in libepoxy source package in Xenial: Fix Released Status in libepoxy source package in Zesty: Fix Released Bug description: [Impact] * Updating libepoxy with the updates pocket (xenial) and the -proposed pocket (zesty) breaks systems with AMDGPU-PRO proprietary drivers [Test Case] * Have that driver/card [Regression Potential] * None, I'm disabling a patch that I introduced in the last SRU. * Debian opened an RC bug and will fix the same in the next point release, and I'm discussing with upstream to revert that patch (they should have already reverted it) * I just updated it to artful and Debian will follow in a few hours I guess [Other info] When updating my Xubuntu 16.04.2 system today the upgrade from libepoxy0 1.3.1-1 to libepoxy0 1.3.1-1ubuntu0.16.04.1 caused my system to hang right before the login screen. Unfortunately since this was a complete system lock up I can't provide any logs as I had to restore the entire root partition from backup. Since I can't get system recovery mode to work (it's been broken for a few years and times out within two minutes) it doesn't give me enough time gather any logs before it exits. I understand the system recovery problem is known, but I've tried all the solutions I could over the years, on multiple systems, and just can't get it to work without timing out anymore. In any case I verified the problem was libepoxy0 by applying all the available updates except libexpoxy0 and rebooting without any problems. I then allowed the upgrade of libepoxy0, libepoxy0:i386, and libeepoxy-dev and the system hung at boot as previously described. I went through the same procedure twice to confirm. I'm running kernel 4.9.31-040931-lowlatency with AMDGPU-PRO 16.50 patched drivers, with all system updates. If you need more information please contact me and I'll get you anything I can. But as I said, since the system locks up I'm not sure what else I can garner. lsb_release -rd: Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy libepoxy0: libepoxy0: Installed: 1.3.1-1 Candidate: 1.3.1-1ubuntu0.16.04.1 Version table: 1.3.1-1ubuntu0.16.04.1 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 1.3.1-1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libepoxy/+bug/1698233/+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 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug was fixed in the package multipath-tools - 0.5.0+git1.656f8865-5ubuntu2.5 --- multipath-tools (0.5.0+git1.656f8865-5ubuntu2.5) xenial; urgency=medium * debian/initramfs/hooks: drop dm-emc (it hasn't existed since 2.6.27) and add dm-queue-length: it's required on some hardware, such as XtremIO, where it is the default path selector. (LP: #1673350) -- Mathieu Trudel-Lapierre Tue, 28 Mar 2017 09:58:21 -0400 ** Changed in: multipath-tools (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/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in multipath-tools source package in Xenial: Fix Released Status in hw-detect source package in Yakkety: Fix Committed Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Status in multipath-tools source package in Yakkety: Fix Released Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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
