[Group.of.nepali.translators] [Bug 1595775] [NEW] linux-snapdragon: -proposed tracker
Public bug reported: 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: 1595772 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-snapdragon (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-xenial ** Also affects: linux-snapdragon (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates
[Group.of.nepali.translators] [Bug 1595774] [NEW] linux-raspi2: -proposed tracker
Public bug reported: 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: 1595772 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/upload-to-ppa Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-raspi2 (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-xenial ** Also affects: linux-raspi2 (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/upload-to-ppa Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Ubuntu Stable Release Updates Team (ubunt
[Group.of.nepali.translators] [Bug 1595507] Re: World readable X11 Cookie key logger
This bug was fixed in the package kinit - 5.22.0-0ubuntu2 --- kinit (5.22.0-0ubuntu2) yakkety; urgency=medium * Security update CVE-2016-3100 (LP: #1595507) - add upstream_permissions-of-tmp-xauth-xxx-_y.diff - add upstream_Fix-race-in-which-the-file-containing-the-X11-cookie.diff -- Philip Muškovac Thu, 23 Jun 2016 20:03:00 +0200 ** Changed in: kinit (Ubuntu) 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/1595507 Title: World readable X11 Cookie key logger Status in kinit package in Ubuntu: Fix Released Status in kinit source package in Xenial: In Progress Bug description: KDE Project Security Advisory = Title: kinit: World readable X11 Cookie key logger Risk Rating:Important CVE:CVE-2016-3100 Platforms: X11 Versions: kinit < 5.23 Author: Siddharth Sharma siddharth@gmail.com Date: 21 June 2016 Overview An authorized user can log key events of other user by accessing world-readable X11 cookie Impact == Pre-authenticated attacker can read all key events by the users logged on to the system. Workaround == None Solution For kinit apply the following patches: https://quickgit.kde.org/?p=kinit.git&a=commitdiff&h=dece8fd89979cd1a86c03bcaceef6e9221e8d8cd https://quickgit.kde.org/?p=kinit.git&a=commitdiff&h=72f3702dbe6cf15c06dc13da2c99c864e9022a58 References == https://bugs.kde.org/show_bug.cgi?id=358593 https://bugs.kde.org/show_bug.cgi?id=363140 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kinit 5.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jun 23 14:06:42 2016 InstallationDate: Installed on 2016-02-11 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: kinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1595507/+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 1595772] [NEW] linux: 4.4.0-28.47 -proposed tracker
Public bug reported: This bug is for tracking the 4.4.0-28.47 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 ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Status: New ** Tags: block-proposed block-proposed-xenial kernel-release-tracking-bug xenial ** Tags added: kernel-release-tracking-bug ** Tags added: block-proposed ** Tags added: block-proposed-xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags added: xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/p
[Group.of.nepali.translators] [Bug 1570968] Re: Call to undefined function eregi()
** Also affects: phamm (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1570968 Title: Call to undefined function eregi() Status in phamm package in Ubuntu: Triaged Status in phamm source package in Xenial: New Bug description: PHP message: PHP Fatal error: Uncaught Error: Call to undefined function eregi() in /usr/share/phamm/controllers/helpers.php:285 Stack trace: #0 /usr/share/phamm/public/main.php(251): check_syntax('domain', 'asdasd') #1 {main} thrown in /usr/share/phamm/controllers/helpers.php on line 285 PHP Version: 7 although prerequisites are PHP5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phamm/+bug/1570968/+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 1595749] Re: Correct Apache syntax for PHP7.0
** Also affects: fusionforge (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: fusionforge (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1595749 Title: Correct Apache syntax for PHP7.0 Status in fusionforge package in Ubuntu: Fix Released Status in fusionforge source package in Xenial: In Progress Bug description: fusionforge (6.0.3+20151023-1ubuntu1.1) xenial; urgency=medium * debian/patches/update-for-php7.patch: correct a2enmod syntax for PHP7.0 (LP: #). -- Nishanth Aravamudan Thu, 23 Jun 2016 16:15:37 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fusionforge/+bug/1595749/+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 1595274] Re: nvme cli utility clips Leaf model # to 20 characters
This bug was fixed in the package nvme-cli - 0.7-1ubuntu1 --- nvme-cli (0.7-1ubuntu1) yakkety; urgency=low * Merge from Debian unstable. - Includes upstream fix for truncated Leaf model number (LP: #1595274). * Remaining changes: - fix segfault when using show-regs command with no device name - fix null pointer deference segfault on strcmp() on a null string nvme-cli (0.7-1) unstable; urgency=medium * New upstream release * Bump Standard-Version to 3.9.8, no changes required. -- Steve Langasek Thu, 23 Jun 2016 12:45:21 -0700 ** Changed in: nvme-cli (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1595274 Title: nvme cli utility clips Leaf model # to 20 characters Status in nvme-cli package in Ubuntu: Fix Released Status in nvme-cli source package in Xenial: Triaged Bug description: nvme cli only shows the first 20 characters of the Leaf model number (mn) i.e "PCIe3 3.2TB NVMe Fla" root@gdx1x152:~# nvme id-ctrl /dev/nvme0 | more NVME Identify Controller: vid : 0x1c58 ssvid : 0x1014 sn : CJH001001830 mn : PCIe3 3.2TB NVMe Fla fr : KMIPP107 When I check data from lspci it shows correct name Product Name: PCIe3 3.2TB NVMe Flash Adapter checking block device data also shows correct model name # cat /sys/block/nvme0n1/device/model PCIe3 3.2TB NVMe Flash Adapter # == Comment: #5 - Guilherme Guaglianoni Piccoli - 2016-06-21 16:07:02 == Not too much commits between v0.5 and v0.7. The following 2 commits are the fix to this issue: ab43012 ("Fix the bug of Model Number and display the info of Serial Number") a304435 ("Fix the bug of Model Number and display the info of Serial Number") Probably the 1st was merged too early, instead of waiting v2..so it's easier to backport both, in order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1595274/+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 1495580] Re: chfn needs to learn about the --extrausers argument and use libnss-extrausers files when set
This bug was fixed in the package shadow - 1:4.2-3.1ubuntu6 --- shadow (1:4.2-3.1ubuntu6) yakkety; urgency=medium * add support for "chfn --extrausers" (LP: #1495580) -- Michael Vogt Thu, 23 Jun 2016 08:02:00 +0200 ** Changed in: shadow (Ubuntu) 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/1495580 Title: chfn needs to learn about the --extrausers argument and use libnss- extrausers files when set Status in Snappy: Fix Released Status in shadow package in Ubuntu: Fix Released Status in shadow source package in Xenial: Confirmed Bug description: as seen in bug 1492327, adduser now works for creating users in the extrausers db but when it tries to update the GECOS field at the end of adding a user (interactively and noninteractively) chfn falls over ... chfn needs similar patches to the other shadow binaries that recently got extrausers support. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1495580/+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 1595274] Re: nvme cli utility clips Leaf model # to 20 characters
** Also affects: nvme-cli (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nvme-cli (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: nvme-cli (Ubuntu Xenial) Status: New => 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/1595274 Title: nvme cli utility clips Leaf model # to 20 characters Status in nvme-cli package in Ubuntu: New Status in nvme-cli source package in Xenial: Triaged Bug description: nvme cli only shows the first 20 characters of the Leaf model number (mn) i.e "PCIe3 3.2TB NVMe Fla" root@gdx1x152:~# nvme id-ctrl /dev/nvme0 | more NVME Identify Controller: vid : 0x1c58 ssvid : 0x1014 sn : CJH001001830 mn : PCIe3 3.2TB NVMe Fla fr : KMIPP107 When I check data from lspci it shows correct name Product Name: PCIe3 3.2TB NVMe Flash Adapter checking block device data also shows correct model name # cat /sys/block/nvme0n1/device/model PCIe3 3.2TB NVMe Flash Adapter # == Comment: #5 - Guilherme Guaglianoni Piccoli - 2016-06-21 16:07:02 == Not too much commits between v0.5 and v0.7. The following 2 commits are the fix to this issue: ab43012 ("Fix the bug of Model Number and display the info of Serial Number") a304435 ("Fix the bug of Model Number and display the info of Serial Number") Probably the 1st was merged too early, instead of waiting v2..so it's easier to backport both, in order. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1595274/+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 1588066] Re: SRU: backport gdb 7.11.1 patches to 16.04 LTS (from 7.11)
This bug was fixed in the package gdb - 7.11.1-0ubuntu1~16.04 --- gdb (7.11.1-0ubuntu1~16.04) xenial-updates; urgency=medium * SRU: LP: #1588066, backport 7.11.1 to 16.04 LTS. gdb (7.11.1-0ubuntu1) yakkety; urgency=medium * New upstream bug fix release. - Fix PR gdb/19828, PR gdb/20045, PR gdb/18077, PR gdb/20039, PR python/20037, PR remote/19840, PR gdb/19858, PR gdb/19829, PR gdb/19676. -- Matthias Klose Thu, 02 Jun 2016 00:09:52 +0200 ** Changed in: gdb (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/1588066 Title: SRU: backport gdb 7.11.1 patches to 16.04 LTS (from 7.11) Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Xenial: Fix Released Bug description: SRU: backport gdb 7.11.1 patches to 16.04 LTS (from 7.11). The upstream bugfix release contains a handful of patches fixing only bugs, which are: - Fix PR gdb/19828, PR gdb/20045, PR gdb/18077, PR gdb/20039, PR python/20037, PR remote/19840, PR gdb/19858, PR gdb/19829, PR gdb/19676. Also mentioned in the attached debdiff. Proposing to accept this update into xenial-proposed, and accept it if the newly added testcases pass and existing test cases don't show regressions (the testsuite is run during the build). The build in yakkety doesn't show any regressions, and the new test cases pass. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1588066/+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 1588066] Please test proposed package
Hello Matthias, or anyone else affected, Accepted gdb into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gdb/7.11.1-0ubuntu1~16.04 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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! ** Also affects: gdb (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gdb (Ubuntu Xenial) Status: New => Fix Committed ** Changed in: gdb (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1588066 Title: SRU: backport gdb 7.11.1 patches to 16.04 LTS (from 7.11) Status in gdb package in Ubuntu: Fix Released Status in gdb source package in Xenial: Fix Released Bug description: SRU: backport gdb 7.11.1 patches to 16.04 LTS (from 7.11). The upstream bugfix release contains a handful of patches fixing only bugs, which are: - Fix PR gdb/19828, PR gdb/20045, PR gdb/18077, PR gdb/20039, PR python/20037, PR remote/19840, PR gdb/19858, PR gdb/19829, PR gdb/19676. Also mentioned in the attached debdiff. Proposing to accept this update into xenial-proposed, and accept it if the newly added testcases pass and existing test cases don't show regressions (the testsuite is run during the build). The build in yakkety doesn't show any regressions, and the new test cases pass. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1588066/+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 1562042] Re: Traceback in error log during heat-engine service shutdown
This bug was fixed in the package heat - 1:6.0.0-0ubuntu1.1~cloud0 --- heat (1:6.0.0-0ubuntu1.1~cloud0) trusty-mitaka; urgency=medium . * New update for the Ubuntu Cloud Archive. . heat (1:6.0.0-0ubuntu1.1) xenial; urgency=medium . * d/p/engine-shutdown.patch: Cherry pick fix to ensure that heat-engine worker processes are shutdown correctly when SIGINT is received early in the process lifecycle (LP: #1562042). ** Changed in: cloud-archive/mitaka 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/1562042 Title: Traceback in error log during heat-engine service shutdown Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in heat: Fix Released Status in heat package in Ubuntu: Fix Released Status in heat source package in Wily: Fix Released Status in heat source package in Xenial: Fix Released Status in heat source package in Yakkety: Fix Released Bug description: During shutdown of heat-engine service this traceback could be observed in log: ``` 2016-03-25 17:29:22.259 22588 DEBUG oslo_service.service [-] Stop services. stop /usr/lib/python2.7/dist-packages/oslo_service/service.py:583 2016-03-25 17:29:22.261 22588 DEBUG heat.engine.service [-] Attempting to stop engine service... _stop_rpc_server /usr/lib/python2.7/dist-packages/heat/engine/service.py:410 2016-03-25 17:29:22.262 22588 ERROR heat.engine.service [-] Failed to stop engine service, 'NoneType' object has no attribute 'stop' 2016-03-25 17:29:22.264 22588 CRITICAL heat-engine [-] AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine Traceback (most recent call last): 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/bin/heat-engine", line 10, in 2016-03-25 17:29:22.264 22588 ERROR heat-engine sys.exit(main()) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/cmd/engine.py", line 79, in main 2016-03-25 17:29:22.264 22588 ERROR heat-engine launcher.wait() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 577, in wait 2016-03-25 17:29:22.264 22588 ERROR heat-engine self.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 586, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine service.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 117, in wrapper 2016-03-25 17:29:22.264 22588 ERROR heat-engine return f(*args, **kwargs) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 426, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine for stack_id in list(self.thread_group_mgr.groups.keys()): 2016-03-25 17:29:22.264 22588 ERROR heat-engine AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine 2016-03-25 17:29:22.388 22599 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting ``` Full log could be found here: http://pastebin.com/raw/mgRbgvjd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1562042/+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 1562042] Re: Traceback in error log during heat-engine service shutdown
This bug was fixed in the package heat - 1:5.0.1-0ubuntu3.1~cloud0 --- heat (1:5.0.1-0ubuntu3.1~cloud0) trusty-liberty; urgency=medium . * New update for the Ubuntu Cloud Archive. . heat (1:5.0.1-0ubuntu3.1) wily; urgency=medium . * d/p/engine-shutdown.patch: Cherry pick fix to ensure that heat-engine worker processes are shutdown correctly when SIGINT is received early in the process lifecycle (LP: #1562042). ** Changed in: cloud-archive/liberty 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/1562042 Title: Traceback in error log during heat-engine service shutdown Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: Fix Released Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in heat: Fix Released Status in heat package in Ubuntu: Fix Released Status in heat source package in Wily: Fix Released Status in heat source package in Xenial: Fix Released Status in heat source package in Yakkety: Fix Released Bug description: During shutdown of heat-engine service this traceback could be observed in log: ``` 2016-03-25 17:29:22.259 22588 DEBUG oslo_service.service [-] Stop services. stop /usr/lib/python2.7/dist-packages/oslo_service/service.py:583 2016-03-25 17:29:22.261 22588 DEBUG heat.engine.service [-] Attempting to stop engine service... _stop_rpc_server /usr/lib/python2.7/dist-packages/heat/engine/service.py:410 2016-03-25 17:29:22.262 22588 ERROR heat.engine.service [-] Failed to stop engine service, 'NoneType' object has no attribute 'stop' 2016-03-25 17:29:22.264 22588 CRITICAL heat-engine [-] AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine Traceback (most recent call last): 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/bin/heat-engine", line 10, in 2016-03-25 17:29:22.264 22588 ERROR heat-engine sys.exit(main()) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/cmd/engine.py", line 79, in main 2016-03-25 17:29:22.264 22588 ERROR heat-engine launcher.wait() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 577, in wait 2016-03-25 17:29:22.264 22588 ERROR heat-engine self.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 586, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine service.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 117, in wrapper 2016-03-25 17:29:22.264 22588 ERROR heat-engine return f(*args, **kwargs) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 426, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine for stack_id in list(self.thread_group_mgr.groups.keys()): 2016-03-25 17:29:22.264 22588 ERROR heat-engine AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine 2016-03-25 17:29:22.388 22599 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting ``` Full log could be found here: http://pastebin.com/raw/mgRbgvjd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1562042/+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 1594249] Re: [SRU] Update of dashboard fails on Xenial
** Package changed: openstack-dashboard (Ubuntu) => horizon (Ubuntu) ** Changed in: horizon (Ubuntu Xenial) Status: Triaged => 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/1594249 Title: [SRU] Update of dashboard fails on Xenial Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Triaged Status in horizon package in Ubuntu: Invalid Status in horizon source package in Xenial: Fix Committed Bug description: [Impact] NOTE: this bug is limited to the proposed pockets of xenial and trusty-mitaka (UCA). I am currently trying to update the horizon dashboard on Ubuntu 16.04 running OpenStack Mitaka using the new versions coming in from the package repository. aptitude update && aptitude safe-upgrade Get: 1 http://archive.ubuntu.com/ubuntu xenial-proposed InRelease [247 kB] Hit http://mirror2.hs-esslingen.de/mariadb/repo/10.1/ubuntu xenial InRelease Hit http://de.archive.ubuntu.com/ubuntu xenial InRelease Hit http://ppa.launchpad.net/vbernat/haproxy-1.6/ubuntu xenial InRelease Get: 2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB] Get: 3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease [92.2 kB] Get: 4 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB] Hit http://download.ceph.com/debian-jewel xenial InRelease Hit http://www.rabbitmq.com/debian testing InRelease Get: 5 http://de.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [213 kB] Get: 6 http://de.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages [209 kB] Get: 7 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [96.7 kB] Get: 8 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe i386 Packages [93.9 kB] Fetched 1,141 kB in 1s (1,011 kB/s) W: http://download.ceph.com/debian-jewel/dists/xenial/InRelease: Signature by key 08B73419AC32B4E966C1A330E84AC2C0460F3994 uses weak dige st algorithm (SHA1) Resolving dependencies... The following packages will be upgraded: base-files linux-firmware lshw openstack-dashboard openstack-dashboard-ubuntu-theme python-django-horizon python-glanceclient python-oslo.concurrency 8 packages upgraded, 0 newly installed, 0 to remove and 7 not upgraded. Need to get 41.8 MB of archives. After unpacking 539 kB will be used. Do you want to continue? [Y/n/?] Y Get: 1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 base-files amd64 9.4ubuntu4.1 [68.4 kB] Get: 2 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 openstack-dashboard-ubuntu-theme all 2:9.0.1-0ubuntu1 [79.5 kB] Get: 3 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 python-glanceclient all 1:2.0.0-2ubuntu0.16.04.1 [92.1 kB] Get: 4 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 python-oslo.concurrency all 3.7.1-0ubuntu1 [24.5 kB] Get: 5 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 openstack-dashboard all 2:9.0.1-0ubuntu1 [2,442 kB] Get: 6 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 python-django-horizon all 2:9.0.1-0ubuntu1 [6,272 kB] Get: 7 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 lshw amd64 02.17-1.1ubuntu3.2 [215 kB] Get: 8 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 linux-firmware all 1.157.1 [32.6 MB] Fetched 41.8 MB in 0s (42.3 MB/s) (Reading database ... 140753 files and directories currently installed.) Preparing to unpack .../base-files_9.4ubuntu4.1_amd64.deb ... Unpacking base-files (9.4ubuntu4.1) over (9.4ubuntu4) ... Processing triggers for plymouth-theme-ubuntu-text (0.9.2-3ubuntu13.1) ... update-initramfs: deferring update (trigger activated) Processing triggers for install-info (6.1.0.dfsg.1-5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.4.0-25-generic W: mdadm: /etc/mdadm/mdadm.conf defines no arrays. Setting up base-files (9.4ubuntu4.1) ... Installing new version of config file /etc/update-motd.d/10-help-text ... (Reading database ... 140753 files and directories currently installed.) Preparing to unpack .../openstack-dashboard-ubuntu-theme_2%3a9.0.1-0ubuntu1_all.deb ... Unpacking openstack-dashboard-ubuntu-theme (2:9.0.1-0ubuntu1) over (2:9.0.0-0ubuntu2.16.04.1) ... Preparing to unpack .../python-glanceclient_1%3a2.0.0-2ubuntu0.16.04.1_all.deb ... Unpacking python-glanceclient (1:2.0.0-2ubuntu0.16.04.1) over (1:2.0.0-2) ... Preparing to unpack .../python-oslo.concurrency_3.7.1-0ubuntu1_all.deb ... Unpacking python-oslo.concurrency (3.7.1-0ubuntu1) over (3.7.0-2) ... Preparing to unpack .../openstack-dashboard_2%3a9.0.1-0ubuntu1_all.deb ... Unpacking openstack-dashboard (
[Group.of.nepali.translators] [Bug 1574113] Re: curtin/maas don't support multiple (derived) archives/repositories with custom keys
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1574113 Title: curtin/maas don't support multiple (derived) archives/repositories with custom keys Status in cloud-init: Fix Committed Status in curtin: Confirmed Status in MAAS: Triaged Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: In Progress Bug description: In a customer environment I have to deploy using offline resources (no internet connection at all), so I created apt mirror and MAAS images mirror. I configured MAAS to use the local mirrors and I'm able to commission the nodes but I'm not able to deploy the nodes because there is no way to add gpg key of the local repo in target before the 'late' stage'. Using curtin I'm able to add the key but too late, in fact according with http://bazaar.launchpad.net/~curtin- dev/curtin/trunk/view/head:/curtin/commands/install.py#L52 "late" stage is executed after "curthooks" this prevent to add the key. I checked also apt_config function in curthooks.py I did't see code that add the key for each mirror. It should be possible to add gpg public of the repository in maas. -- configs/config-000.cfg -- #cloud-config debconf_selections: maas: | cloud-init cloud-init/datasources multiselect MAAS cloud-init cloud-init/maas-metadata-url string http://100.107.231.164/MAAS/metadata/ cloud-init cloud-init/maas-metadata-credentials string oauth_token_key=8eZmzQWSSQzsUkaLnE&oauth_token_secret=LKmn8sHgzEXfvzSZePAa9jUXvTMRrFNP&oauth_consumer_key=htwDZJFtmv2YvQXhUW cloud-init cloud-init/local-cloud-config string apt_preserve_sources_list: true\nmanage_etc_hosts: false\nmanual_cache_clean: true\nreporting:\n maas: {consumer_key: htwDZJFtmv2YvQXhUW, endpoint: 'http://100.107.231.164/MAAS/metadata/status/node-61b6987c-07a7-11e6-9d23-5254003d2515',\n token_key: 8eZmzQWSSQzsUkaLnE, token_secret: LKmn8sHgzEXfvzSZePAa9jUXvTMRrFNP,\ntype: webhook}\nsystem_info:\n package_mirrors:\n - arches: [i386, amd64]\nfailsafe: {primary: 'http://archive.ubuntu.com/ubuntu', security: 'http://security.ubuntu.com/ubuntu'}\nsearch:\n primary: ['http://100.107.231.166/']\n security: ['http://100.107.231.166/']\n - arches: [default]\nfailsafe: {primary: 'http://ports.ubuntu.com/ubuntu-ports', security: 'http://ports.ubuntu.com/ubuntu-ports'}\nsearch:\n primary: ['http://ports.ubuntu.com/ubuntu-ports']\n security: ['http://ports.ubuntu.com/ubuntu-ports']\n late_commands: maas: [wget, '--no-proxy', 'http://100.107.231.164/MAAS/metadata/latest/by-id/node-61b6987c-07a7-11e6-9d23-5254003d2515/', '--post-data', 'op=netboot_off', '-O', '/dev/null'] apt_key: ["curtin", "in-target", "--", "sh", "-c", "/usr/bin/wget --no-proxy -qO - http://100.107.231.166/magellan.key | apt-key add -"] power_state: mode: reboot apt_mirrors: ubuntu_archive: http://100.107.231.166// ubuntu_security: http://100.107.231.166// - curtin end of log -- Leaving 'diversion of /etc/init/ureadahead.conf to /etc/init/ureadahead.conf.disabled by cloud-init' Setting up swapspace version 1, size = 8388604 KiB no label, UUID=e2fe91bc-91e9-4e43-b50f-209dfcf04089 Get:1 http://100.107.231.166 trusty InRelease [17.7 kB] Get:2 http://100.107.231.166 trusty-updates InRelease [17.7 kB] Get:3 http://100.107.231.166 trusty-security InRelease [17.7 kB] Ign http://100.107.231.166 trusty InRelease Get:4 http://100.107.231.166 trusty/main amd64 Packages [412 kB] Ign http://100.107.231.166 trusty-updates InRelease Ign http://100.107.231.166 trusty-security InRelease Get:5 http://100.107.231.166 trusty/restricted amd64 Packages [20 B] Get:6 http://100.107.231.166 trusty/universe amd64 Packages [20 B] Get:7 http://100.107.231.166 trusty/multiverse amd64 Packages [20 B] Get:8 http://100.107.231.166 trusty-updates/main amd64 Packages [33.0 kB] Get:9 http://100.107.231.166 trusty-updates/restricted amd64 Packages [20 B] Get:10 http://100.107.231.166 trusty-updates/universe amd64 Packages [20 B] Get:11 http://100.107.231.166 trusty-updates/multiverse amd64 Packages [20 B] Get:12 http://100.107.231.166 trusty-security/main amd64 Pack
[Group.of.nepali.translators] [Bug 1571761] Re: zfs-import-cache.service slows boot by 60 seconds
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Status: New => Fix Released ** Changed in: cloud-init (Ubuntu Xenial) Status: Fix Released => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1571761 Title: zfs-import-cache.service slows boot by 60 seconds Status in cloud-init package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in cloud-init source package in Xenial: In Progress Status in zfs-linux source package in Xenial: New Bug description: Fresh uvt-kvm guest, then $ sudo apt-get install zfsutils-linux $ sudo reboot The reboot will show on console waiting for tasks, then after ~ 60 seconds it continues boot. Logging in shows: $ sudo systemd-analyze critical-chain zfs-mount.service The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. zfs-mount.service +81ms └─zfs-import-cache.service @1min 786ms +272ms └─systemd-udev-settle.service @494ms +1min 275ms └─systemd-udev-trigger.service @415ms +55ms └─systemd-udevd-control.socket @260ms └─-.mount @124ms └─system.slice @129ms └─-.slice @124ms Seems possibly related / or some discussion at https://github.com/zfsonlinux/zfs/issues/2368 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: zfsutils-linux 0.6.5.6-0ubuntu8 ProcVersionSignature: User Name 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 18 16:42:35 2016 ProcEnviron: TERM=screen.xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1571761/+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 1575938] Re: Instance path in / if instance-id starts with '/'
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1575938 Title: Instance path in / if instance-id starts with '/' Status in cloud-init: In Progress Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: In Progress Bug description: A cloud using the Ec2 datasource has an instance-id metadata value in the form: /Compute-$TENANT/$CLOUDUSERNAME/$UUID The leading '/' causes /var/lib/cloud/instance to link to /Compute-$TENANT/$CLOUDUSERNAME/$UUID rather than /var/lib/cloud/instances/Compute-$TENANT/$CLOUDUSERNAME/$UUID To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1575938/+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 1582323] Re: Commissioning fails when competing cloud metadata resides on disk
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1582323 Title: Commissioning fails when competing cloud metadata resides on disk Status in cloud-init: Fix Committed Status in MAAS: Triaged Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: In Progress Bug description: A customer reused hardware that had previously deployed a RHEL Overcloud-controller which places metadata on the disk as a legitimate source, that cloud-init looks at by default. When the newly enlisted node appeared it had the name of "overcloud-controller-0" vs. maas- enlist, pulled from the disk metadata which had overridden MAAS' metadata. Commissioning continually failed on all of the nodes until the disk metadata was manually removed (KVM boot Ubuntu ISO, rm -f data or dd zeros to disk). To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1582323/+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 1577844] Re: Drop unnecessary blocking of all net udev rules
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1577844 Title: Drop unnecessary blocking of all net udev rules Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: In Progress Bug description: cloud-inits networking setup currently jumps through a lot of bad hoops to make sure that ifup@ does not run until after cloud-init- local.service. This includes blocking udev rules for an indefinite time, which is racy, a potential deadlock, and highly non-elegant. This is also not necessary: while ifupdown's net udev rule certainly can fire before cloud-init-local, it only asynchronously starts ifup@.service which will be deferred until after network-pre.target and thus after cloud-init-local.service. --- Original description, which turned out to be completely false and just us being misled: ifup@.service can (and often does) run for a particular interface before networking.service runs. This is brittle as during early boot ifup is prone to fail: / might still be read-only, /var might not yet exist or be writable, dhclient-enter-hooks.d/ or if-up.d/ hooks might silently fail, etc. It is also unnecessary as networking.service will bring up all "auto" and all present "allow-hotplug" interfaces anyway, and it runs at the right time. We should make either 80-ifupdown.rules or ifup@.service ignore events until networking.service is active, or wait until after it has run (slower, but avoids race conditions when hotplug events happen while networking.service is running). Thus we need to add After=networking.service to ifup@.service, so that this only does stuff after doing the "coldplug" configuration. This also affects cloud-init's setup of networking: this currently jumps through a lot of bad hoops to make sure that ifup@ does not run until after cloud-init-local.service. This includes blocking udev rules for an indefinite time, which is racy, a potential deadlock, and highly non-elegant. https://bugs.debian.org/752919 is related to this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1577844/+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 1579130] Re: need to support renaming of devices in container and on first boot
Hello, An SRU upload of cloud-init for 16.04 that contains a fix for this bug has been made under bug 1595302. Please track that bug if you are interested. ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Xenial) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu Xenial) Status: New => In Progress ** No longer affects: systemd (Ubuntu Xenial) ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Scott Moser (smoser) -- 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/1579130 Title: need to support renaming of devices in container and on first boot Status in cloud-init package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Triaged Status in cloud-init source package in Xenial: In Progress Bug description: We're interested in supporting network configuration of cloud instances including lxc containers via maas/cloud-init yaml format. For Containers, the end goal is to do: $ lxc init xenial x1 $ ncpath=/var/lib/cloud/seed/nocloud-net/network-config $ sudo tee /var/lib/lxd/containers/x1/rootfs/$ncpath < into 'eth0'). That is implemented by check of /sys/devices/virtual/net/eth0/name_assign_type . Value of 4 means renamed. c.) systemd.link will not attempt to rename a device that does not have a driver. To see that run: udevadm test-builtin net_setup_link /sys/class/net/eth0 http://paste.ubuntu.com/16261974/ d.) on first boot of a cloud instance, the systemd.link files in the initramfs are either pristine or from the previous instance. The devices will leave the initramfs either named incorrectly or named with standard persistent naming and will have already been renamed. To force these systemd.link files to run in spite of 'b' on kvm guests or bare metal, we have found that unbind and rebind of the device will clear the state and rename would occur. that can be done as shown in https://bugs.launchpad.net/ubuntu/+source/cloud- init/+bug/1577844/comments/3 but since there is no 'driver' we cannot unbind and rebind veth devices. To do this right, we need to support: 1.) renaming on first boot with initramfs and with 'stale' initramfs 2.) renaming in lxc containers 3.) user updating whatever files or mechanism is used post first boot. For example, if the user wrote a 25-my-rules.link after first boot, a reboot should prefer their provided names to whatever were originally there. 4.) if cloud-init networking is disabled, the renaming should not occur. Related Bugs: * bug 1594546: no need to write systemd.link files ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri May 6 15:42:52 2016 MachineType: LENOVO 33672B7 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=19ac97d5-6973-4193-9a09-2e6bbfa38262 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G8ET96WW (2.56 ) dmi.board.asset.tag: Not Available dmi.board.name: 33672B7 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG8ET96WW(2.56):bd12/18/2013:svnLENOVO:pn33672B7:pvrThinkPadX131e:rvnLENOVO:rn33672B7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 33672B7 dmi.product.version: ThinkPad X131e dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1579130/+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 1501838] Re: Tests: lazy load operation of attribute 'snapshot_metadata' cannot proceed
Hi Tobias, Thanks for the notification on this. It looks like a reasonable backport to the liberty cinder package for ubuntu. We'll work on getting it backported. For now, marking this as fix-released for Xenial+ since both patches landed in 8.0.0. ** Also affects: cinder (Ubuntu Wily) Importance: Undecided Status: New ** Also affects: cinder (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: cinder (Ubuntu Wily) Status: New => Triaged ** Changed in: cinder (Ubuntu Xenial) Status: New => Fix Released ** Changed in: cinder (Ubuntu) Status: Confirmed => Fix Released ** Changed in: cinder (Ubuntu) Importance: Undecided => High ** Changed in: cinder (Ubuntu Xenial) Importance: Undecided => High ** Changed in: cinder (Ubuntu) Importance: High => Undecided ** Changed in: cinder (Ubuntu Wily) Importance: Undecided => High ** Changed in: cinder (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1501838 Title: Tests: lazy load operation of attribute 'snapshot_metadata' cannot proceed Status in Cinder: Fix Released Status in cinder package in Ubuntu: Fix Released Status in cinder source package in Wily: Triaged Status in cinder source package in Xenial: Fix Released Bug description: Possible issue with the Snapshot object? master @ 7f498b0 Merge "Obtain target authentication from database same as LIO target" Running this tox env (subset of our full tests): [testenv:py34not] commands = ostestr {posargs} --concurrency=16 --regex (cinder.tests.unit.test_volume|cinder.tests.unit.image.test_cache) cinder.tests.unit.test_volume.GetActiveByWindowTestCase.test_snapshot_get_active_by_window -- Captured traceback: ~~~ Traceback (most recent call last): File "cinder/tests/unit/test_volume.py", line 5982, in test_snapshot_get_active_by_window datetime.datetime(1, 4, 1, 1, 1, 1)).objects File "/home/eharney/src/cinder-trunk8/.tox/py34not/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 171, in wrapper result = fn(cls, context, *args, **kwargs) File "cinder/objects/snapshot.py", line 251, in get_active_by_window snapshots, expected_attrs=['metadata']) File "/home/eharney/src/cinder-trunk8/.tox/py34not/lib/python2.7/site-packages/oslo_versionedobjects/base.py", line 991, in obj_make_list **extra_args) File "cinder/objects/snapshot.py", line 121, in _from_db_object metadata = db_snapshot.get('snapshot_metadata') File "/home/eharney/src/cinder-trunk8/.tox/py34not/lib/python2.7/site-packages/oslo_db/sqlalchemy/models.py", line 68, in get return getattr(self, key, default) File "/home/eharney/src/cinder-trunk8/.tox/py34not/lib/python2.7/site-packages/sqlalchemy/orm/attributes.py", line 237, in __get__ return self.impl.get(instance_state(instance), dict_) File "/home/eharney/src/cinder-trunk8/.tox/py34not/lib/python2.7/site-packages/sqlalchemy/orm/attributes.py", line 578, in get value = self.callable_(state, passive) File "/home/eharney/src/cinder-trunk8/.tox/py34not/lib/python2.7/site-packages/sqlalchemy/orm/strategies.py", line 502, in _load_for_state (orm_util.state_str(state), self.key) sqlalchemy.orm.exc.DetachedInstanceError: Parent instance is not bound to a Session; lazy load operation of attribute 'snapshot_metadata' cannot proceed To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1501838/+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 1590994] Re: [Regression] crash in scan_dmi_sysfs when running as non-root
This bug was fixed in the package lshw - 02.17-1.1ubuntu3.2 --- lshw (02.17-1.1ubuntu3.2) xenial; urgency=medium * d/p/Avoid-crash-in-scan_dmi_sysfs-when-running-as-non-ro.patch: Fix a regression from the last upload that causes lshw to crash when running unprivileged (LP: #1590994). -- dann frazier Tue, 14 Jun 2016 15:38:08 -0600 ** Changed in: lshw (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/1590994 Title: [Regression] crash in scan_dmi_sysfs when running as non-root Status in lshw: Unknown Status in lshw package in Ubuntu: Fix Released Status in lshw source package in Xenial: Fix Released Bug description: [Impact] lshw crashes when run as non-root: Though it does warn before crashing that it should be run as super- user, it should fail gracefully - not abort and dump core. A number of users have been hitting this since the regression has been introduced: https://errors.ubuntu.com/problem/3ef7206b4102c14c8741b44fde30b21b4a571bbe [Test Case] ubuntu@lshw:~$ lshw WARNING: you should run this program as super-user. terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Aborted (core dumped) [Regression Risk] The fix I've proposed[*] only comes into play when lshw is about to crash, so regression risk should be minimal. [*] https://github.com/lyonel/lshw/pull/14 To manage notifications about this bug go to: https://bugs.launchpad.net/lshw/+bug/1590994/+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 1484159] Re: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] is not supported
This bug was fixed in the package linux-firmware - 1.157.1 --- linux-firmware (1.157.1) xenial; urgency=medium * Add firmware for QCA9377 wireless network adapter ath10k: QCA9377 hw1.0: add firmware and board files -LP: #1484159 -- Seth Forshee Fri, 10 Jun 2016 07:34:04 -0500 ** Changed in: linux-firmware (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/1484159 Title: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter [168c:0042] is not supported Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux-firmware source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux-firmware source package in Yakkety: Fix Released Bug description: This card remains unsupported out-of-the-box by the ath10k_pci kernel module. At this point, it looks like kvalo's ath10k-firmware repo just needs to be pulled in. --- HOW TO GET THIS CARD TO WORK: I don't actually have this card, but AndyP was able to get this card to work by following my instructions, so I've written them here in a clearer format. 1) Use a kernel that supports this card Support for this card is not present in kernel 4.2. However, it was added at some point between then and kernel 4.4. If you're running Ubuntu 16.04 LTS or above, your kernel is fine; skip to the next step. If you're running Ubuntu 15.10 or below, see https://wiki.ubuntu.com/Kernel/MainlineBuilds for info on installing a newer kernel. Alternatively, you can use backports. This is a lot more work, but if you really need to keep using an older kernel for some reason, there are some guides to installing backports in the comments below. 2) Get the latest firmware from https://github.com/kvalo/ath10k- firmware/archive/master.zip wget https://github.com/kvalo/ath10k-firmware/archive/master.zip 3) Unzip the downloaded file. Inside the ath10k-firmware-master folder is a folder named QCA9377. Copy the QCA9377 folder to /lib/firmware/ath10k: unzip master.zip sudo cp -r ath10k-firmware-master/QCA9377/ /lib/firmware/ath10k/ 4) Run the following commands to rename the necessary firmware file: cd /lib/firmware/ath10k/QCA9377/hw1.0/ sudo mv firmware-5.bin_WLAN.TF.1.0-00267-1 firmware-5.bin 5) Reboot your computer. Run "lshw -C network" to see if your card is recognized. You can delete the files you downloaded earlier: cd ~ rm master.zip rm -r ath10k-firmware-master/ Please tell me if these instructions are working for you. The original bug description follows. --- Hi, Qualcomm Atheros Device [168c:0042] (rev 30) is not supported by linux kernal. Please add support. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-61-generic 3.13.0-61.100 ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu14 1658 F pulseaudio /dev/snd/controlC1: ubuntu14 1658 F pulseaudio CurrentDesktop: Unity Date: Wed Aug 12 20:31:24 2015 HibernationDevice: RESUME=UUID=0483444a-0d9a-4215-b36b-4aee75fd9ec0 InstallationDate: Installed on 2015-08-11 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Acer Aspire E5-573 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-61-generic root=UUID=72a8a100-d5ec-4e9d-8bc5-45695001a29c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-61-generic N/A linux-backports-modules-3.13.0-61-generic N/A linux-firmware 1.127.15 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: ZORO_BH dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd04/20/2015:svnAcer:pnAspireE5-573:pvrV3.72:rvnAcer:rnZORO_BH:r
[Group.of.nepali.translators] [Bug 1591010] Re: two s390x fixes for docker
This bug was fixed in the package golang-1.6 - 1.6.2-0ubuntu5~16.04 --- golang-1.6 (1.6.2-0ubuntu5~16.04) xenial; urgency=medium * Backport new upstream release to Xenial to fix epoll on ppc64el and s390x. (LP: #1567096, #1591010) -- Michael Hudson-Doyle Fri, 10 Jun 2016 15:34:17 +1200 ** Changed in: golang-1.6 (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/1591010 Title: two s390x fixes for docker Status in golang-1.6 package in Ubuntu: Fix Released Status in golang-1.6 source package in Xenial: Fix Released Bug description: [Impact] As explained in https://github.com/golang/go/issues/16021#issuecomment-225029684, the s390x port for Go contains two bugs that prevent docker from operating correctly. [Test Case] Build the docker, containerd and runc source packages from yakkety, install them "docker run s390x/ubuntu:16.04 echo hi" -- in the failing case this will hang on exit and containerd will be observed to use 100% cpu. Rebuild all packages that build-depend on golang in xenial. [Regression potential] Slight. I believe the Go point releases meet the guidelines described at https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1591010/+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 1567096] Re: Docker doesn't work since Containerd integration
This bug was fixed in the package golang-1.6 - 1.6.2-0ubuntu5~16.04 --- golang-1.6 (1.6.2-0ubuntu5~16.04) xenial; urgency=medium * Backport new upstream release to Xenial to fix epoll on ppc64el and s390x. (LP: #1567096, #1591010) -- Michael Hudson-Doyle Fri, 10 Jun 2016 15:34:17 +1200 ** Changed in: golang-1.6 (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/1567096 Title: Docker doesn't work since Containerd integration Status in golang-1.6 package in Ubuntu: Fix Released Status in golang-1.6 source package in Trusty: New Status in golang-1.6 source package in Xenial: Fix Released Bug description: -- Problem Description -- Docker build hangs indefinitely when run using a 1.11.0 binary built after containerd integration, and go 1.6 on ppc64le. Doing the same thing works with gccgo. Looking at the differences in docker logs shows that the containerd event "exit", never happens when using a binary built with gc. fsnotify, the file system handler for go, doesn't seem to receive the correct event when a file is either written to, or closed, which I believe is whats causing this issue. Link to fsnotify issue which shows some failing tests : https://github.com/fsnotify/fsnotify/issues/130 I have a patch that fixes the errors when I run fsnotify. I am preparing it for submission now and should be out there as a golang CL this morning. Do you want the patch so you can rebuild golang with it? If fsnotify is a separate package then you will have to rebuild it with the new golang. Here's the CL link if you want to get the patch for ppc64le: https://go-review.googlesource.com/#/c/21582/ Go to the upper right where it says download and I think if you select patch file it will give you the patch. We'll update with more info after testing the patch Lynn submitted, but we wanted to let Canonical know about this issue in the meantime since 1.11 is about to GA upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.6/+bug/1567096/+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 1515768] Re: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy
Also marking this as fix-released for Ubuntu since it is available in nova 13.0.0+. ** Changed in: nova (Ubuntu) Status: Confirmed => Fix Released ** Also affects: nova (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Xenial) Status: New => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1515768 Title: Instance creation fails with libvirtError: Unable to create tap device: Device or resource busy Status in OpenStack Compute (nova): Fix Released Status in tacker: Fix Committed Status in nova package in Ubuntu: Fix Released Status in nova source package in Xenial: Fix Released Bug description: Summary: This issue is observed frequently on Jenkins gate and has been reproducible in local setup too. Steps: Initiate 3 stack create requests at once in a script: heat stack-create -f /home/stack/template_file stack1 heat stack-create -f /home/stack/template_file stack2 heat stack-create -f /home/stack/template_file stack3 using the following HOT file: http://paste.openstack.org/show/479920/ One of the stack creations fails with CreateFailed: Resource Create Failed: Conflict: Resources. vdu3: Port Is Still In Use. From the nova logs, there are duplicate bridges created for one of the servers. The qemu xml fails with libvirtError: Unable to create tap device tapd3a3d9e9-5d: Device or resource busy. See timestamp 2015-11-25 23:03:14.940 in n-cpu.log Attaching the relevant n-cpu.log, q-svc.log and h-eng.log Observation: The 1st network interface for the nova instance is a Neutron Port resource provided in HOT template. Nova sends a PUT request to update the port information. It also sends 2 POST requests for the 2nd and 3rd network interfaces. Neutron receives the PUT request and sends network-event changed event while nova is still waiting for the POST response for the 2 ports. If the network-changed event is received before the 3rd port POST response is received, refresh_cache is acquired by nova_service Nova sends a query for port information, updates the cache and release the lock. By then, POST requests are completed which acquires the cache lock again and sends request for network info. refresh_cache is updated twice and contains duplicate set of ports Network vifs are built for all 6 ports and qemu xml is build based on that. Duplicate bridges in xml is complained by libvirt as device or resource busy. Version and environment: Devstack Master To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1515768/+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 1562042] Re: Traceback in error log during heat-engine service shutdown
This bug was fixed in the package heat - 1:5.0.1-0ubuntu3.1 --- heat (1:5.0.1-0ubuntu3.1) wily; urgency=medium * d/p/engine-shutdown.patch: Cherry pick fix to ensure that heat-engine worker processes are shutdown correctly when SIGINT is received early in the process lifecycle (LP: #1562042). -- James Page Tue, 10 May 2016 12:40:54 +0100 ** Changed in: heat (Ubuntu Wily) 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/1562042 Title: Traceback in error log during heat-engine service shutdown Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: Fix Committed Status in Ubuntu Cloud Archive mitaka series: Fix Committed Status in heat: Fix Released Status in heat package in Ubuntu: Fix Released Status in heat source package in Wily: Fix Released Status in heat source package in Xenial: Fix Released Status in heat source package in Yakkety: Fix Released Bug description: During shutdown of heat-engine service this traceback could be observed in log: ``` 2016-03-25 17:29:22.259 22588 DEBUG oslo_service.service [-] Stop services. stop /usr/lib/python2.7/dist-packages/oslo_service/service.py:583 2016-03-25 17:29:22.261 22588 DEBUG heat.engine.service [-] Attempting to stop engine service... _stop_rpc_server /usr/lib/python2.7/dist-packages/heat/engine/service.py:410 2016-03-25 17:29:22.262 22588 ERROR heat.engine.service [-] Failed to stop engine service, 'NoneType' object has no attribute 'stop' 2016-03-25 17:29:22.264 22588 CRITICAL heat-engine [-] AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine Traceback (most recent call last): 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/bin/heat-engine", line 10, in 2016-03-25 17:29:22.264 22588 ERROR heat-engine sys.exit(main()) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/cmd/engine.py", line 79, in main 2016-03-25 17:29:22.264 22588 ERROR heat-engine launcher.wait() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 577, in wait 2016-03-25 17:29:22.264 22588 ERROR heat-engine self.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 586, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine service.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 117, in wrapper 2016-03-25 17:29:22.264 22588 ERROR heat-engine return f(*args, **kwargs) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 426, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine for stack_id in list(self.thread_group_mgr.groups.keys()): 2016-03-25 17:29:22.264 22588 ERROR heat-engine AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine 2016-03-25 17:29:22.388 22599 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting ``` Full log could be found here: http://pastebin.com/raw/mgRbgvjd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1562042/+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 1562042] Re: Traceback in error log during heat-engine service shutdown
This bug was fixed in the package heat - 1:6.0.0-0ubuntu1.1 --- heat (1:6.0.0-0ubuntu1.1) xenial; urgency=medium * d/p/engine-shutdown.patch: Cherry pick fix to ensure that heat-engine worker processes are shutdown correctly when SIGINT is received early in the process lifecycle (LP: #1562042). -- James Page Tue, 10 May 2016 12:40:54 +0100 ** Changed in: heat (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/1562042 Title: Traceback in error log during heat-engine service shutdown Status in Ubuntu Cloud Archive: Fix Released Status in Ubuntu Cloud Archive liberty series: Fix Committed Status in Ubuntu Cloud Archive mitaka series: Fix Committed Status in heat: Fix Released Status in heat package in Ubuntu: Fix Released Status in heat source package in Wily: Fix Released Status in heat source package in Xenial: Fix Released Status in heat source package in Yakkety: Fix Released Bug description: During shutdown of heat-engine service this traceback could be observed in log: ``` 2016-03-25 17:29:22.259 22588 DEBUG oslo_service.service [-] Stop services. stop /usr/lib/python2.7/dist-packages/oslo_service/service.py:583 2016-03-25 17:29:22.261 22588 DEBUG heat.engine.service [-] Attempting to stop engine service... _stop_rpc_server /usr/lib/python2.7/dist-packages/heat/engine/service.py:410 2016-03-25 17:29:22.262 22588 ERROR heat.engine.service [-] Failed to stop engine service, 'NoneType' object has no attribute 'stop' 2016-03-25 17:29:22.264 22588 CRITICAL heat-engine [-] AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine Traceback (most recent call last): 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/bin/heat-engine", line 10, in 2016-03-25 17:29:22.264 22588 ERROR heat-engine sys.exit(main()) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/cmd/engine.py", line 79, in main 2016-03-25 17:29:22.264 22588 ERROR heat-engine launcher.wait() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 577, in wait 2016-03-25 17:29:22.264 22588 ERROR heat-engine self.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/oslo_service/service.py", line 586, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine service.stop() 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/osprofiler/profiler.py", line 117, in wrapper 2016-03-25 17:29:22.264 22588 ERROR heat-engine return f(*args, **kwargs) 2016-03-25 17:29:22.264 22588 ERROR heat-engine File "/usr/lib/python2.7/dist-packages/heat/engine/service.py", line 426, in stop 2016-03-25 17:29:22.264 22588 ERROR heat-engine for stack_id in list(self.thread_group_mgr.groups.keys()): 2016-03-25 17:29:22.264 22588 ERROR heat-engine AttributeError: 'NoneType' object has no attribute 'groups' 2016-03-25 17:29:22.264 22588 ERROR heat-engine 2016-03-25 17:29:22.388 22599 INFO oslo_service.service [-] Parent process has died unexpectedly, exiting ``` Full log could be found here: http://pastebin.com/raw/mgRbgvjd To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1562042/+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 1587667] Re: Import from Debian fails for source packages with included tarball .asc
This bug was fixed in the package dpkg - 1.16.1.2ubuntu7.8 --- dpkg (1.16.1.2ubuntu7.8) precise; urgency=medium * Backport from Debian (LP: #1587667): - Allow detached upstream signatures for upstream orig.tar files in the .dsc file. Suggested by Daniel Kahn Gillmor . Closes: #759478 - Allow detached upstream orig tarball signatures when extracting version 1.0 non-native source packages. -- Colin Watson Tue, 14 Jun 2016 19:22:53 +0100 ** Changed in: dpkg (Ubuntu Precise) 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/1587667 Title: Import from Debian fails for source packages with included tarball .asc Status in Launchpad itself: Fix Committed Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Precise: Fix Released Status in dpkg source package in Trusty: Fix Released Status in dpkg source package in Xenial: Fix Released Bug description: SRU justification: [Impact] Launchpad can't import some source packages from Debian unstable. The fix is to cherry-pick changes from unstable that support unpacking (but, for minimality, not creating) such source packages. [Test Case] For the format 3.0 case, download the limnoria source package from Debian unstable and unpack it with "dpkg-source -x". For the format 1.0 case, there are no examples as yet in unstable, but it's easy to construct one: download a 1.0 package (e.g. makepasswd), sign its .orig.tar.gz with "gpg --armor --clearsign", rebuild the source package using unstable's toolchain, and then try to unpack it with "dpkg-source -x" in precise/trusty. [Regression Potential] Confined to "dpkg-source -x", so it should be sufficient to check that unpacking packages without .orig.*.asc still works. Original report follows: https://launchpad.net/debian/+source/vlc/ is missing Debian branches for sid and stretch. This then also breaks auto-sync of some of Debian's packages to Ubuntu's development branch. This is apparently what broke the auto-import: dpkg-source: error: unrecognized file for a v2.0 source package: vlc_2.2.3.orig.tar.xz.asc See this discussion about including .asc files in Debian source packages which requires dpkg to be updated: https://lists.debian.org/debian-dpkg/2016/05/msg00041.html Initial discussion: http://irclogs.ubuntu.com/2016/05/31/%23ubuntu-devel.html#t22:44 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1587667/+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 1587667] Re: Import from Debian fails for source packages with included tarball .asc
This bug was fixed in the package dpkg - 1.17.5ubuntu5.7 --- dpkg (1.17.5ubuntu5.7) trusty; urgency=medium * Backport from Debian (LP: #1587667): - Allow detached upstream signatures for upstream orig.tar files in the .dsc file. Suggested by Daniel Kahn Gillmor . Closes: #759478 - Allow detached upstream orig tarball signatures when extracting version 1.0 non-native source packages. -- Colin Watson Tue, 14 Jun 2016 19:31:28 +0100 ** Changed in: dpkg (Ubuntu Trusty) 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/1587667 Title: Import from Debian fails for source packages with included tarball .asc Status in Launchpad itself: Fix Committed Status in dpkg package in Ubuntu: Fix Released Status in dpkg source package in Precise: Fix Released Status in dpkg source package in Trusty: Fix Released Status in dpkg source package in Xenial: Fix Released Bug description: SRU justification: [Impact] Launchpad can't import some source packages from Debian unstable. The fix is to cherry-pick changes from unstable that support unpacking (but, for minimality, not creating) such source packages. [Test Case] For the format 3.0 case, download the limnoria source package from Debian unstable and unpack it with "dpkg-source -x". For the format 1.0 case, there are no examples as yet in unstable, but it's easy to construct one: download a 1.0 package (e.g. makepasswd), sign its .orig.tar.gz with "gpg --armor --clearsign", rebuild the source package using unstable's toolchain, and then try to unpack it with "dpkg-source -x" in precise/trusty. [Regression Potential] Confined to "dpkg-source -x", so it should be sufficient to check that unpacking packages without .orig.*.asc still works. Original report follows: https://launchpad.net/debian/+source/vlc/ is missing Debian branches for sid and stretch. This then also breaks auto-sync of some of Debian's packages to Ubuntu's development branch. This is apparently what broke the auto-import: dpkg-source: error: unrecognized file for a v2.0 source package: vlc_2.2.3.orig.tar.xz.asc See this discussion about including .asc files in Debian source packages which requires dpkg to be updated: https://lists.debian.org/debian-dpkg/2016/05/msg00041.html Initial discussion: http://irclogs.ubuntu.com/2016/05/31/%23ubuntu-devel.html#t22:44 To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad/+bug/1587667/+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 1572661] Re: Ubuntu Gnome Bug -evolution translation
** Changed in: evolution (Ubuntu Xenial) Importance: Undecided => High ** Changed in: evolution (Ubuntu Xenial) 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/1572661 Title: Ubuntu Gnome Bug -evolution translation Status in evolution package in Ubuntu: Invalid Status in evolution source package in Xenial: Triaged Bug description: * Impact evolution is not translated * Test case start evolution under a non english locale, it should be translated * Regression potential none, that's a small packaging change to add translations to the deb - Ubuntu Gnome 16.04 RC Evolution is not translated in another language. It is in english only. Affects at least french (canadian), Norwegian (Bokmål) and german (seen on a Google Plus post : https://plus.google.com/+UbuntuGNOMEorg/posts/bsFL3SLf6ot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1572661/+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 1594928] Re: linux-raspi2: 4.4.0-1015.19 -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/raspi2/4.4.0-1015.19/raspi2-xenial-proposed-frozen.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/1594928 Title: linux-raspi2: 4.4.0-1015.19 -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: New 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 4.4.0-1015.19 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 -- derivative-trackers-created: true kernel-stable-master-bug: 1594906 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1594928/+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 1595495] Re: DASD drives can only hold 3 partitions
This bug was fixed in the package partman-base - 187ubuntu3 --- partman-base (187ubuntu3) yakkety; urgency=medium * On s390[x], Prevent using extended partitions on DASD drives that can only hold 3 partitions. Parted doesn't have special knowledge about that and claims that msdos partition table on DASD drives can hold usual maximum number of partitions types. LP: #1595495. -- Dimitri John Ledkov Thu, 23 Jun 2016 12:06:00 +0100 ** Changed in: partman-base (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/1595495 Title: DASD drives can only hold 3 partitions Status in partman-base package in Ubuntu: Fix Released Status in partman-base source package in Xenial: Triaged Bug description: [Impact] * DASD drives have two types ECKD and FBA. * ECKD have been made to use dasd partition table by default, however can be used with msdos partition table * FBA devices use msdos partition table by default * Both types of drives can only hold 3 partitions * However parted/partman default to using logical partitions with default installation recipe, thus exploading instalations. [Test Case] * Start the installer, activate ECKD and/or FBA devices * In case of ECKD choose to use msdos partition table (label) * The installer should only create primary partitions, and not offer to create logical partitions in any way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1595495/+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 1592114] Re: Device shutdown notification for CAPI Flash cards
https://lists.ubuntu.com/archives/kernel-team/2016-June/078524.html ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1592114 Title: Device shutdown notification for CAPI Flash cards Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: In Progress Bug description: ---Problem Description--- Some CAPI Flash cards need notification of device shutdown in order to flush pending I/Os. A PCI notification hook for shutdown has been added where the driver notifies the card and returns. When the device is removed in the PCI remove path, this code will wait for shutdown processing to complete. It could take a minimum of 1 second for shutdown processing to complete. To avoid an indefinite wait, code has been added to read the status incrementally from 100ms up to 1.5 seconds. Contact Information = ukri...@linux.vnet.ibm.com This is a defect placeholder for submitting a patch to Canonical, that is in the process of getting submitted upstream for the 4.8 kernel. We would like to have this patch included in the pointrelease, 16.04.1. Please lookout for the patch that will be attached to this bug soon and probably closer to the deadline for 16.04.1. I will submit the patch as soon as I get the review comments addressed and well tested. -- Uma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592114/+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 1595507] [NEW] World readable X11 Cookie key logger
Public bug reported: KDE Project Security Advisory = Title: kinit: World readable X11 Cookie key logger Risk Rating:Important CVE:CVE-2016-3100 Platforms: X11 Versions: kinit < 5.23 Author: Siddharth Sharma siddharth@gmail.com Date: 21 June 2016 Overview An authorized user can log key events of other user by accessing world-readable X11 cookie Impact == Pre-authenticated attacker can read all key events by the users logged on to the system. Workaround == None Solution For kinit apply the following patches: https://quickgit.kde.org/?p=kinit.git&a=commitdiff&h=dece8fd89979cd1a86c03bcaceef6e9221e8d8cd https://quickgit.kde.org/?p=kinit.git&a=commitdiff&h=72f3702dbe6cf15c06dc13da2c99c864e9022a58 References == https://bugs.kde.org/show_bug.cgi?id=358593 https://bugs.kde.org/show_bug.cgi?id=363140 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kinit 5.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jun 23 14:06:42 2016 InstallationDate: Installed on 2016-02-11 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: kinit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kinit (Ubuntu) Importance: High Assignee: Philip Muškovac (yofel) Status: New ** Affects: kinit (Ubuntu Xenial) Importance: High Assignee: Philip Muškovac (yofel) Status: New ** Tags: amd64 apport-bug xenial ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-3100 ** Changed in: kinit (Ubuntu) Importance: Undecided => High ** Changed in: kinit (Ubuntu) Assignee: (unassigned) => Philip Muškovac (yofel) ** Also affects: kinit (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: kinit (Ubuntu Xenial) Importance: Undecided => High ** Changed in: kinit (Ubuntu Xenial) Assignee: (unassigned) => Philip Muškovac (yofel) -- 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/1595507 Title: World readable X11 Cookie key logger Status in kinit package in Ubuntu: New Status in kinit source package in Xenial: New Bug description: KDE Project Security Advisory = Title: kinit: World readable X11 Cookie key logger Risk Rating:Important CVE:CVE-2016-3100 Platforms: X11 Versions: kinit < 5.23 Author: Siddharth Sharma siddharth@gmail.com Date: 21 June 2016 Overview An authorized user can log key events of other user by accessing world-readable X11 cookie Impact == Pre-authenticated attacker can read all key events by the users logged on to the system. Workaround == None Solution For kinit apply the following patches: https://quickgit.kde.org/?p=kinit.git&a=commitdiff&h=dece8fd89979cd1a86c03bcaceef6e9221e8d8cd https://quickgit.kde.org/?p=kinit.git&a=commitdiff&h=72f3702dbe6cf15c06dc13da2c99c864e9022a58 References == https://bugs.kde.org/show_bug.cgi?id=358593 https://bugs.kde.org/show_bug.cgi?id=363140 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: kinit 5.18.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jun 23 14:06:42 2016 InstallationDate: Installed on 2016-02-11 (132 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: kinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kinit/+bug/1595507/+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 1595495] [NEW] DASD drives can only hold 3 partitions
Public bug reported: [Impact] * DASD drives have two types ECKD and FBA. * ECKD have been made to use dasd partition table by default, however can be used with msdos partition table * FBA devices use msdos partition table by default * Both types of drives can only hold 3 partitions * However parted/partman default to using logical partitions with default installation recipe, thus exploading instalations. [Test Case] * Start the installer, activate ECKD and/or FBA devices * In case of ECKD choose to use msdos partition table (label) * The installer should only create primary partitions, and not offer to create logical partitions in any way ** Affects: partman-base (Ubuntu) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Affects: partman-base (Ubuntu Xenial) Importance: High Assignee: Dimitri John Ledkov (xnox) Status: Triaged ** Also affects: partman-base (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: partman-base (Ubuntu) Status: New => Triaged ** Changed in: partman-base (Ubuntu Xenial) Status: New => Triaged ** Changed in: partman-base (Ubuntu) Importance: Undecided => High ** Changed in: partman-base (Ubuntu Xenial) Importance: Undecided => High ** Changed in: partman-base (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: partman-base (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- 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/1595495 Title: DASD drives can only hold 3 partitions Status in partman-base package in Ubuntu: Triaged Status in partman-base source package in Xenial: Triaged Bug description: [Impact] * DASD drives have two types ECKD and FBA. * ECKD have been made to use dasd partition table by default, however can be used with msdos partition table * FBA devices use msdos partition table by default * Both types of drives can only hold 3 partitions * However parted/partman default to using logical partitions with default installation recipe, thus exploading instalations. [Test Case] * Start the installer, activate ECKD and/or FBA devices * In case of ECKD choose to use msdos partition table (label) * The installer should only create primary partitions, and not offer to create logical partitions in any way To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1595495/+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 1594929] Re: linux-snapdragon: 4.4.0-1018.21 -proposed tracker
Skipping certification-testing for this cycle, since we don't have a hardware for this kernel. ** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/certification-testing Assignee: Canonical Hardware Certification (canonical-hw-cert) => Yung Shen (kaxing) -- 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/1594929 Title: linux-snapdragon: 4.4.0-1018.21 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: New 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 4.4.0-1018.21 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 -- derivative-trackers-created: true kernel-stable-master-bug: 1594906 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1594929/+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 1575055] Re: check_instance_id() error on reboots when using config-drive
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Fix Committed ** Changed in: ubuntu-z-systems Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1575055 Title: check_instance_id() error on reboots when using config-drive Status in cloud-init: Fix Committed Status in Ubuntu on IBM z Systems: Fix Committed Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Bug description: Problem Description = When using a config-drive to provide meta-data to cloud-init on ubuntu (for Linux guest running in KVM for z Systems) we get a check_instance_id() error whenever we soft reboot after the (successful) initial boot. The error shows: [5.283203] cloud-init[1637]: Cloud-init v. 0.7.7 running 'init-local' at Sat, 23 Apr 2016 00:50:58 +. Up 5.25 seconds. [5.283368] cloud-init[1637]: 2016-04-22 20:50:58,839 - util.py[WARNING]: failed of stage init-local [5.286659] cloud-init[1637]: failed run of stage init-local [5.286770] cloud-init[1637]: [5.286849] cloud-init[1637]: Traceback (most recent call last): [5.286924] cloud-init[1637]: File "/usr/bin/cloud-init", line 520, in status_wrapper [5.286998] cloud-init[1637]: ret = functor(name, args) [5.287079] cloud-init[1637]: File "/usr/bin/cloud-init", line 250, in main_init [5.287152] cloud-init[1637]: init.fetch(existing=existing) [5.287225] cloud-init[1637]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 322, in fetch [5.287298] cloud-init[1637]: return self._get_data_source(existing=existing) [5.287371] cloud-init[1637]: File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 229, in _get_data_source [5.287445] cloud-init[1637]: ds.check_instance_id(self.cfg)): [5.287518] cloud-init[1637]: TypeError: check_instance_id() takes 1 positional argument but 2 were given [5.287592] cloud-init[1637]: [FAILED] Failed to start Initial cloud-init job (pre-networking). The failure of the init-local pre-networking does seem to lead to a boot up delay as cloud-init tries to search for networking outside of the already saved networking data. Otherwise the error is purely cosmetic as later init modules find (or let existing IP configuration take over) and bring up the correct interfaces. The original problem was found outside of openstack with stand-alone cloud-config iso images. But have been able to reproduce the problem within an openstack ICM environment. Team has had some success getting around the problem by patching the check_instance_id function in /usr/lib/python3/dist- packages/cloudinit/sources/DataSourceConfigDrive.py so that it accepted an extra argument, ex: ubuntu@markvercd:~$ sudo cat check_instance_id.patch --- /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py 2016-04-06 15:29:59.0 + +++ /usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py.new 2016-04-11 22:53:47.799867139 + @@ -155,7 +155,7 @@ return True -def check_instance_id(self): +def check_instance_id(self,somecfg): # quickly (local check only) if self.instance_id is still valid return sources.instance_id_matches_system_uuid(self.get_instance_id()) ubuntu@markvercd:~$ ---uname output--- Linux k6mpathcl.pokprv.stglabs.ibm.com 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:31:26 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = KVM guest on a z13 (2827-732) LPAR Steps to Reproduce = 1) set up ubuntu guest image with cloud-init 2) pass in iso image with cloud-config data in cdrom device 3) boot up successfully with cloud-config data 4) attempt a soft reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1575055/+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