[Group.of.nepali.translators] [Bug 1616740] [NEW] Revert removing gnome-maps from ubuntu-gnome-desktop
Public bug reported: Impact == Ubuntu GNOME 16.04 included gnome-maps by default. Ubuntu GNOME 16.04.1 did not but those upgrading from 15.10 or 16.04 still have gnome-maps installed. Now that gnome-maps is working again, for consistency, we should undo the removal of gnome-maps from the ubuntu-gnome-desktop metapackage (see bug 1602035 for the removal). Test Case = 1. From the Ubuntu GNOME 16.04.1 live image (or from Ubuntu GNOME clean installed after 16.04.1's release), install the update to ubuntu-gnome-desktop. gnome-maps should be automatically installed. 2. Check to see if gnome-maps shows up on http://cdimage.ubuntu.com/ubuntu-gnome/xenial/daily-live/current/xenial-desktop-amd64.manifest Regression Potential N/A ** Affects: ubuntu-gnome-meta (Ubuntu) Importance: Wishlist Status: Fix Released ** Affects: ubuntu-gnome-meta (Ubuntu Xenial) Importance: Wishlist Status: Triaged ** Tags: xenial ** Tags added: xenial ** Also affects: ubuntu-gnome-meta (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: ubuntu-gnome-meta (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: ubuntu-gnome-meta (Ubuntu Xenial) Status: New => Triaged ** Description changed: Impact == Ubuntu GNOME 16.04 included gnome-maps by default. Ubuntu GNOME 16.04.1 did not but those upgrading from 15.10 or 16.04 still have gnome-maps installed. - Now that gnome-maps is working again, for consistency, we should undo the removal of gnome-maps from the ubuntu-gnome-desktop metapackage. + Now that gnome-maps is working again, for consistency, we should undo the removal of gnome-maps from the ubuntu-gnome-desktop metapackage (see bug 1602035 for the removal). Test Case = 1. From the Ubuntu GNOME 16.04.1 live image (or from Ubuntu GNOME clean installed after 16.04.1's release), install the update to ubuntu-gnome-desktop. gnome-maps should be automatically installed. 2. Check to see if gnome-maps shows up on http://cdimage.ubuntu.com/ubuntu-gnome/xenial/daily-live/current/xenial-desktop-amd64.manifest Regression Potential N/A -- 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/1616740 Title: Revert removing gnome-maps from ubuntu-gnome-desktop Status in ubuntu-gnome-meta package in Ubuntu: Fix Released Status in ubuntu-gnome-meta source package in Xenial: Triaged Bug description: Impact == Ubuntu GNOME 16.04 included gnome-maps by default. Ubuntu GNOME 16.04.1 did not but those upgrading from 15.10 or 16.04 still have gnome-maps installed. Now that gnome-maps is working again, for consistency, we should undo the removal of gnome-maps from the ubuntu-gnome-desktop metapackage (see bug 1602035 for the removal). Test Case = 1. From the Ubuntu GNOME 16.04.1 live image (or from Ubuntu GNOME clean installed after 16.04.1's release), install the update to ubuntu-gnome-desktop. gnome-maps should be automatically installed. 2. Check to see if gnome-maps shows up on http://cdimage.ubuntu.com/ubuntu-gnome/xenial/daily-live/current/xenial-desktop-amd64.manifest Regression Potential N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1616740/+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 1616707] [NEW] SRU: New upstream bugfix release (3.18.4 and 3.10.4)
Public bug reported: Impact == gnome-maps has a new upstream bugfix release for all supported versions. The new release downloads a service.json file from GNOME that indicates the current preferred map tile server. (This is useful in case of provider changes as happened with bug 1602035). In the previous bugfix release, all requests for tiles went through a GNOME.org proxy which introduced noticeable lag. The other change is that the Mapbox attribution overlay logo is now transparent instead of being embedded in a gray rectangle. https://git.gnome.org/browse/gnome-maps/tree/NEWS?h=gnome-3-18 https://git.gnome.org/browse/gnome-maps/log?h=gnome-3-18 https://git.gnome.org/browse/gnome-maps/tree/NEWS?h=gnome-3-10 https://git.gnome.org/browse/gnome-maps/log?h=gnome-3-10 This was fixed in yakkety with https://launchpad.net/ubuntu/+source /gnome-maps/3.20.3-1 Test Case = After installing the update, open the Maps app. Scroll around, zoom in and out. Regression Potential Low. This is a GNOME bugfix release that the developer is strongly encouraging that distributors distribute. ** Affects: gnome-maps (Ubuntu) Importance: Low Status: Fix Released ** Affects: gnome-maps (Ubuntu Trusty) Importance: Low Status: In Progress ** Affects: gnome-maps (Ubuntu Xenial) Importance: Low Status: In Progress ** Tags: trusty upgrade-software-version xenial yakkety ** Also affects: gnome-maps (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gnome-maps (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: gnome-maps (Ubuntu Trusty) Status: New => In Progress ** Changed in: gnome-maps (Ubuntu Trusty) Importance: Undecided => Low ** Changed in: gnome-maps (Ubuntu Xenial) Status: New => In Progress ** Changed in: gnome-maps (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1616707 Title: SRU: New upstream bugfix release (3.18.4 and 3.10.4) Status in gnome-maps package in Ubuntu: Fix Released Status in gnome-maps source package in Trusty: In Progress Status in gnome-maps source package in Xenial: In Progress Bug description: Impact == gnome-maps has a new upstream bugfix release for all supported versions. The new release downloads a service.json file from GNOME that indicates the current preferred map tile server. (This is useful in case of provider changes as happened with bug 1602035). In the previous bugfix release, all requests for tiles went through a GNOME.org proxy which introduced noticeable lag. The other change is that the Mapbox attribution overlay logo is now transparent instead of being embedded in a gray rectangle. https://git.gnome.org/browse/gnome-maps/tree/NEWS?h=gnome-3-18 https://git.gnome.org/browse/gnome-maps/log?h=gnome-3-18 https://git.gnome.org/browse/gnome-maps/tree/NEWS?h=gnome-3-10 https://git.gnome.org/browse/gnome-maps/log?h=gnome-3-10 This was fixed in yakkety with https://launchpad.net/ubuntu/+source /gnome-maps/3.20.3-1 Test Case = After installing the update, open the Maps app. Scroll around, zoom in and out. Regression Potential Low. This is a GNOME bugfix release that the developer is strongly encouraging that distributors distribute. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-maps/+bug/1616707/+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 1591821] Re: [Feature] intel_idle for Denverton
Merged in v4.8 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) 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/1591821 Title: [Feature] intel_idle for Denverton Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: New Status in linux source package in Yakkety: Fix Released Bug description: This is intended to track intel_idle enabling for Denverton HW: Harrisonvile Upstream schedule: Kernel: 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591821/+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 1591815] Re: [Feature] EDAC: Update driver for SKX-SP
Merged in v4.8 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) 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/1591815 Title: [Feature] EDAC: Update driver for SKX-SP Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: Provide detailed memory topology and configuration information as well as translating error addresses to physical DIMM addresses. HW: Purley Upstream schedule: kernel: 4.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591815/+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 1612305] Re: linux: 4.4.0-36.55 -proposed tracker
** Changed in: kernel-sru-workflow/verification-testing 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/1612305 Title: linux: 4.4.0-36.55 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the 4.4.0-36.55 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 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1612305/+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 1607666] Re: sudo fails with host netgroup returned from freeipa
** Also affects: sudo (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/1607666 Title: sudo fails with host netgroup returned from freeipa Status in sudo package in Ubuntu: New Status in sudo source package in Xenial: New Bug description: Sudo currently fails to validate netgroups against host netgroups returned from the sss plugin, see https://fedorahosted.org/freeipa/ticket/6139 for the glory details. This was fixed in sudo 1.8.17 (https://www.sudo.ws/repos/sudo/rev/2eab4070dcf7 to be exact), which I'd very much like to see backported to Ubuntu 16.04. If possible, updating sudo completely to 1.8.17 would be nice, since there have been quite a few improvements with regards to sss and freeipa and it would be a shame if we could not benefit from them given that 16.04 is LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1607666/+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 1616318] Re: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => 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/1616318 Title: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: Fix Committed Bug description: Steps: 1) Install Ubuntu 16.04 2) Enter to Dekstop. 3) Insert the USB 3.1 key in the thunderbolt port. 4) Remove the USB 3.1 key from the thunderbolt port. 5) Insert the USB 3.1 key in the thunderbolt port. Expected results: Can detect the USB 3.1 key and system will not hang. Actual results: System Hang To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616318/+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 1591655] Re: [Feature] Instruction decoder support for new SKX instructions- AVX512
Merged in v4.8 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) 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/1591655 Title: [Feature] Instruction decoder support for new SKX instructions- AVX512 Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: Instruction decoder support for new SKX instruction AVX-512. HW：Purley upstream schedule: 4.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591655/+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 1591648] Re: [Feature] KBL: Sandy Peak(3168) WiFi/BT support
Merged in v4.8 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) 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/1591648 Title: [Feature] KBL: Sandy Peak(3168) WiFi/BT support Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: Sandy Peak (SdP) 1x1 Supports BT 4.1/4.2 Schedule: Alpha: Done Beta: Done（ww10） PV: Done (ww16) Sandy Peak is supported in kernel starting from 4.6 with a firmware available for all (iwlwifi-3168-21.ucode) To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1591648/+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 1616517] [NEW] whoopsie does not send fields from some package management application crashes
Public bug reported: The package hook for update-manager and aptdaemon add information like /var/log/apt/term.log and /var/log/apt/history.log that would be useful in debugging crashes from those applications. However, those files can be larger than 1 KB so whoopsie does not send them to the Error Tracker. We should be sending those fields along. ** Affects: whoopsie (Ubuntu) Importance: Medium Status: Triaged ** Affects: whoopsie (Ubuntu Trusty) Importance: High Status: Triaged ** Affects: whoopsie (Ubuntu Xenial) Importance: Medium Status: Triaged ** Tags: trusty xenial yakkety ** Changed in: whoopsie (Ubuntu) Status: New => Triaged ** Changed in: whoopsie (Ubuntu) Importance: Undecided => Medium ** Also affects: whoopsie (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: whoopsie (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: whoopsie (Ubuntu Trusty) Status: New => Triaged ** Changed in: whoopsie (Ubuntu Trusty) Importance: Undecided => High ** Changed in: whoopsie (Ubuntu Xenial) Status: New => Triaged ** Changed in: whoopsie (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1616517 Title: whoopsie does not send fields from some package management application crashes Status in whoopsie package in Ubuntu: Triaged Status in whoopsie source package in Trusty: Triaged Status in whoopsie source package in Xenial: Triaged Bug description: The package hook for update-manager and aptdaemon add information like /var/log/apt/term.log and /var/log/apt/history.log that would be useful in debugging crashes from those applications. However, those files can be larger than 1 KB so whoopsie does not send them to the Error Tracker. We should be sending those fields along. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1616517/+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 1520446] Re: [Feature]intel_idle enabling on Broxton-P
Merged in v4.7 ** Information type changed from Proprietary to Public ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Yakkety) 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/1520446 Title: [Feature]intel_idle enabling on Broxton-P Status in intel: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in linux source package in Yakkety: Fix Released Bug description: This feature is to track intel_idle enabling activities for Broxton-P HW: Apollo Lake Scheduler: Kernel: 4.7 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1520446/+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 1615380] Re: security issues on borgbackup
yes, 1.0.7 is fine. ** No longer affects: virtualbox (Ubuntu) ** No longer affects: virtualbox (Ubuntu Xenial) ** Also affects: borgbackup (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: borgbackup (Ubuntu Yakkety) 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/1615380 Title: security issues on borgbackup Status in borgbackup package in Ubuntu: Fix Released Status in borgbackup source package in Xenial: New Status in borgbackup source package in Yakkety: Fix Released Bug description: as explained here, upstream is asking to SRU borgbackup because of the fixes below https://github.com/borgbackup/borg/compare/28cbf2481564%5E...f32c8858ad3f https://github.com/borgbackup/borg/commit/dde18d6a7660837ce7b4f30d31960bdc74252570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1615380/+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 1581540] Re: Add oprofile support for z13
** Changed in: ubuntu-z-systems 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/1581540 Title: Add oprofile support for z13 Status in Ubuntu on IBM z Systems: Fix Released Status in oprofile package in Ubuntu: Fix Released Status in oprofile source package in Xenial: Fix Released Bug description: == Comment: #0 - Aziz Rozyev - 2016-04-20 11:19:50 == ---Problem Description--- operf failure, 'strace operf' shows that it tries to get 'cpu_type' from /proc/cpuinfo, whereas there is no such field in cpuinfo. Contact Information = Aziz Rozyev/aziz.roz...@ru.ibm.com ---uname output--- Linux s35lp26 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:07:12 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 lpar type: 2964 model: 703 N96 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- run 'operf' Userspace tool common name: operf The userspace tool has the following bit modes: tested on 64bit Userspace tool obtained from project website: na *Additional Instructions for Aziz Rozyev/aziz.roz...@ru.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #4 - Andreas Arnez - 2016-05-12 04:52:40 == So far oprofile didn't support z13. A patch for adding z13 support has now been posted upstream: http://marc.info/?l=oprofile-list&m=146298177508640&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1581540/+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 1593953] Re: EC_KEY_generate_key() causes FIPS self-test failure
Hello Kazuki, or anyone else affected,
Accepted openssl into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu4.3 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: openssl (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed
--
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/1593953
Title:
EC_KEY_generate_key() causes FIPS self-test failure
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Bug description:
EC_KEY_generate_key() internally calls fips_pkey_signature_test()
which performs a pairwise check by ECDSA signing/verifying, but some
groups don't support ECDSA.
For example, `openssl ecparam -genkey -name Oakley-EC2N-4` fails.
Unfortunately `openssl ecparam` doesn't give any useful information so
I modified a bit:
~~~
diff --git a/apps/ecparam.c b/apps/ecparam.c
index 71b67f4..db89c2f 100644
--- a/apps/ecparam.c
+++ b/apps/ecparam.c
@@ -585,6 +585,7 @@ int MAIN(int argc, char **argv)
if (!EC_KEY_generate_key(eckey)) {
EC_KEY_free(eckey);
+ERR_print_errors(bio_err);
goto end;
}
if (outformat == FORMAT_ASN1)
~~~
And I got:
~~~
$ LD_LIBRARY_PATH=$(pwd)/target/lib ./target/bin/openssl ecparam -genkey
-name Oakley-EC2N-4
-BEGIN EC PARAMETERS-
BgA=
-END EC PARAMETERS-
140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no
inverse:bn_gcd.c:525:
140614096975512:error:0306E06C:bignum routines:BN_mod_inverse:no
inverse:bn_gcd.c:525:
140614096975512:error:2A067003:lib(42):ECDSA_sign_setup:BN lib:ecs_ossl.c:206:
140614096975512:error:2A06502A:lib(42):ECDSA_do_sign:reason(42):ecs_ossl.c:302:
140614096975512:error:2D079089:FIPS routines:fips_pkey_signature_test:test
failure:fips_post.c:166:
140614096975512:error:2D06A07F:FIPS routines:FIPS_CHECK_EC:pairwise test
failed:ec_key.c:249:
~~~
I'm using Ubuntu 16.04 and openssl 1.0.2g-1ubuntu4.1.
This was originally reported at Ruby's issue tracker:
https://bugs.ruby-lang.org/issues/12504
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1593953/+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 1594748] Re: CRYPTO_set_mem_functions() is broken
Hello Timo, or anyone else affected,
Accepted openssl into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/openssl/1.0.2g-
1ubuntu4.3 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: openssl (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed
--
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/1594748
Title:
CRYPTO_set_mem_functions() is broken
Status in OpenSSL:
Unknown
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Xenial:
Fix Committed
Bug description:
Description: Ubuntu 16.04 LTS
Release: 16.04
openssl:
Installed: 1.0.2g-1ubuntu4.1
Candidate: 1.0.2g-1ubuntu4.1
Version table:
*** 1.0.2g-1ubuntu4.1 500
500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
100 /var/lib/dpkg/status
1.0.2g-1ubuntu4 500
500 http://fi.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
CRYPTO_set_mem_functions() always returns 0 because library
initialization already calls CRYPTO_malloc() and disables it:
#0 CRYPTO_malloc (num=num@entry=1168, file=file@entry=0x770ae02c
"fips_drbg_lib.c",
line=line@entry=106) at mem.c:329
#1 0x770596df in FIPS_drbg_new (type=type@entry=0,
flags=flags@entry=0)
at fips_drbg_lib.c:106
#2 0x7705aeb9 in FIPS_drbg_health_check (
dctx=dctx@entry=0x7731c960 ) at fips_drbg_selftest.c:760
#3 0x770595f0 in FIPS_drbg_init (dctx=dctx@entry=0x7731c960
,
type=, flags=) at fips_drbg_lib.c:94
#4 0x76fe38f3 in RAND_init_fips () at rand_lib.c:287
#5 0x76f26f7a in OPENSSL_init_library () at o_init.c:119
#6 0x77de74ea in call_init (l=, argc=argc@entry=1,
argv=argv@entry=0x7fffe5e8, env=env@entry=0x7fffe5f8) at
dl-init.c:72
#7 0x77de75fb in call_init (env=0x7fffe5f8, argv=0x7fffe5e8,
argc=1,
l=) at dl-init.c:30
#8 _dl_init (main_map=main_map@entry=0x640380, argc=1, argv=0x7fffe5e8,
env=0x7fffe5f8) at dl-init.c:120
This doesn't happen in upstream OpenSSL or in Debian's OpenSSL.
Looking at the patches, this is caused by FIPS_drbg_init() in
openssl-1.0.2g-fips.patch:
+if (!(dctx->xflags & DRBG_FLAG_TEST)) {
+if (!FIPS_drbg_health_check(dctx)) {
+FIPSerr(FIPS_F_FIPS_DRBG_INIT, FIPS_R_SELFTEST_FAILURE);
+return 0;
+}
+}
I don't want any FIPS mode enabled though, so does it really even need
to call RAND_init_fips() then?
To manage notifications about this bug go to:
https://bugs.launchpad.net/openssl/+bug/1594748/+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 1615380] Re: security issues on borgbackup
Can you confirm if everything is fixed in Yakkety first? Thanks ** Also affects: virtualbox (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: borgbackup (Ubuntu) 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/1615380 Title: security issues on borgbackup Status in borgbackup package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in borgbackup source package in Xenial: New Status in virtualbox source package in Xenial: New Bug description: as explained here, upstream is asking to SRU borgbackup because of the fixes below https://github.com/borgbackup/borg/compare/28cbf2481564%5E...f32c8858ad3f https://github.com/borgbackup/borg/commit/dde18d6a7660837ce7b4f30d31960bdc74252570 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1615380/+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 1578833] Re: pollinate should not run in containers and only for first boot
This bug was fixed in the package pollinate - 4.21-0ubuntu1~14.04 --- pollinate (4.21-0ubuntu1~14.04) trusty-proposed; urgency=medium [ Dustin Kirkland ] * pollinate: - fix broken printing of binary data, this was breaking check_pollen nagios scripts on the server [ Junien Fridrick ] * entropy.ubuntu.com.pem: - simplify CA cert to just the DigiCert chain (drop GoDaddy) pollinate (4.20-0ubuntu1) yakkety; urgency=medium * debian/control: - drop the anerd references, hasn't existed in basically forever - update description - add dummy | dh-apparmor dependency to get this building on precise, where dh-systemd doesn't exist - drop run-one dependency, no longer needed - make the bsdutils dependency (for logger) explicit, add epoch * debian/rules: - use systemd, when possible * pollinate: - fix breakage on older (trusty, precise) Ubuntu, where logger does not support --id=[ID]; check version of bsdutils (provides logger) to ensure that it's at least ubuntu wily - cloud-init version string * debian/pollinate.service, debian/pollinate.upstart: - improve the init messages logged pollinate (4.19-0ubuntu1) yakkety; urgency=medium [ Martin Pitt ] * debian/pollinate.service: Move installation from network.target to multi-user.target. network.target is too early and causes dependency loops with e. g. NFS. (LP: #1576333) * debian/pollinate.preinst: Clean up old enablement symlink on upgrade. This needs to be kept until after 18.04 LTS. pollinate (4.18-0ubuntu1) yakkety; urgency=medium * debian/pollinate.service: - move to later in boot, after network starts, but before ssh starts pollinate (4.17-0ubuntu1) yakkety; urgency=medium * debian/pollinate.service: - use the right flag file for LP: #1578833 pollinate (4.16-0ubuntu1) yakkety; urgency=medium [ Martin Pitt ] * Don't run pollinate.service in containers (as containers can't and should not write the host's random pool) and when we already have a saved random seeds (i. e. only on first boot). (LP: #1578833) * Bump Standards-Version to 3.9.8 (no changes needed). [ Dustin Kirkland ] * pollinate: use timeout(1) to limit curl, related to LP: #1578833 pollinate (4.15-0ubuntu1) xenial; urgency=medium * pollinate: LP: #1555362 - log the right pid pollinate (4.14-0ubuntu1) xenial; urgency=medium * pollinate, pollinate.1: LP: #1554152 - change the failure mode of pollinate, so as to more cleanly tolerate network failures - add a --strict option to re-enable the previous behavior, ie, strictly exit non-zero if pollinate fails for any reason - we've always promised that pollinate would operate on a best-effort basis, improving the prng seeding when possible, but failing gracefully when not possible; as such, we've made good on the first half of that promise, however, the latter half has proven troublesome; this is due to the fact that if pollinate exits non-zero, then its callers (cloud-init, maas, etc.) may well interpret the behavior strictly as a failure to boot the system, when in fact that's not the case; instead, we'll clearly print a warning to syslog, and we'll retry the seeding on next pollinate service start (e.g. a reboot); moreover, we'll carry a --strict flag in the case that users want to opt into the previous behavior pollinate (4.13-0ubuntu1) wily; urgency=medium [ Robie Basak ] * entropy.ubuntu.com.pem: - Add "DigiCert Global Root CA" certificate from ca-certificates package to entropy.ubuntu.com.pem. This is required to correctly verify against the new entropy.ubuntu.com SSL certificate. pollinate (4.12-0ubuntu1) wily; urgency=medium * pollinate: - add cpu hardware model to user agent * entropy.ubuntu.com.pem: - entropy.ubuntu.com SSL is coming up for renewal on 2015-09-15 - update the certs for the pollinate package - Note that this changes the issuing CA to DigiCert, which requires a new intermediary. -- Dustin Kirkland Mon, 11 Jul 2016 10:52:57 -0500 ** Changed in: pollinate (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/1578833 Title: pollinate should not run in containers and only for first boot Status in pollinate package in Ubuntu: Fix Released Status in pollinate source package in Trusty: Fix Released Status in pollinate source package in Xenial: Fix Released Bug description: Booting a xenial cloud image in lxd shows that pollinate by far is the biggest bottleneck: $ systemd-analyze blame 2.756s pollinate.service 656ms cloud-init-local.service 598ms cloud-init.service 509ms cloud-config.service
[Group.of.nepali.translators] [Bug 1581540] Re: Add oprofile support for z13
This bug was fixed in the package oprofile - 1.1.0-0ubuntu1.1 --- oprofile (1.1.0-0ubuntu1.1) xenial; urgency=medium * Cherrypick platfroms from upstream git and mailing list: - Goldmont - z13 LP: #1581540 -- Dimitri John Ledkov Fri, 20 May 2016 11:10:58 +0100 ** Changed in: oprofile (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/1581540 Title: Add oprofile support for z13 Status in Ubuntu on IBM z Systems: Fix Committed Status in oprofile package in Ubuntu: Fix Released Status in oprofile source package in Xenial: Fix Released Bug description: == Comment: #0 - Aziz Rozyev - 2016-04-20 11:19:50 == ---Problem Description--- operf failure, 'strace operf' shows that it tries to get 'cpu_type' from /proc/cpuinfo, whereas there is no such field in cpuinfo. Contact Information = Aziz Rozyev/aziz.roz...@ru.ibm.com ---uname output--- Linux s35lp26 4.4.0-15-generic #31-Ubuntu SMP Fri Mar 18 19:07:12 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = z13 lpar type: 2964 model: 703 N96 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- run 'operf' Userspace tool common name: operf The userspace tool has the following bit modes: tested on 64bit Userspace tool obtained from project website: na *Additional Instructions for Aziz Rozyev/aziz.roz...@ru.ibm.com: -Attach ltrace and strace of userspace application. == Comment: #4 - Andreas Arnez - 2016-05-12 04:52:40 == So far oprofile didn't support z13. A patch for adding z13 support has now been posted upstream: http://marc.info/?l=oprofile-list&m=146298177508640&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1581540/+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 1576333] Re: runs to early, causes dependency loops
This bug was fixed in the package pollinate - 4.21-0ubuntu1~14.04 --- pollinate (4.21-0ubuntu1~14.04) trusty-proposed; urgency=medium [ Dustin Kirkland ] * pollinate: - fix broken printing of binary data, this was breaking check_pollen nagios scripts on the server [ Junien Fridrick ] * entropy.ubuntu.com.pem: - simplify CA cert to just the DigiCert chain (drop GoDaddy) pollinate (4.20-0ubuntu1) yakkety; urgency=medium * debian/control: - drop the anerd references, hasn't existed in basically forever - update description - add dummy | dh-apparmor dependency to get this building on precise, where dh-systemd doesn't exist - drop run-one dependency, no longer needed - make the bsdutils dependency (for logger) explicit, add epoch * debian/rules: - use systemd, when possible * pollinate: - fix breakage on older (trusty, precise) Ubuntu, where logger does not support --id=[ID]; check version of bsdutils (provides logger) to ensure that it's at least ubuntu wily - cloud-init version string * debian/pollinate.service, debian/pollinate.upstart: - improve the init messages logged pollinate (4.19-0ubuntu1) yakkety; urgency=medium [ Martin Pitt ] * debian/pollinate.service: Move installation from network.target to multi-user.target. network.target is too early and causes dependency loops with e. g. NFS. (LP: #1576333) * debian/pollinate.preinst: Clean up old enablement symlink on upgrade. This needs to be kept until after 18.04 LTS. pollinate (4.18-0ubuntu1) yakkety; urgency=medium * debian/pollinate.service: - move to later in boot, after network starts, but before ssh starts pollinate (4.17-0ubuntu1) yakkety; urgency=medium * debian/pollinate.service: - use the right flag file for LP: #1578833 pollinate (4.16-0ubuntu1) yakkety; urgency=medium [ Martin Pitt ] * Don't run pollinate.service in containers (as containers can't and should not write the host's random pool) and when we already have a saved random seeds (i. e. only on first boot). (LP: #1578833) * Bump Standards-Version to 3.9.8 (no changes needed). [ Dustin Kirkland ] * pollinate: use timeout(1) to limit curl, related to LP: #1578833 pollinate (4.15-0ubuntu1) xenial; urgency=medium * pollinate: LP: #1555362 - log the right pid pollinate (4.14-0ubuntu1) xenial; urgency=medium * pollinate, pollinate.1: LP: #1554152 - change the failure mode of pollinate, so as to more cleanly tolerate network failures - add a --strict option to re-enable the previous behavior, ie, strictly exit non-zero if pollinate fails for any reason - we've always promised that pollinate would operate on a best-effort basis, improving the prng seeding when possible, but failing gracefully when not possible; as such, we've made good on the first half of that promise, however, the latter half has proven troublesome; this is due to the fact that if pollinate exits non-zero, then its callers (cloud-init, maas, etc.) may well interpret the behavior strictly as a failure to boot the system, when in fact that's not the case; instead, we'll clearly print a warning to syslog, and we'll retry the seeding on next pollinate service start (e.g. a reboot); moreover, we'll carry a --strict flag in the case that users want to opt into the previous behavior pollinate (4.13-0ubuntu1) wily; urgency=medium [ Robie Basak ] * entropy.ubuntu.com.pem: - Add "DigiCert Global Root CA" certificate from ca-certificates package to entropy.ubuntu.com.pem. This is required to correctly verify against the new entropy.ubuntu.com SSL certificate. pollinate (4.12-0ubuntu1) wily; urgency=medium * pollinate: - add cpu hardware model to user agent * entropy.ubuntu.com.pem: - entropy.ubuntu.com SSL is coming up for renewal on 2015-09-15 - update the certs for the pollinate package - Note that this changes the issuing CA to DigiCert, which requires a new intermediary. -- Dustin Kirkland Mon, 11 Jul 2016 10:52:57 -0500 ** Changed in: pollinate (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/1576333 Title: runs to early, causes dependency loops Status in pollinate package in Ubuntu: Fix Released Status in pollinate source package in Trusty: Fix Released Status in pollinate source package in Xenial: Fix Released Status in pollinate source package in Yakkety: Fix Released Bug description: The first half of the original bug report got fixed in bug 1578833, but pollinate still runs to early. SRU INFORMATION === Impact: Causes service failures during boot when using NFS mounts, reg
[Group.of.nepali.translators] [Bug 1610252] Re: nsx.ini installed to incorrect location
This bug was fixed in the package vmware-nsx - 8.0.0-0ubuntu0.16.04.2
---
vmware-nsx (8.0.0-0ubuntu0.16.04.2) xenial; urgency=medium
* d/python-vmware-nsx.{install,maintscript}: Install nsx.ini to
/etc/neutron/plugins/vmware rather than directly into /etc/neutron,
and deal with migration of any user changes (LP: #1610252).
vmware-nsx (8.0.0-0ubuntu0.16.04.1) xenial; urgency=medium
[ James Page ]
* New upstream release for OpenStack Mitaka (LP: #1600162, Closes: #830337).
* Align (Build-)Depends with upstream.
* Fix epoch for python-neutron-lbaas dependencies.
* Switch to ostestr for unit test execution, avoiding test races and
associated FTBFS (Closes: #830337).
* Add BD on python-testresources (indirect test dependency).
[ Ondřej Nový ]
* Fixed VCS URLs (https).
* d/rules: Removed UPSTREAM_GIT with default value
* d/copyright: Changed source URL to https protocol
-- James Page Fri, 05 Aug 2016 14:46:20 +0100
** Changed in: vmware-nsx (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/1610252
Title:
nsx.ini installed to incorrect location
Status in vmware-nsx package in Ubuntu:
Fix Released
Status in vmware-nsx source package in Xenial:
Fix Released
Status in vmware-nsx source package in Yakkety:
Fix Released
Bug description:
[Impact]
nsx.ini configuration file is not installed inline with driver documentation,
creating end user confusion.
[Test Case]
sudo apt-get install python-vmware-nsx
Currently nsx.ini is installed into /etc/neutron; the expected
location is /etc/neutron/plugins/vmware/nsx.ini.
[Regression Potential]
Minimal; update will deal with any end user changes as well.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vmware-nsx/+bug/1610252/+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 1600162] Re: 1.0.0 release is not compatible with OpenStack Mitaka
This bug was fixed in the package vmware-nsx - 8.0.0-0ubuntu0.16.04.2
---
vmware-nsx (8.0.0-0ubuntu0.16.04.2) xenial; urgency=medium
* d/python-vmware-nsx.{install,maintscript}: Install nsx.ini to
/etc/neutron/plugins/vmware rather than directly into /etc/neutron,
and deal with migration of any user changes (LP: #1610252).
vmware-nsx (8.0.0-0ubuntu0.16.04.1) xenial; urgency=medium
[ James Page ]
* New upstream release for OpenStack Mitaka (LP: #1600162, Closes: #830337).
* Align (Build-)Depends with upstream.
* Fix epoch for python-neutron-lbaas dependencies.
* Switch to ostestr for unit test execution, avoiding test races and
associated FTBFS (Closes: #830337).
* Add BD on python-testresources (indirect test dependency).
[ Ondřej Nový ]
* Fixed VCS URLs (https).
* d/rules: Removed UPSTREAM_GIT with default value
* d/copyright: Changed source URL to https protocol
-- James Page Fri, 05 Aug 2016 14:46:20 +0100
** Changed in: vmware-nsx (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/1600162
Title:
1.0.0 release is not compatible with OpenStack Mitaka
Status in vmware-nsx package in Ubuntu:
Fix Released
Status in vmware-nsx source package in Xenial:
Fix Released
Status in vmware-nsx source package in Yakkety:
Fix Released
Bug description:
[Impact]
NSX SDN support is currently broken in Ubuntu 16.04
[Test Case]
Deploy OpenStack with NSX SDN; resulting cloud is not functional
Package FTBFS, with missing dependencies and then incompatibilities with
neutron core.
[Regression Potential]
Well it can't get much worse that it is now..
[Original Bug Report]
The vmware-nsx team released an 8.0.0 release (which is compatible with
OpenStack Mitaka as shipped in 16.04); the 1.0.0 release a) fails to pass its
unit tests a b) is not compatible with Mitaka.
We need to update to 8.0.0 to provide compatibility.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vmware-nsx/+bug/1600162/+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 1616157] Re: [SRU] 2.13
** Also affects: snapd (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/1616157 Title: [SRU] 2.13 Status in snapd package in Ubuntu: New Status in snapd source package in Xenial: New Bug description: This is a new version of snapd. The changelog for 2.13 is available here https://github.com/snapcore/snapd/blob/2.13/debian/changelog, the raw git changelog is available here: https://github.com/snapcore/snapd/commits/2.13 (note that the debian changelog is auto-generated from the merges of the git commits so there is usually no need to look at the raw git commits). The snappy team released a new 2.13 micro release that we want SRU into xenial. The new process described in https://wiki.ubuntu.com/SnapdUpdates was used and we have done integration-tests on the snappy images, autopkgtests on classic and unit tests. The following automatic tests are run: - travis unit tests https://travis-ci.org/snapcore/snapd/branches (check for 2.13 here) - travis/spread based integration/system tests: https://travis-ci.org/snapcore/snapd/branches (check for 2.13 here under "spread") - jenkins autopkgtests http://162.213.35.179:8080/job/snappy-by-tag-autopkgtest/17/ - jenkins integration tests: http://162.213.35.179:8080/job/snappy-by-tag-integration-test/18/ The following additional tests were performed: """ - adt-buildvm-ubuntu-cloud - customize the resulting image: "sudo apt install snapd && sudo snap install hello-world && hello-world.env && sudo snap remove hello-world" (ensures the base image has the old debs and the daemon has some state) - adt-run --source snapd_2.13.dsc --- adt-virt-qemu adt-xenial-amd64-cloud.img: PASS """ This included the upgrade from 2.12 as part of the autopkgtest run. There are also various snaps installed/removed (including installing and running ubuntu-calculator-app in xvfb) and run as part of the auto pkg test, including reboots to ensure that the system keeps working over reboots. After installing the new snapd it was ensured that apt is unaffected by doing: """ - sudo apt install -y hello && sudo apt remove -y hello """ After installing the new snapd gnome-software was used: """ - install "http" (snap) and remove it again """ All worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1616157/+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 1567540] Re: ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes up or down.)
This bug was fixed in the package ntp - 1:4.2.8p4+dfsg-3ubuntu5.1 --- ntp (1:4.2.8p4+dfsg-3ubuntu5.1) xenial; urgency=medium * d/p/ntp-4.2.8p4-segfaults-[1-3]-3.patch fix startup crashes by including Juergen Perlinger's work on upstream bugs 2954 and 2831 to fix those (LP: #1567540). -- Christian Ehrhardt Mon, 01 Aug 2016 10:50:52 +0200 ** Changed in: ntp (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/1567540 Title: ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes up or down.) Status in NTP: Fix Released Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Xenial: Fix Released Bug description: [Impact] * In NTP 4.2.8p4 there are several races that can cause a crash on startup or on a bit later but still on startup by DNS querying a peer. * The crash obviously affects users, especially as it seems - due to its racy nature - not appear on most, but severely hamstring some other users. * The details are a bit blurred, but overall there were four fixes upstream that address just this "kind of issue" that seemed to surface post 4.2.8p4. [Test Case] * Start NTP (service) * Expectation: work * Failure: Crash * Constraints: this is a race, it seems to appear at <0.1% chance to all systems I have (or lower - as I just can say it didn't trigger in 1000 tests). But that matches other reports. OTOH for some systems it seems to trigger >50% which also matches the high amount of crash reports (close to 20k now) as referred in comment 43 [Regression Potential] * Eventually the change is rather invasive as it changes the locking scheme of parts of the code - so there surely is some regression potential. * Fortunately all of this change is upstream and tested there quite heavily. Most of it for a few months already. * I tested as good as I could and could neither in code nor in test find an obvious weakness, and looking at all the crash reports it is about time. [Other Info] * While all study of bugs, upstream changes and tests suggest we haven't broken anything, still I have to admit that "on my own" I can't confirm that it fixed the bug. So we are really dependent on the reporters here that seem to have the kind of hardware where it "crashes reliably". ntp crashes every time the network goes up or down while the system is running and also crashes after booting up without network. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-03-12 (26 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu4 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-03-12 (31 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=306314bc-efcb-4c2d-b0e9-e05ec92ed0f0 ro ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-13 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160412) NtpStatus: ntpq: read: Connection refused Package: ntp 1:4.2.8p4+dfsg-3ubuntu5 PackageArchitecture: amd64 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=13f57794-2e19-4a56-836a-94185bba5ec5 ro quiet splash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVe
[Group.of.nepali.translators] [Bug 1612291] Re: cannot create $SNAP_USER_DATA when using ecryptfs and sudo
This bug was fixed in the package snap-confine - 1.0.38-0ubuntu0.16.04.8
---
snap-confine (1.0.38-0ubuntu0.16.04.8) xenial; urgency=medium
* debian/patches/04_not_die_unknown_locations.patch:
- move to /tmp if the current location can not be preserved
(LP: #1612684)
snap-confine (1.0.38-0ubuntu0.16.04.7) xenial; urgency=medium
* fix apparmor rules when a snap is run on new-style encrypted
home with sudo (LP: #1612291)
snap-confine (1.0.38-0ubuntu0.16.04.6) xenial; urgency=medium
* fix apparmor rules when a snap is run on encrypted home
with sudo (LP: #1612291)
snap-confine (1.0.38-0ubuntu0.16.04.5) xenial; urgency=medium
* 03_fix_snap_user_data_regression.patch:
- fix regression in autopkgtest with snap-confine when the
SNAP_USER_DATA directory is not created for services
(LP: #1612120)
-- Michael Vogt Fri, 12 Aug 2016 16:45:17
+0200
** Changed in: snap-confine (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/1612291
Title:
cannot create $SNAP_USER_DATA when using ecryptfs and sudo
Status in Snappy Launcher:
Fix Released
Status in snap-confine package in Ubuntu:
Fix Released
Status in snap-confine source package in Xenial:
Fix Released
Bug description:
Because of the two apparmor rules on snap-confine, attempts to create
user data directory from snap-confine will fail when the user is using
new-style encrypted home directory and sudo to start a snap.
TEST CASE:
1. sudo adduser --encrypt-home test-encrypted
2. Ensure that the test-encrypted user can use sudo, e.g. add it to the sudo
group
3. Log in as test-encrypted user
4. Install the hello-world snap
5. Run sudo /snap/bin/hello-world
6. Verify that `hello-world` fails to run
7. Install snap-confine from xenial-propsoed
8. verify that `hello-world` runs now
The following patch makes the problem go away:
diff --git a/debian/usr.bin.snap-confine b/debian/usr.bin.snap-confine
index f3e6308..aeb17bd 100644
--- a/debian/usr.bin.snap-confine
+++ b/debian/usr.bin.snap-confine
@@ -155,6 +155,6 @@
owner @{HOME}/.Private/ r,
owner @{HOME}/.Private/** mrixwlk,
# new-style encrypted $HOME
-owner @{HOMEDIRS}/.ecryptfs/*/.Private/ r,
-owner @{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
+@{HOMEDIRS}/.ecryptfs/*/.Private/ r,
+@{HOMEDIRS}/.ecryptfs/*/.Private/** mrixwlk,
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/snap-confine/+bug/1612291/+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 1612120] Re: $SNAP_USER_DATA is no longer created by snap-confine but is not yet created by snapd
This bug was fixed in the package snap-confine - 1.0.38-0ubuntu0.16.04.8 --- snap-confine (1.0.38-0ubuntu0.16.04.8) xenial; urgency=medium * debian/patches/04_not_die_unknown_locations.patch: - move to /tmp if the current location can not be preserved (LP: #1612684) snap-confine (1.0.38-0ubuntu0.16.04.7) xenial; urgency=medium * fix apparmor rules when a snap is run on new-style encrypted home with sudo (LP: #1612291) snap-confine (1.0.38-0ubuntu0.16.04.6) xenial; urgency=medium * fix apparmor rules when a snap is run on encrypted home with sudo (LP: #1612291) snap-confine (1.0.38-0ubuntu0.16.04.5) xenial; urgency=medium * 03_fix_snap_user_data_regression.patch: - fix regression in autopkgtest with snap-confine when the SNAP_USER_DATA directory is not created for services (LP: #1612120) -- Michael Vogt Fri, 12 Aug 2016 16:45:17 +0200 ** Changed in: snap-confine (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/1612120 Title: $SNAP_USER_DATA is no longer created by snap-confine but is not yet created by snapd Status in Snappy Launcher: Fix Released Status in snap-confine package in Ubuntu: Fix Released Status in snap-confine source package in Xenial: Fix Released Bug description: We've noticed that the code that creates the $SNAP_USER_DATA directory has now been removed from snap-confine for the past few releases but the corresponding code in snapd, that depends on snap-exec, is not yet active. This has lead to some snaps that rely on it to have no way to create per-user data directories. TEST CASE: 1. sudo snap install bluez 2. sudo systemctl status snap.bluez.obex 3. verify that it fails to start the service 4. install snapd from xenial-proposed 5. snap remove bluez 6. snap install bluez 7. repeat (2) 8. verify that it works this time To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1612120/+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 1612684] Re: dies when run in a place that is not inside the snap chroot
This bug was fixed in the package snap-confine - 1.0.38-0ubuntu0.16.04.8 --- snap-confine (1.0.38-0ubuntu0.16.04.8) xenial; urgency=medium * debian/patches/04_not_die_unknown_locations.patch: - move to /tmp if the current location can not be preserved (LP: #1612684) snap-confine (1.0.38-0ubuntu0.16.04.7) xenial; urgency=medium * fix apparmor rules when a snap is run on new-style encrypted home with sudo (LP: #1612291) snap-confine (1.0.38-0ubuntu0.16.04.6) xenial; urgency=medium * fix apparmor rules when a snap is run on encrypted home with sudo (LP: #1612291) snap-confine (1.0.38-0ubuntu0.16.04.5) xenial; urgency=medium * 03_fix_snap_user_data_regression.patch: - fix regression in autopkgtest with snap-confine when the SNAP_USER_DATA directory is not created for services (LP: #1612120) -- Michael Vogt Fri, 12 Aug 2016 16:45:17 +0200 ** Changed in: snap-confine (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/1612684 Title: dies when run in a place that is not inside the snap chroot Status in Snappy Launcher: Fix Released Status in snap-confine package in Ubuntu: Fix Released Status in snap-confine source package in Xenial: Fix Released Bug description: When running any snap from a place that is not inside the snap chroot (like /tmp/some-subdir or /srv) running the snap-confine launcher dies with a ugly error. TEST CASE: 1. mkdir /tmp/99 2. cd /tmp/99 3. sudo snap install hello-world 4. verify that it shows: "cannot remain in /tmp/99, please run this snap from another location. errmsg: No such file or directory" 5. install snap-confine from xenial-proposed 6. verify that hello-world runs now (and shows a message that it switches to /tmp) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-confine/+bug/1612684/+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 1579834] Re: update-apt-xapian-index-dbus fails because of wrong import
Hello Carlo, or anyone else affected, Accepted into xenial-proposed. The package will build now and be available in a few hours 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! ** Changed in: apt-xapian-index (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/1579834 Title: update-apt-xapian-index-dbus fails because of wrong import Status in apt-xapian-index package in Ubuntu: Fix Released Status in apt-xapian-index source package in Xenial: Fix Released Bug description: [Test Case] 1) run /usr/share/apt-xapian-index/update-apt-xapian-index-dbus 2) Observe it terminate with an error and does not update the index "Failed to import 'No module named 'glib'', can not use dbus" With the version from proposed it should not exit with this error. [Expected result] 1) sudo rm -rf /var/lib/apt-xapian-index/ 2) make sure no other instance of update-apt-xapian-index-dbus is running 3) run sudo /usr/share/apt-xapian-index/update-apt-xapian-index-dbus 4) leave u-axi-dbus running, and run kcmshell5 kcm_driver_manager 5) u-axi-dbus produces no output (instead of the failure message), and after some time /var/lib/apt-xapian-index/ is created and populated again and the driver manager shows suggested packages instead of "collecting information" (see also bug #1530523) [Regression Potential] It doesn't work at all, so this'll be an improvement. - Mai 09 15:42:10 bear dbus[1017]: [system] Activating service name='org.debian.AptXapianIndex' (using servicehelper) Mai 09 15:42:10 bear org.debian.AptXapianIndex[1017]: Failed to import 'No module named 'glib'', can not use dbus Mai 09 15:42:11 bear dbus[1017]: [system] Activated service 'org.debian.AptXapianIndex' failed: Launch helper exited with unknown return code 1 The correct import should be: from gi.repository import GLib as glib from gi.repository import GObject as gobject ProblemType: BugDistroRelease: Ubuntu 16.04 Package: apt-xapian-index 0.47ubuntu8 [modified: usr/share/apt-xapian-index/update-apt-xapian-index-dbus] ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Mon May 9 17:52:17 2016 InstallationDate: Installed on 2015-05-04 (370 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) PackageArchitecture: allSourcePackage: apt-xapian-index UpgradeStatus: Upgraded to xenial on 2016-05-04 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1579834/+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
