[Group.of.nepali.translators] [Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
** Changed in: shim (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/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim Status in shim package in Ubuntu: Fix Released Status in shim source package in Xenial: Fix Released Bug description: Sometime after August 25th (or so) something changed in the Yakkety ISOs that make them no longer boot under QEMU in UEFI mode. However, the ISOs do work fine still on the physical UEFI hardware I've tested (3 different systems). I'm not sure about other VM solutions like Virtual Box, etc., as I haven't tested under anything other than QEMU. But under QEMU, UEFI mode installs are definitely broken. You get stuck in the OVMF firmware with the following text on the screen (see attached screenshot): Boot Failed. EFI Floppy Boot Failed. EFI Floppy 1 Thus far I've only tested with a Xenial host, so I'm not sure whether this problem exists with a Yakkety host + Yakkety guest. This problem also doesn't seem to be the result of any changes in QEMU (and related) in Xenial. With a Xenial host, you can still do UEFI mode installs fine under QEMU when the guest is using the 16.04.1 ISOs, and likewise when the guest is using the latest Xenial daily (16.04.2 WIP) ISOs. So the problem seems to be only when using a Yakkety guest in UEFI mode. Note this problem effects both Yakkety desktop and server ISOs (when installing under QEMU in UEFI mode). Finally, on the off chance it might be helpful to anyone who comes across this bug report, I wrote a blog post a while back on how to use QEMU in UEFI mode on a Xenial (or newer) host: http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial- host-uefi-guest Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1624096/+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 1674938] Re: linux: 4.4.0-70.91 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 22. March 2017 19:03 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 24. March 2017 06:34 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 24. March 2017 06:34 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1674938 Title: linux: 4.4.0-70.91 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow security-signoff series: Confirmed Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1674939 derivatives: 1674940,1674941,1674944,1674945 -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674938/+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 1303508] Re: privacy settings: remove history datetimepicker not working
This bug was fixed in the package activity-log-manager - 0.9.7-0ubuntu25 --- activity-log-manager (0.9.7-0ubuntu25) zesty; urgency=medium * debian/patches/21_clear_history_calendars.patch: - Fix calendars not working when selecting date range to clear (LP: #1303508) -- Robert Ancell Fri, 24 Mar 2017 10:56:02 +1300 ** Changed in: activity-log-manager (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1303508 Title: privacy settings: remove history datetimepicker not working Status in Activity Log Manager: Fix Committed Status in activity-log-manager package in Ubuntu: Fix Released Status in activity-log-manager source package in Trusty: Fix Committed Status in activity-log-manager source package in Xenial: Fix Committed Status in activity-log-manager source package in Yakkety: Fix Committed Bug description: [Impact] User is unable to use calendar widgets when clearing history - they do not respond to mouse clicks. [Test Case] 1. Open System Settings. 2. Select "Security & Privacy" 3. Select "Files & Applications" tab 4. Select "Clear Usage Data..." 5. Click dropdown beside one of the date widgets Expected result: A calendar is shown and a date can be selected. Observed result: The calendar is shown, but is greyed out and doesn't respond to clicks. The calendar doesn't disappear until System Settings is closed. [Regression Potential] Low. Fix makes widgets work correctly with modal dialogs. Regressions are likely to be contained to these widgets which are not working correctly currently. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1303508/+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 1668583] Re: upgrade activity failing with "The following packages have unmet dependencies: lxd: Unknown dependency error"
This bug was fixed in the package landscape-client - 16.03-0ubuntu3 --- landscape-client (16.03-0ubuntu3) zesty; urgency=medium * Don't report packages that are coming from backports, so that Landscape doesn't try to upgrade to versions of packages that are in backports. (LP: #1668583) -- Bjorn Tillenius Mon, 20 Mar 2017 10:25:40 + ** Changed in: landscape-client (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/1668583 Title: upgrade activity failing with "The following packages have unmet dependencies: lxd: Unknown dependency error" Status in Landscape Client: Fix Committed Status in landscape-client package in Ubuntu: Fix Released Status in landscape-client source package in Trusty: Incomplete Status in landscape-client source package in Xenial: Incomplete Status in landscape-client source package in Yakkety: Incomplete Bug description: Hi, I have an upgrade activity that is failing with the following error message : The following packages have unmet dependencies: lxd: Unknown dependency error This is on xenial. [Impact] In a lot of cases, landscape-client can't update packages on xenial machines if lxd is installed. [Test case] Register a fresh xenial machine with landscape.canonical.com. (Install landscape-client and run 'sudo landscape-config'). After the registration is done, go to Landscape, accept the pending computer and wait for package information to sync. Without the fix, there should be an upgrade for lxd and lxd-client available to the version that is in xenial-backports. With the patch, there won't be any upgrade available. [Regression potnentials] Users won't be able to install packages from backports. This is OK, though, since Landscape doesn't support that officially. To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1668583/+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 1675163] Re: Don't attempt to create devices in LXC containers
This bug was fixed in the package makedev - 2.3.1-93ubuntu2 --- makedev (2.3.1-93ubuntu2) zesty; urgency=medium * Don't attempt to create /dev devices when inside a container. (LP: #1675163) -- Stéphane Graber Wed, 22 Mar 2017 16:38:22 -0400 ** Changed in: makedev (Ubuntu Zesty) 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/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Triaged Status in makedev source package in Trusty: Triaged Status in makedev source package in Xenial: Triaged Status in makedev source package in Yakkety: Triaged Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+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 1412548] Re: OCF Resource Agent "Filesystem" is still CMAN dependent
In 2013, resource-agents upstream changed their code: https://github.com/ClusterLabs/resource- agents/commit/8a0e21b4f25efd83b962bfe7195a80e608e708fd and then all of that code was then removed in upstream as being for SLES10 only... https://github.com/ClusterLabs/resource- agents/commit/a753a0fdfad2e439ad80d2c962ce1bce452f27a5 such that the patch in $description should not be necessary and does not appear to be apply to the code in 16.04. @beat-c can you provide the output of `apt policy resource-agents` which is what actually provides the file in question in this bug? I do not understand I agree that the upstream fix available in 16.04 might be worth backporting to 14.04 since that is before the code was removed (it seems). I would prefer we used that patch rather than the one in $description, functionally-equivalent but a backport rather than a diversion from upstream. ** Changed in: resource-agents (Ubuntu) Status: New => Triaged ** Also affects: ocfs2-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: resource-agents (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ocfs2-tools (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: resource-agents (Ubuntu Trusty) Importance: Undecided Status: New ** No longer affects: ocfs2-tools (Ubuntu Trusty) ** No longer affects: ocfs2-tools (Ubuntu Xenial) ** Changed in: ocfs2-tools (Ubuntu) Status: Confirmed => Invalid ** Changed in: resource-agents (Ubuntu Trusty) Status: New => Triaged ** Changed in: resource-agents (Ubuntu Xenial) Status: New => Incomplete ** Changed in: resource-agents (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1412548 Title: OCF Resource Agent "Filesystem" is still CMAN dependent Status in ocfs2-tools package in Ubuntu: Invalid Status in resource-agents package in Ubuntu: Invalid Status in resource-agents source package in Trusty: Triaged Status in resource-agents source package in Xenial: Incomplete Bug description: The script /usr/lib/ocf/resource.d/heartbeat/Filesystem is used as part of the pacemaker system to mount disks, especially those on shared filesystems. In the version of the script provided with 14.04, when the filesystem is of type "ocfs2", the script incorrectly checks that the HA_cluster_type is "cman". However is no longer used with 14.04. The script thus fails with the error ": ocfs2 is not compatible with your environment." The script should instead have checked to ensure that the HA_cluster_type is set to "corosync". The following patch needs to be applied to correct the error: --- Filesystem2013-12-16 07:41:25.0 + +++ Filesystem.new2015-01-19 19:01:30.181772112 + @@ -338,7 +338,7 @@ ocfs2_init() # not need this: OCFS2_SLES10="" - if [ "X$HA_cluster_type" = "Xcman" ]; then + if [ "X$HA_cluster_type" = "Xcorosync" ]; then return elif [ "X$HA_cluster_type" != "Xopenais" ]; then if grep -q "SUSE Linux Enterprise Server 10" /etc/SuSE-release >/dev/null 2>&1 ; then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/1412548/+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 1303508] Re: privacy settings: remove history datetimepicker not working
** Also affects: activity-log-manager (Ubuntu Trusty) 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/1303508 Title: privacy settings: remove history datetimepicker not working Status in Activity Log Manager: Fix Committed Status in activity-log-manager package in Ubuntu: Fix Committed Status in activity-log-manager source package in Trusty: New Status in activity-log-manager source package in Xenial: New Status in activity-log-manager source package in Yakkety: New Bug description: [Impact] User is unable to use calendar widgets when clearing history - they do not respond to mouse clicks. [Test Case] 1. Open System Settings. 2. Select "Security & Privacy" 3. Select "Files & Applications" tab 4. Select "Clear Usage Data..." 5. Click dropdown beside one of the date widgets Expected result: A calendar is shown and a date can be selected. Observed result: The calendar is shown, but is greyed out and doesn't respond to clicks. The calendar doesn't disappear until System Settings is closed. [Regression Potential] Low. Fix makes widgets work correctly with modal dialogs. Regressions are likely to be contained to these widgets which are not working correctly currently. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1303508/+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 1303508] Re: privacy settings: remove history datetimepicker not working
** Changed in: activity-log-manager (Ubuntu) Status: In Progress => Fix Committed ** Also affects: activity-log-manager (Ubuntu Yakkety) 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/1303508 Title: privacy settings: remove history datetimepicker not working Status in Activity Log Manager: Fix Committed Status in activity-log-manager package in Ubuntu: Fix Committed Status in activity-log-manager source package in Trusty: New Status in activity-log-manager source package in Xenial: New Status in activity-log-manager source package in Yakkety: New Bug description: [Impact] User is unable to use calendar widgets when clearing history - they do not respond to mouse clicks. [Test Case] 1. Open System Settings. 2. Select "Security & Privacy" 3. Select "Files & Applications" tab 4. Select "Clear Usage Data..." 5. Click dropdown beside one of the date widgets Expected result: A calendar is shown and a date can be selected. Observed result: The calendar is shown, but is greyed out and doesn't respond to clicks. The calendar doesn't disappear until System Settings is closed. [Regression Potential] Low. Fix makes widgets work correctly with modal dialogs. Regressions are likely to be contained to these widgets which are not working correctly currently. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1303508/+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 1594740] Re: Supervisor not enabled or started in Ubuntu 16.04 after installation
This bug was fixed in the package supervisor - 3.2.0-2ubuntu0.1 --- supervisor (3.2.0-2ubuntu0.1) xenial; urgency=medium * Enable and start systemd service. Thanks to Orestis Ioannou . (Closes LP: #1594740). -- Nishanth Aravamudan Fri, 10 Mar 2017 10:43:23 -0800 ** Changed in: supervisor (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/1594740 Title: Supervisor not enabled or started in Ubuntu 16.04 after installation Status in supervisor package in Ubuntu: Fix Released Status in supervisor source package in Xenial: Fix Released Status in supervisor source package in Yakkety: Fix Released Bug description: [Impact] * In all prior releases to 16.04, `apt-get install supervisor` would result in supervisor being started after package installation (and configured to start by default at boot). This is the principle of least surprise in action and reflects Ubuntu's ease of use. * Due to the timing of 16.04, the version from Debian was broken to not support systemd properly. * Both Debian and Ubuntu have been fixed since the version in 16.04, in the same way as the proposed fix. [Test Case] * Install supervisor. After installation, the service should be running and should be enabled. [Regression Potential] * As the behavior is currently regressed relative to 14.04, I believe the primary potential source of regressions will be users who have manually fixed-up systemd to do what was expected on their systems. I believe dpkg will notice the differences, if any, between the system- installed supervisor systemd files and those in this package. --- Expected behavior = In Ubuntu 10.04, 12.04 and 14.04 after running "apt-get install supervisor" the Supervisor daemon is automatically enabled (to start on boot) and started (so that Supervisor is running by the time apt- get returns). What actually happens = In Ubuntu 16.04 the Supervisor daemon is not automatically enabled nor is it started during installation. This breaks compatibility with previous and expected behavior. Why this is a problem = I've built dozens of tools that use Supervisor for process supervision and these tools are deployed using custom Debian packages. Each of these packages has a dependency on the supervisor package with the expectation that Supervisor will be installed, enabled and started so that my post-installation scripts can call "supervisorctl" and expect it to work (instead of complaining about a missing UNIX socket file and exiting with a nonzero status code, thereby breaking my automated server provisioning). Known workaround Create a shim package with a dependency on supervisor and a post- installation script that runs the following commands: # On Ubuntu 16.04 the installation of Supervisor does not # enable and start the Supervisor daemon which breaks # compatibility with previous Ubuntu releases. if [ $(lsb_release --short --codename) = xenial ]; then # Make sure the daemon is enabled. if ! systemctl --quiet is-enabled supervisor; then systemctl enable supervisor fi # Make sure the daemon is started. if ! systemctl --quiet is-active supervisor; then systemctl start supervisor fi fi Alternatively one can obviously just run these commands by hand to rectify the situation. It's kind of nasty that I have to create a shim package like this to compensate for a break in backwards compatibility that is -as far as I know- undocumented and most likely unintentional. What's more is that a lot of people will lack the means to create shim packages like this, so thousands of Ubuntu users / integrators / system administrators worldwide will need to repeat these shenanigans manually. Affected versions = peter@template-xenial:~$ lsb_release --short --description Ubuntu 16.04 LTS peter@template-xenial:~$ apt-cache policy supervisor supervisor: Installed: 3.2.0-2 Candidate: 3.2.0-2 Version table: *** 3.2.0-2 500 500 http://mirror.nl.leaseweb.net/ubuntu xenial/universe amd64 Packages 500 http://mirror.nl.leaseweb.net/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status Root cause analysis === In Ubuntu 16.04 Supervisor is managed by systemd however the post- installation script is using update-rc.d and invoke-rc.d to enable and start Supervisor. As far as I know these commands are remnants of the old daemon management infrastructure and they don't integrate wi
[Group.of.nepali.translators] [Bug 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)
This bug was fixed in the package ltt-control - 2.8.1-1ubuntu1 --- ltt-control (2.8.1-1ubuntu1) yakkety; urgency=medium * Fix lttng list --kernel --syscall failure (LP: #1671063) -- Colin Ian King Tue, 14 Mar 2017 13:39:11 + ** Changed in: ltt-control (Ubuntu Yakkety) 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/1671063 Title: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM) Status in ltt-control package in Ubuntu: Fix Released Status in ltt-control source package in Xenial: Fix Released Status in ltt-control source package in Yakkety: Fix Released Bug description: == SRU Request [Xenial, Yaketty + Zesty ] == Without this minor fix, the lttng tool receives a "Not enough memory" error when in fact this is not the case. == How to reproduce == lttng list --kernel --sysall produces: Error: Unable to list system calls: Not enough memory Error: Command error With the fix, this does not occur. == Fix == https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html == Regression Potential == Minimal, low risk. Two test cases failed on this arch: == lttng smoke test list kernel events == PASSED (lttng list --kernel) Error: Unable to list system calls: Not enough memory Error: Command error FAILED (lttng list --kernel --syscall) FAILED (lttng list --kernel --syscall more output expected) == lttng smoke test trace open/close system calls == ... FAILED (did not trace any open system calls) Please find attachment for complete log. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-40-generic 4.8.0-40.43 ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17 Uname: Linux 4.8.0-40-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Mar 8 06:39:24 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.8.0-40-generic N/A linux-backports-modules-4.8.0-40-generic N/A linux-firmware1.161.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltt-control/+bug/1671063/+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 1671063] Re: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM)
This bug was fixed in the package ltt-control - 2.7.1-2ubuntu1 --- ltt-control (2.7.1-2ubuntu1) xenial; urgency=medium * Fix lttng list --kernel --syscall failure (LP: #1671063) -- Colin Ian King Tue, 14 Mar 2017 13:39:11 + ** Changed in: ltt-control (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/1671063 Title: ubuntu_lttng_smoke_test failed on Yakkety s390x (zVM) Status in ltt-control package in Ubuntu: Fix Released Status in ltt-control source package in Xenial: Fix Released Status in ltt-control source package in Yakkety: Fix Released Bug description: == SRU Request [Xenial, Yaketty + Zesty ] == Without this minor fix, the lttng tool receives a "Not enough memory" error when in fact this is not the case. == How to reproduce == lttng list --kernel --sysall produces: Error: Unable to list system calls: Not enough memory Error: Command error With the fix, this does not occur. == Fix == https://lists.lttng.org/pipermail/lttng-dev/2017-March/026959.html == Regression Potential == Minimal, low risk. Two test cases failed on this arch: == lttng smoke test list kernel events == PASSED (lttng list --kernel) Error: Unable to list system calls: Not enough memory Error: Command error FAILED (lttng list --kernel --syscall) FAILED (lttng list --kernel --syscall more output expected) == lttng smoke test trace open/close system calls == ... FAILED (did not trace any open system calls) Please find attachment for complete log. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-40-generic 4.8.0-40.43 ProcVersionSignature: Ubuntu 4.8.0-40.43-generic 4.8.17 Uname: Linux 4.8.0-40-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Mar 8 06:39:24 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M debug udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.8.0-40-generic N/A linux-backports-modules-4.8.0-40-generic N/A linux-firmware1.161.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltt-control/+bug/1671063/+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 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts
This bug was fixed in the package xen - 4.6.5-0ubuntu1 --- xen (4.6.5-0ubuntu1) xenial; urgency=medium * Rebasing to upstream stable release 4.6.5 (LP: #1671864) https://www.xenproject.org/downloads/xen-archives/xen-46-series.html - Includes fix for booting 4.10 Linux kernels in HVM guests on Intel hosts which support the TSC_ADJUST MSR (LP: #1671760) - Additional security relevant changes: * CVE-2013-2076 / XSA-052 (update) - Information leak on XSAVE/XRSTOR capable AMD CPUs * CVE-2016-7093 / XSA-186 (4.6.3 became vulnerable) - x86: Mishandling of instruction pointer truncation during emulation * XSA-207 - memory leak when destroying guest without PT devices - Replacing the following security fixes with the versions from the stable update: * CVE-2015-7812 / XSA-145 - arm: Host crash when preempting a multicall * CVE-2015-7813 / XSA-146 - arm: various unimplemented hypercalls log without rate limiting * CVE-2015-7814 / XSA-147 - arm: Race between domain destruction and memory allocation decrease * CVE-2015-7835 / XSA-148 - x86: Uncontrolled creation of large page mappings by PV guests * CVE-2015-7969 / XSA-149, XSA-151 - leak of main per-domain vcpu pointer array - x86: leak of per-domain profiling-related vcpu pointer array * CVE-2015-7970 / XSA-150 - x86: Long latency populate-on-demand operation is not preemptible * CVE-2015-7971 / XSA-152 - x86: some pmu and profiling hypercalls log without rate limiting * CVE-2015-7972 / XSA-153 - x86: populate-on-demand balloon size inaccuracy can crash guests * CVE-2016-2270 / XSA-154 - x86: inconsistent cachability flags on guest mappings * CVE-2015-8550 / XSA-155 - paravirtualized drivers incautious about shared memory contents * CVE-2015-5307, CVE-2015-8104 / XSA-156 - x86: CPU lockup during exception delivery * CVE-2015-8338 / XSA-158 - long running memory operations on ARM * CVE-2015-8339, CVE-2015-8340 / XSA-159 XENMEM_exchange error handling issues * CVE-2015-8341 / XSA-160 - libxl leak of pv kernel and initrd on error * CVE-2015-8555 / XSA-165 - information leak in legacy x86 FPU/XMM initialization * XSA-166 - ioreq handling possibly susceptible to multiple read issue * CVE-2016-1570 / XSA-167 - PV superpage functionality missing sanity checks * CVE-2016-1571 / XSA-168 - VMX: intercept issue with INVLPG on non-canonical address * CVE-2015-8615 / XSA-169 - x86: unintentional logging upon guest changing callback method * CVE-2016-2271 / XSA-170 - VMX: guest user mode may crash guest with non-canonical RIP * CVE-2016-3158, CVE-2016-3159 / XSA-172 - broken AMD FPU FIP/FDP/FOP leak workaround * CVE-2016-3960 / XSA-173 - x86 shadow pagetables: address width overflow * CVE-2016-4962 / XSA-175 - Unsanitised guest input in libxl device handling code * CVE-2016-4480 / XSA-176 - x86 software guest page walk PS bit handling flaw * CVE-2016-4963 / XSA-178 - Unsanitised driver domain input in libxl device handling * CVE-2016-5242 / XSA-181 - arm: Host crash caused by VMID exhaustion * CVE-2016-6258 / XSA-182 - x86: Privilege escalation in PV guests * CVE-2016-6259 / XSA-183 - x86: Missing SMAP whitelisting in 32-bit exception / event delivery * CVE-2016-7092 / XSA-185 - x86: Disallow L3 recursive pagetable for 32-bit PV guests * CVE-2016-7094 / XSA-187 - x86 HVM: Overflow of sh_ctxt->seg_reg[] * CVE-2016- / XSA-190 - CR0.TS and CR0.EM not always honored for x86 HVM guests * CVE-2016-9386 / XSA-191 - x86 null segments not always treated as unusable * CVE-2016-9382 / XSA-192 - x86 task switch to VM86 mode mis-handled * CVE-2016-9385 / XSA-193 - x86 segment base write emulation lacking canonical address checks * CVE-2016-9383 / XSA-195 - x86 64-bit bit test instruction emulation broken * CVE-2016-9377, CVE-2016-9378 / XSA-196 - x86 software interrupt injection mis-handled * CVE-2016-9379, CVE-2016-9380 / XSA-198 - delimiter injection vulnerabilities in pygrub * CVE-2016-9932 / XSA-200 - x86 CMPXCHG8B emulation fails to ignore operand size override * CVE-2016-9815, CVE-2016-9816, CVE-2016-9817, CVE-2016-9818 / XSA-201 - ARM guests may induce host asynchronous abort * CVE-2016-10024 / XSA-202 - x86 PV guests may be able to mask interrupts * CVE-2016-10025 / XSA-203 - x86: missing NULL pointer check in VMFUNC emulation * CVE-2016-10013 / XSA-204 - x86: Mishandling of SYSCALL singlestep during emulation
[Group.of.nepali.translators] [Bug 1671864] Re: Xen stable update to 4.6.5
This bug was fixed in the package xen - 4.6.5-0ubuntu1 --- xen (4.6.5-0ubuntu1) xenial; urgency=medium * Rebasing to upstream stable release 4.6.5 (LP: #1671864) https://www.xenproject.org/downloads/xen-archives/xen-46-series.html - Includes fix for booting 4.10 Linux kernels in HVM guests on Intel hosts which support the TSC_ADJUST MSR (LP: #1671760) - Additional security relevant changes: * CVE-2013-2076 / XSA-052 (update) - Information leak on XSAVE/XRSTOR capable AMD CPUs * CVE-2016-7093 / XSA-186 (4.6.3 became vulnerable) - x86: Mishandling of instruction pointer truncation during emulation * XSA-207 - memory leak when destroying guest without PT devices - Replacing the following security fixes with the versions from the stable update: * CVE-2015-7812 / XSA-145 - arm: Host crash when preempting a multicall * CVE-2015-7813 / XSA-146 - arm: various unimplemented hypercalls log without rate limiting * CVE-2015-7814 / XSA-147 - arm: Race between domain destruction and memory allocation decrease * CVE-2015-7835 / XSA-148 - x86: Uncontrolled creation of large page mappings by PV guests * CVE-2015-7969 / XSA-149, XSA-151 - leak of main per-domain vcpu pointer array - x86: leak of per-domain profiling-related vcpu pointer array * CVE-2015-7970 / XSA-150 - x86: Long latency populate-on-demand operation is not preemptible * CVE-2015-7971 / XSA-152 - x86: some pmu and profiling hypercalls log without rate limiting * CVE-2015-7972 / XSA-153 - x86: populate-on-demand balloon size inaccuracy can crash guests * CVE-2016-2270 / XSA-154 - x86: inconsistent cachability flags on guest mappings * CVE-2015-8550 / XSA-155 - paravirtualized drivers incautious about shared memory contents * CVE-2015-5307, CVE-2015-8104 / XSA-156 - x86: CPU lockup during exception delivery * CVE-2015-8338 / XSA-158 - long running memory operations on ARM * CVE-2015-8339, CVE-2015-8340 / XSA-159 XENMEM_exchange error handling issues * CVE-2015-8341 / XSA-160 - libxl leak of pv kernel and initrd on error * CVE-2015-8555 / XSA-165 - information leak in legacy x86 FPU/XMM initialization * XSA-166 - ioreq handling possibly susceptible to multiple read issue * CVE-2016-1570 / XSA-167 - PV superpage functionality missing sanity checks * CVE-2016-1571 / XSA-168 - VMX: intercept issue with INVLPG on non-canonical address * CVE-2015-8615 / XSA-169 - x86: unintentional logging upon guest changing callback method * CVE-2016-2271 / XSA-170 - VMX: guest user mode may crash guest with non-canonical RIP * CVE-2016-3158, CVE-2016-3159 / XSA-172 - broken AMD FPU FIP/FDP/FOP leak workaround * CVE-2016-3960 / XSA-173 - x86 shadow pagetables: address width overflow * CVE-2016-4962 / XSA-175 - Unsanitised guest input in libxl device handling code * CVE-2016-4480 / XSA-176 - x86 software guest page walk PS bit handling flaw * CVE-2016-4963 / XSA-178 - Unsanitised driver domain input in libxl device handling * CVE-2016-5242 / XSA-181 - arm: Host crash caused by VMID exhaustion * CVE-2016-6258 / XSA-182 - x86: Privilege escalation in PV guests * CVE-2016-6259 / XSA-183 - x86: Missing SMAP whitelisting in 32-bit exception / event delivery * CVE-2016-7092 / XSA-185 - x86: Disallow L3 recursive pagetable for 32-bit PV guests * CVE-2016-7094 / XSA-187 - x86 HVM: Overflow of sh_ctxt->seg_reg[] * CVE-2016- / XSA-190 - CR0.TS and CR0.EM not always honored for x86 HVM guests * CVE-2016-9386 / XSA-191 - x86 null segments not always treated as unusable * CVE-2016-9382 / XSA-192 - x86 task switch to VM86 mode mis-handled * CVE-2016-9385 / XSA-193 - x86 segment base write emulation lacking canonical address checks * CVE-2016-9383 / XSA-195 - x86 64-bit bit test instruction emulation broken * CVE-2016-9377, CVE-2016-9378 / XSA-196 - x86 software interrupt injection mis-handled * CVE-2016-9379, CVE-2016-9380 / XSA-198 - delimiter injection vulnerabilities in pygrub * CVE-2016-9932 / XSA-200 - x86 CMPXCHG8B emulation fails to ignore operand size override * CVE-2016-9815, CVE-2016-9816, CVE-2016-9817, CVE-2016-9818 / XSA-201 - ARM guests may induce host asynchronous abort * CVE-2016-10024 / XSA-202 - x86 PV guests may be able to mask interrupts * CVE-2016-10025 / XSA-203 - x86: missing NULL pointer check in VMFUNC emulation * CVE-2016-10013 / XSA-204 - x86: Mishandling of SYSCALL singlestep during emulation
[Group.of.nepali.translators] [Bug 1671760] Re: Xen HVM guests running linux 4.10 fail to boot on Intel hosts
This bug was fixed in the package xen - 4.4.2-0ubuntu0.14.04.10 --- xen (4.4.2-0ubuntu0.14.04.10) trusty; urgency=medium * Backport upstream change to fix TSC_ADJUST MSR handling in HVM guests running on Intel based hosts (LP: #1671760) -- Stefan Bader Tue, 14 Mar 2017 11:17:48 +0100 ** Changed in: xen (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/1671760 Title: Xen HVM guests running linux 4.10 fail to boot on Intel hosts Status in linux package in Ubuntu: Won't Fix Status in xen package in Ubuntu: Fix Released Status in linux source package in Trusty: Invalid Status in xen source package in Trusty: Fix Released Status in linux source package in Xenial: Invalid Status in xen source package in Xenial: Fix Released Status in linux source package in Yakkety: Invalid Status in xen source package in Yakkety: Fix Released Status in linux source package in Zesty: Won't Fix Status in xen source package in Zesty: Fix Released Bug description: Starting with Linux kernel 4.10, the kernel does some sanity checking on the TSC_ADJUST MSR. Xen has implemented some support for that MSR in the hypervisor (Xen 4.3 and later) for HVM guests. But boot and secondary vCPUs are set up inconsistently. This causes the boot of a 4.10 HVM guest to hang early on boot. This was fixed in the hypervisor by: commit 98297f09bd07bb63407909aae1d309d8adeb572e x86/hvm: do not set msr_tsc_adjust on hvm_set_guest_tsc_fixed That fix would be contained in 4.6.5 and 4.7.2 and would be in 4.8.1 (not released, yet) which mean that Ubuntu 14.04/16.04/16.10 and 17.04 currently are affected. --- SRU Justification: Impact: Without the TSC_ADJUST MSR fix, 4.10 and later kernels will get stuck at boot when running as (PV)HVM guests on Xen 4.3 and later. Fix: Above fix either individually applied or as part of Xen stable stream (for Xen 4.7.x and 4.6.x) resolves the issue. Testcase: - Requires Intel based host which supports the TSC_ADJUST MSR - Configured as Xen host - HVM guest running Zesty/17.04 - Stuck at boot before, normal booting OS after To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671760/+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 1303508] Re: privacy settings: remove history datetimepicker not working
** Description changed: - Setting a custom date is not possible because datetimepicker does not - react on input. + [Impact] + User is unable to use calendar widgets when clearing history - they do not respond to mouse clicks. + + [Test Case] + 1. Open System Settings. + 2. Select "Security & Privacy" + 3. Select "Files & Applications" tab + 4. Select "Clear Usage Data..." + 5. Click dropdown beside one of the date widgets + + Expected result: + A calendar is shown and a date can be selected. + + Observed result: + The calendar is shown, but is greyed out and doesn't respond to clicks. The calendar doesn't disappear until System Settings is closed. + + [Regression Potential] + Low. Fix makes widgets work correctly with modal dialogs. Regressions are likely to be contained to these widgets which are not working correctly currently. ** Also affects: activity-log-manager (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/1303508 Title: privacy settings: remove history datetimepicker not working Status in Activity Log Manager: Fix Committed Status in activity-log-manager package in Ubuntu: In Progress Status in activity-log-manager source package in Xenial: New Bug description: [Impact] User is unable to use calendar widgets when clearing history - they do not respond to mouse clicks. [Test Case] 1. Open System Settings. 2. Select "Security & Privacy" 3. Select "Files & Applications" tab 4. Select "Clear Usage Data..." 5. Click dropdown beside one of the date widgets Expected result: A calendar is shown and a date can be selected. Observed result: The calendar is shown, but is greyed out and doesn't respond to clicks. The calendar doesn't disappear until System Settings is closed. [Regression Potential] Low. Fix makes widgets work correctly with modal dialogs. Regressions are likely to be contained to these widgets which are not working correctly currently. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/1303508/+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 1674748] Re: Intel 8265 does not work with 16.04 linux-firmware 1.157.8
** Also affects: linux-firmware (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-firmware (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-firmware (Ubuntu Yakkety) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Yakkety) Assignee: (unassigned) => Seth Forshee (sforshee) ** Changed in: linux-firmware (Ubuntu Yakkety) Importance: Undecided => Medium ** Description changed: + SRU Justification + + Impact: The current iwlwifi firmware lacks support for Intel 8265 + wireless. + + Fix: An updated version of the -22 ucode includes support for this + hardware. + + Regression Potential: There were some regressions with earlier versions + of the -22 ucode, but testing the most recent update found that these + have been fixed. No additional regressions were found in testing. + + --- + Using the Intel wireless firmware from 1.161.1 should fix this issue -- 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/1674748 Title: Intel 8265 does not work with 16.04 linux-firmware 1.157.8 Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Xenial: In Progress Status in linux-firmware source package in Yakkety: In Progress Bug description: SRU Justification Impact: The current iwlwifi firmware lacks support for Intel 8265 wireless. Fix: An updated version of the -22 ucode includes support for this hardware. Regression Potential: There were some regressions with earlier versions of the -22 ucode, but testing the most recent update found that these have been fixed. No additional regressions were found in testing. --- Using the Intel wireless firmware from 1.161.1 should fix this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1674748/+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 1668093] Re: ssh-keygen -H corrupts already hashed entries
This bug was fixed in the package openssh - 1:7.4p1-9
---
openssh (1:7.4p1-9) unstable; urgency=medium
* Fix null pointer dereference in ssh-keygen; this fixes an autopkgtest
regression introduced in 1:7.4p1-8.
-- Colin Watson Thu, 16 Mar 2017 13:43:15 +
** Changed in: openssh (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1668093
Title:
ssh-keygen -H corrupts already hashed entries
Status in openssh package in Ubuntu:
Fix Released
Status in openssh source package in Xenial:
Triaged
Status in openssh source package in Yakkety:
Triaged
Status in openssh package in Debian:
Fix Released
Bug description:
[Impact]
* re-execution of ssh-keygen -H can clobber known-hosts
* Due to that users might get spurious re-warnings of known systems. For
Automation it might be worse as it might stop to work when re-executed.
* This is a regression from Trusty (working) to Xenial (fail) upgrade
due to an upstream bug in the versions we merged.
* This is a backport of the upstream fix
[Test Case]
* Pick a Host IP to scan keys from that you can reach and replies with SSH,
then run the following trivial loop:
$ ssh-keyscan ${IP} > ~/.ssh/known_hosts; for i in $(seq 1 20); do
ssh-keygen -H; diff -Naur ~/.ssh/known_hosts.old ~/.ssh/known_hosts; done
* Expected: no diff reported, since already hashed entries should be left
as-is
* Without fix: - diff in the hashes
[Regression Potential]
* The fix is upstream and soon in Debian as well, so we are not
custom diverting here.
* The risk should be minimal as this only changes ssh-keygen so
despite openssh being really critical this doesn't affect ssh itself
at all.
[Other Info]
* n/a
---
xenial @ 1:7.2p2-4ubuntu2.1 on amd64 has this bug. trusty @
1:6.6p1-2ubuntu2.8 on amd64 does not have this bug. I have not tested
any other ssh versions.
The following should reproduce the issue:
#ssh-keyscan > ~/.ssh/known_hosts
# ssh root@X
Permission denied (publickey).
# ssh-keygen -H
/root/.ssh/known_hosts updated.
Original contents retained as /root/.ssh/known_hosts.old
WARNING: /root/.ssh/known_hosts.old contains unhashed entries
Delete this file to ensure privacy of hostnames
# ssh root@XX
Permission denied (publickey).
# ssh-keygen -H
/root/.ssh/known_hosts updated.
Original contents retained as /root/.ssh/known_hosts.old
WARNING: /root/.ssh/known_hosts.old contains unhashed entries
Delete this file to ensure privacy of hostnames
# ssh root@X
The authenticity of host 'XX' can't be established.
RSA key fingerprint is XX.
Are you sure you want to continue connecting (yes/no)?
# diff known_hosts.old known_hosts
1c1
< |1|BoAbRpUE3F5AzyprJcbjdepeDh8=|x/1AcaLxh45FlShmVQnlgx2qjxY= X
---
> |1|nTPsoLxCugQyZi3pqOa2pc/cX64=|bUH5qwZlZPp8msMGHdLtslf3Huk= X
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1668093/+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 1562002] Re: Nautilus: lag after choosing action in top right menu
** Bug watch added: GNOME Bug Tracker #769287 https://bugzilla.gnome.org/show_bug.cgi?id=769287 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=769287 Importance: Unknown Status: Unknown -- 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/1562002 Title: Nautilus: lag after choosing action in top right menu Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: Confirmed Bug description: # Impact This is known to affect Nautilus, but can potentially affect other applications too (the upstream bug has an example test app attached). See also the duplicate bug 1644393, which is another appearance of the same bug but with other symptoms. # Proposed Fix The proposed fix is an upstream commit taken from gtk-3-20 branch: https://git.gnome.org/browse/gtk+/commit/?id=10c3a2483635d1c1 # Test Case https://bugzilla.gnome.org/show_bug.cgi?id=769287#c0 has a test case. # Regression Potential The bug is fixed in GTK+ 3.20.9, so the fix was already present in the version that shipped with Yakkety. I am not aware of any regressions. - choosing action like New Tab, New Folder, Select Items Matching, will make nautilus lag (unresponsive) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 25 20:52:21 2016 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+685+36'" InstallationDate: Installed on 2016-03-24 (1 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1562002/+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 1637223] Re: Update to newer version of docker-compose >= 1.6
** Description changed: [Impact] Ubuntu 16.04.1 does not contain latest docker-compose release needed to handle v2 yml files. As minimum level 1.6 has to be integrated. [Test case] Follow the instructions at https://docs.docker.com/compose/gettingstarted/#step-4-build-and-run-your-app-with-compose, installing docker and docker-compose from the packages. [Regression potential] - TBD. + Docker compose is currently broken in Xenial (because docker is too new) so it can't get much worse. dockerpty and python-docker have no reverse-depends and so updating them is of low risk. (possibly these packages should be considered part of the "docker group" per https://wiki.ubuntu.com/DockerUpdates ?) ** Changed in: dockerpty (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1637223 Title: Update to newer version of docker-compose >= 1.6 Status in Ubuntu on IBM z Systems: In Progress Status in docker-compose package in Ubuntu: Invalid Status in dockerpty package in Ubuntu: Invalid Status in python-docker package in Ubuntu: Invalid Status in docker-compose source package in Xenial: In Progress Status in dockerpty source package in Xenial: In Progress Status in python-docker source package in Xenial: In Progress Status in docker-compose source package in Yakkety: In Progress Status in python-docker source package in Yakkety: In Progress Bug description: [Impact] Ubuntu 16.04.1 does not contain latest docker-compose release needed to handle v2 yml files. As minimum level 1.6 has to be integrated. [Test case] Follow the instructions at https://docs.docker.com/compose/gettingstarted/#step-4-build-and-run-your-app-with-compose, installing docker and docker-compose from the packages. [Regression potential] Docker compose is currently broken in Xenial (because docker is too new) so it can't get much worse. dockerpty and python-docker have no reverse-depends and so updating them is of low risk. (possibly these packages should be considered part of the "docker group" per https://wiki.ubuntu.com/DockerUpdates ?) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1637223/+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 1637290] Re: Update to the signed 0.9+1474479173.6c180c6-0ubuntu1 shim binary from Microsoft
This bug was fixed in the package livecd-rootfs - 2.435.1 --- livecd-rootfs (2.435.1) yakkety; urgency=medium [ Robert C Jennings ] * ubuntu-cpc: Remove redundant copy of grub files. (LP: #1637290) -- Mathieu Trudel-Lapierre Thu, 17 Nov 2016 16:13:28 -0500 ** Changed in: livecd-rootfs (Ubuntu Yakkety) 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/1637290 Title: Update to the signed 0.9+1474479173.6c180c6-0ubuntu1 shim binary from Microsoft Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in grub2 source package in Precise: New Status in grub2-signed source package in Precise: New Status in livecd-rootfs source package in Precise: Invalid Status in shim source package in Precise: New Status in shim-signed source package in Precise: New Status in grub2 source package in Trusty: Fix Committed Status in grub2-signed source package in Trusty: Fix Committed Status in livecd-rootfs source package in Trusty: Invalid Status in shim source package in Trusty: New Status in shim-signed source package in Trusty: Fix Committed Status in grub2 source package in Xenial: Fix Committed Status in grub2-signed source package in Xenial: Fix Committed Status in livecd-rootfs source package in Xenial: Fix Committed Status in shim source package in Xenial: New Status in shim-signed source package in Xenial: Fix Committed Status in grub2 source package in Yakkety: Fix Committed Status in grub2-signed source package in Yakkety: Fix Committed Status in livecd-rootfs source package in Yakkety: Fix Released Status in shim source package in Yakkety: New Status in shim-signed source package in Yakkety: Fix Committed Bug description: [Impact] We might want to boot securely one of these days. [Test case] 1) Upgrading - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Verify that the new shimx64.efi file is under /boot/efi/EFI/ubuntu, along with mmx64.efi and fbx64.efi. - Verify that /boot/efi/EFI/ubuntu/MokManager.efi no longer exists. - Verify that trying to apt install grub alone, or apt install shim alone, pulls in the correct matching versions of packages and gives the same results. 2) Booting normally - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system, with Secure Boot enabled. - Verify it boots successfully to the login prompt. - There should be no messages about "Verification failure" or other errors before the kernel is loaded. 3) Network boot. - Update to shim signed and grub2 signed EFI binaries on the TFTP server used. - Verify that a network booting system still boots normally through shim and grub, reaching a login prompt. 4) BootEntry options - Update to new shim, shim-signed, grub2, grub2-signed on an UEFI system. - Update or install fwupdate. - Verify that new updates can be applied via fwupdate, that when an update is available, fwupdate will correctly start, apply the update, and reboot to shim normally, leading to a working system. 5) live builds - confirm that the new version of livecd-rootfs has been published to -updates first, and that a daily build of the UEFI-enabled cloud images succeeds with the new shim filenames. [Regression Potential] Any failure to load the kernel from grub, or for shim to load grub, or for the system firmware to load shim (such as "Verification failure" messages) or failure to retrieve or parse BootEntry extended options (such as necessary to load MokManager or fwupdate) should be considered regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1637290/+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 1675369] Re: Metacity Not Sending ConfigureNotify events
** Description changed: - When using seamless applications such as Rdesktop, the window manager - needs to send ConfigureNotify events. This is specified in ICCCM - section 4.1.5. Without it, software will hang and wait for a response. + # Impact + When using seamless applications such as Rdesktop, the window manager needs to send ConfigureNotify events. This is specified in ICCCM section 4.1.5. Without it, software will hang and wait for a response. + This greatly impacts corporate and enterprise users that are trying to + integrate Microsoft Windows applications using Rdesktop. + + # Proposed Fix A patch has been created here and should be merged: https://git.gnome.org/browse/metacity/commit/?h=gnome-3-24&id=f09967fc0f1d65fc7b5057b362b9657154a86079 - I have hand tested this patch on GNOME 3.18 on 16.04 LTS and it works. - We are requesting this to be merged. This greatly impacts corporate and - enterprise users that are trying to integrate Microsoft Windows - applications using Rdesktop. + # Test Case + Use Rdesktop in seamless mode for a while. + + # Regression Potential + The reporter has verified the fix, and it works. It has also been in Zesty since Mar 20th and so far nobody complained. ** Also affects: metacity (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: metacity (Ubuntu Yakkety) Importance: Undecided Status: New ** Changed in: metacity (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/1675369 Title: Metacity Not Sending ConfigureNotify events Status in metacity package in Ubuntu: Fix Released Status in metacity source package in Xenial: New Status in metacity source package in Yakkety: New Bug description: # Impact When using seamless applications such as Rdesktop, the window manager needs to send ConfigureNotify events. This is specified in ICCCM section 4.1.5. Without it, software will hang and wait for a response. This greatly impacts corporate and enterprise users that are trying to integrate Microsoft Windows applications using Rdesktop. # Proposed Fix A patch has been created here and should be merged: https://git.gnome.org/browse/metacity/commit/?h=gnome-3-24&id=f09967fc0f1d65fc7b5057b362b9657154a86079 # Test Case Use Rdesktop in seamless mode for a while. # Regression Potential The reporter has verified the fix, and it works. It has also been in Zesty since Mar 20th and so far nobody complained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1675369/+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 1672755] Re: SRU 1.0 tracking bug
This bug was fixed in the package ubuntu-image - 1.0+16.10ubuntu1 --- ubuntu-image (1.0+16.10ubuntu1) yakkety; urgency=medium * SRU tracking number LP: #1672755 * Exit with a console message instead of crashing when the contents of a partition does not fit within the specified size. (LP:1666580) * Don't install an unusable global flake8 extension. (LP:1631156) * Fix the autopkgtests to use --output-dir instead of the obsolete --output command line switch. (LP:1667140) * Added ``--image-file-list`` command line argument to record the paths of all the disk image files written. * Added an autopkgtest to prove that generated images can be successfully booted (on amd64 only). (LP:1625732) * Add an autopkgtest for ensuring each PR has a changelog entry and a bug linked to it. (LP:1655671) * Make ubuntu-image a classic confinement snap. (LP:1638645) -- Barry Warsaw Wed, 22 Feb 2017 11:30:01 -0500 ** Changed in: ubuntu-image (Ubuntu Yakkety) 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/1672755 Title: SRU 1.0 tracking bug Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Fix Released Bug description: New SRU tracking bug (with exception) for ubuntu-image 1.0 in Yakkety and Xenial. See https://wiki.ubuntu.com/UbuntuImageUpdates [Impact] ubuntu-image 1.0 fixes some bugs and pays down some technical debt. It represents the final gold release for the Zesty cycle, SRU'd back into X and Y. This release fixes some bogus warnings on the size of the mbr partition, it reverts an archive-wide global breakage for flake8, and it adds a new command line option --image-file-list. The snap version is now classic confinement. [Test Case] Create an image using the official amd64 model assertion. Ensure that the resulting image boots to 'press enter to configure' phase. [Regression Potential] * ubuntu-image may not produce a bootable image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1672755/+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 1672755] Re: SRU 1.0 tracking bug
This bug was fixed in the package ubuntu-image - 1.0+16.04ubuntu1 --- ubuntu-image (1.0+16.04ubuntu1) xenial; urgency=medium * SRU tracking number LP: #1672755 * Exit with a console message instead of crashing when the contents of a partition does not fit within the specified size. (LP:1666580) * Don't install an unusable global flake8 extension. (LP:1631156) * Fix the autopkgtests to use --output-dir instead of the obsolete --output command line switch. (LP:1667140) * Added ``--image-file-list`` command line argument to record the paths of all the disk image files written. * Added an autopkgtest to prove that generated images can be successfully booted (on amd64 only). (LP:1625732) * Add an autopkgtest for ensuring each PR has a changelog entry and a bug linked to it. (LP:1655671) * Make ubuntu-image a classic confinement snap. (LP:1638645) -- Barry Warsaw Wed, 22 Feb 2017 11:30:01 -0500 ** Changed in: ubuntu-image (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/1672755 Title: SRU 1.0 tracking bug Status in ubuntu-image package in Ubuntu: Fix Released Status in ubuntu-image source package in Xenial: Fix Released Status in ubuntu-image source package in Yakkety: Fix Released Bug description: New SRU tracking bug (with exception) for ubuntu-image 1.0 in Yakkety and Xenial. See https://wiki.ubuntu.com/UbuntuImageUpdates [Impact] ubuntu-image 1.0 fixes some bugs and pays down some technical debt. It represents the final gold release for the Zesty cycle, SRU'd back into X and Y. This release fixes some bogus warnings on the size of the mbr partition, it reverts an archive-wide global breakage for flake8, and it adds a new command line option --image-file-list. The snap version is now classic confinement. [Test Case] Create an image using the official amd64 model assertion. Ensure that the resulting image boots to 'press enter to configure' phase. [Regression Potential] * ubuntu-image may not produce a bootable image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1672755/+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 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE
This bug was fixed in the package zfs-linux - 0.6.5.8-0ubuntu4.2
---
zfs-linux (0.6.5.8-0ubuntu4.2) yakkety; urgency=low
* Enable zfs to respect RSIZE_LIMIT limits (LP: #1656259)
backport of upstream commit 933ec999511f3d29de005bfa8966ae007b161c0f
("Retire .write/.read file operations")
-- Colin Ian King Fri, 17 Feb 2017 11:00:12
+
** Changed in: zfs-linux (Ubuntu Yakkety)
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/1656259
Title:
Linux ZFS port doesn't respect RLIMIT_FSIZE
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Committed
Status in zfs-linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Committed
Status in zfs-linux source package in Zesty:
Fix Released
Bug description:
== SRU Request, Yakkety, Xenial ==
bash -c 'ulimit -f 1024; yes | head -n2097152'
>/path/on/filesystem/under/test
On ext4, this test case prints something along the lines of:
bash: line 1: 11274 Broken pipe yes
11275 File size limit exceeded(core dumped) | head -n2097152
On ZFS, this test case incorrectly exits zero with no output,
demonstrating that ZFS does not respect RLIMIT_FSIZE.
I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT,
and on those systems this test case correctly generates SIGXFSZ; so it
seems that this is a bug in the Linux port of ZFS.
(This was discovered while tracking down Launchpad test suite failures
under LXD on ZFS. Launchpad uses RLIMIT_FSIZE in one place to guard
against bugs that cause debdiff to generate arbitrarily large amounts
of output and fill the disk.)
== Fix ==
Upstream fix
https://github.com/behlendorf/zfs/commit/230c03e59d3d13d9b60125f73cf3fff327b45c21
== Test case ==
With the fix:
bash -c 'ulimit -f 1024; yes | head -n2097152'
>/path/on/filesystem/under/test
should report:
bash: line 1: 11274 Broken pipe yes
11275 File size limit exceeded(core dumped) | head -n2097152
== Regression Potential ==
Could break read/writes semantics to zfs
--
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-57-generic 4.4.0-57.78
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 13 10:01:36 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875
InstallationDate: Installed on 2013-03-01 (1413 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
MachineType: LENOVO 20BXCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed
root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-57-generic N/A
linux-backports-modules-4.4.0-57-generic N/A
linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET49WW (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BXCTO1WW
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1656259/+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 1656259] Re: Linux ZFS port doesn't respect RLIMIT_FSIZE
This bug was fixed in the package zfs-linux - 0.6.5.6-0ubuntu16
---
zfs-linux (0.6.5.6-0ubuntu16) xenial; urgency=medium
* Enable zfs to respect RSIZE_LIMIT limits (LP: #1656259)
- backport of zfs upstream commit 4b908d32200b6e5c7b5115322b6c8d25e770daa0
("Linux 4.8 compat: posix_acl_valid()") to facilitate changes in
posix_acl_valid.
1015-Linux-4.8-compat-posix_acl_valid.patch
- backport of upstream commit 933ec999511f3d29de005bfa8966ae007b161c0f
("Retire .write/.read file operations")
1016-Retire-.write-.read-file-operations.patch
-- Colin Ian King Fri, 17 Feb 2017 11:00:12
+
** Changed in: zfs-linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1656259
Title:
Linux ZFS port doesn't respect RLIMIT_FSIZE
Status in Linux:
Fix Released
Status in linux package in Ubuntu:
Fix Committed
Status in zfs-linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Committed
Status in zfs-linux source package in Xenial:
Fix Released
Status in linux source package in Yakkety:
Fix Committed
Status in zfs-linux source package in Yakkety:
Fix Released
Status in linux source package in Zesty:
Fix Committed
Status in zfs-linux source package in Zesty:
Fix Released
Bug description:
== SRU Request, Yakkety, Xenial ==
bash -c 'ulimit -f 1024; yes | head -n2097152'
>/path/on/filesystem/under/test
On ext4, this test case prints something along the lines of:
bash: line 1: 11274 Broken pipe yes
11275 File size limit exceeded(core dumped) | head -n2097152
On ZFS, this test case incorrectly exits zero with no output,
demonstrating that ZFS does not respect RLIMIT_FSIZE.
I asked a friend to run this on Solaris 5.10 and FreeBSD 10.0-CURRENT,
and on those systems this test case correctly generates SIGXFSZ; so it
seems that this is a bug in the Linux port of ZFS.
(This was discovered while tracking down Launchpad test suite failures
under LXD on ZFS. Launchpad uses RLIMIT_FSIZE in one place to guard
against bugs that cause debdiff to generate arbitrarily large amounts
of output and fill the disk.)
== Fix ==
Upstream fix
https://github.com/behlendorf/zfs/commit/230c03e59d3d13d9b60125f73cf3fff327b45c21
== Test case ==
With the fix:
bash -c 'ulimit -f 1024; yes | head -n2097152'
>/path/on/filesystem/under/test
should report:
bash: line 1: 11274 Broken pipe yes
11275 File size limit exceeded(core dumped) | head -n2097152
== Regression Potential ==
Could break read/writes semantics to zfs
--
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-57-generic 4.4.0-57.78
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Jan 13 10:01:36 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=139ad421-b014-4c34-ae8c-dd1d15205875
InstallationDate: Installed on 2013-03-01 (1413 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130223.1)
MachineType: LENOVO 20BXCTO1WW
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic.efi.signed
root=UUID=12c52021-a1ab-4984-9dd7-63cf0dcaac16 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-57-generic N/A
linux-backports-modules-4.4.0-57-generic N/A
linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/21/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET49WW (1.14 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BXCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrJBET49WW(1.14):bd05/21/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20BXCTO1WW
dmi.product.version: ThinkPad T450s
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1656259/+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 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
The important bits of udev seem to be these:
P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0
E: DRIVER=mlx4_core
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: MODALIAS=pci:v15B3d1003sv1014sd04B5bc02sc00i00
E: OF_COMPATIBLE_N=0
E: OF_FULLNAME=/pciex@3fffe4040/pci@0/ethernet@0
E: OF_NAME=ethernet
E: PCI_CLASS=2
E: PCI_ID=15B3:1003
E: PCI_SLOT_NAME=0008:01:00.0
E: PCI_SUBSYS_ID=1014:04B5
E: SUBSYSTEM=pci
E: USEC_INITIALIZED=11882462
P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_MODEL_ID=0x1003
E: ID_NET_DRIVER=mlx4_en
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enxe41d2d2590c0
E: ID_NET_NAME_PATH=enP8p1s0
E: ID_OUI_FROM_DATABASE=Mellanox Technologies, Inc.
E: ID_PATH=pci-0008:01:00.0
E: ID_PATH_TAG=pci-0008_01_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: ID_VENDOR_ID=0x15b3
E: IFINDEX=8
E: INTERFACE=enP8p1s0
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enP8p1s0
E: TAGS=:systemd:
E: USEC_INITIALIZED=8004370
P: /devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0d1
E: DEVPATH=/devices/pci0008:00/0008:00:00.0/0008:01:00.0/net/enP8p1s0d1
E: ID_BUS=pci
E: ID_MM_CANDIDATE=1
E: ID_MODEL_FROM_DATABASE=MT27500 Family [ConnectX-3]
E: ID_MODEL_ID=0x1003
E: ID_NET_DRIVER=mlx4_en
E: ID_NET_LINK_FILE=/lib/systemd/network/99-default.link
E: ID_NET_NAME_MAC=enxe41d2d2590c1
E: ID_NET_NAME_PATH=enP8p1s0d1
E: ID_OUI_FROM_DATABASE=Mellanox Technologies, Inc.
E: ID_PATH=pci-0008:01:00.0
E: ID_PATH_TAG=pci-0008_01_00_0
E: ID_PCI_CLASS_FROM_DATABASE=Network controller
E: ID_PCI_SUBCLASS_FROM_DATABASE=Ethernet controller
E: ID_VENDOR_FROM_DATABASE=Mellanox Technologies
E: ID_VENDOR_ID=0x15b3
E: IFINDEX=9
E: INTERFACE=enP8p1s0d1
E: SUBSYSTEM=net
E: SYSTEMD_ALIAS=/sys/subsystem/net/devices/enP8p1s0d1
E: TAGS=:systemd:
E: USEC_INITIALIZED=7956109
** Changed in: checkbox (Ubuntu)
Status: New => Invalid
** Changed in: checkbox (Ubuntu Xenial)
Status: New => Invalid
** Changed in: checkbox (Ubuntu)
Status: Invalid => New
** Changed in: checkbox (Ubuntu)
Status: New => Incomplete
--
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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in checkbox package in Ubuntu:
Incomplete
Status in linux package in Ubuntu:
Confirmed
Status in checkbox source package in Xenial:
Invalid
Status in linux source package in Xenial:
Confirmed
Bug description:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager
saw 8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev
]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendo
[Group.of.nepali.translators] [Bug 1656528] Re: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw'
This bug was fixed in the package thermald - 1.5.3-4ubuntu1 --- thermald (1.5.3-4ubuntu1) yakkety; urgency=medium * fix spamming of logs when writes file (LP: #1656528) - patch from Srinivas Pandruvada at Intel, not yet mainline -- Colin King Thu, 23 Feb 2017 09:26:23 + ** Changed in: thermald (Ubuntu Yakkety) 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/1656528 Title: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw' Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Xenial: Fix Released Status in thermald source package in Yakkety: Fix Released Status in thermald source package in Zesty: Fix Released Bug description: [SRU REQUEST, Xenial, Yakkety] Thermald is spamming the log with error messages on sysfs write failure messages. Demote these to debug level errors so that they aren't logged unless running in debug mode. [FIX] See comment #24, with the fix the messages are not logged when in normal non-debug running mode. [REGRESSION POTENIAL] Minimal, this just reduces the logging spam by turning messages into debug only for when running in debug mode. --- This seems somewhat related to https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046 For some reason thermald is writing the message "sysfs write failed constraint_0_power_limit_uw" to the syslog every few seconds. However, there's nothing in the kernel log. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" $ uname -a Linux graham-desktop 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep thermald ii thermald 1.5.3-4amd64Thermal monitoring and controlling daemon $ grep "sysfs write failed constraint_0_power_limit_uw" /var/log/syslog | wc -l 14160 $ grep thermald /var/log/kern.log | wc -l 0 I'm an experienced Linux user but not an experienced bug submitter, so please let me know if I have failed to provide any necessary info. Am happy to attach additional logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+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 1656528] Re: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw'
This bug was fixed in the package thermald - 1.5-2ubuntu3 --- thermald (1.5-2ubuntu3) xenial; urgency=medium * fix spamming of logs when writes file (LP: #1656528) - patch from Srinivas Pandruvada at Intel, not yet mainline -- Colin King Wed, 15 Mar 2017 17:32:33 + ** Changed in: thermald (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/1656528 Title: thermald spamming syslog with 'sysfs write failed constraint_0_power_limit_uw' Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Xenial: Fix Released Status in thermald source package in Yakkety: Fix Released Status in thermald source package in Zesty: Fix Released Bug description: [SRU REQUEST, Xenial, Yakkety] Thermald is spamming the log with error messages on sysfs write failure messages. Demote these to debug level errors so that they aren't logged unless running in debug mode. [FIX] See comment #24, with the fix the messages are not logged when in normal non-debug running mode. [REGRESSION POTENIAL] Minimal, this just reduces the logging spam by turning messages into debug only for when running in debug mode. --- This seems somewhat related to https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1543046 For some reason thermald is writing the message "sysfs write failed constraint_0_power_limit_uw" to the syslog every few seconds. However, there's nothing in the kernel log. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.10 DISTRIB_CODENAME=yakkety DISTRIB_DESCRIPTION="Ubuntu 16.10" $ uname -a Linux graham-desktop 4.8.0-34-generic #36-Ubuntu SMP Wed Dec 21 17:24:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l | grep thermald ii thermald 1.5.3-4amd64Thermal monitoring and controlling daemon $ grep "sysfs write failed constraint_0_power_limit_uw" /var/log/syslog | wc -l 14160 $ grep thermald /var/log/kern.log | wc -l 0 I'm an experienced Linux user but not an experienced bug submitter, so please let me know if I have failed to provide any necessary info. Am happy to attach additional logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1656528/+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 1671117] Re: [SRU] ceph 10.2.6
This bug was fixed in the package ceph - 10.2.6-0ubuntu0.16.04.1
---
ceph (10.2.6-0ubuntu0.16.04.1) xenial; urgency=medium
* New upstream stable point release (LP: #1671117):
- d/p/osd-limit-omap-data-in-push-op.patch,rgw_rados-creation_time.patch:
Dropped, included upstream.
- d/p/*: Refresh.
-- James Page Thu, 09 Mar 2017 16:21:36 +
** Changed in: ceph (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/1671117
Title:
[SRU] ceph 10.2.6
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive mitaka series:
Fix Committed
Status in ceph package in Ubuntu:
Fix Released
Status in ceph source package in Xenial:
Fix Released
Status in ceph source package in Yakkety:
Fix Released
Status in ceph source package in Zesty:
Fix Released
Bug description:
This point release fixes several important bugs in RBD mirroring, RGW
multi-site, CephFS, and RADOS.
We recommend that all v10.2.x users upgrade.
For more detailed information, see the complete changelog[1] and the
release notes[2]
Notable Changes
---
* build/ops: add hostname sanity check to run-{c}make-check.sh (issue#18134 ,
pr#12302 , Nathan Cutler)
* build/ops: add ldap lib to rgw lib deps based on build config (issue#17313
, pr#13183 , Nathan Cutler)
* build/ops: ceph-create-keys loops forever (issue#17753 , pr#11884 , Alfredo
Deza)
* build/ops: ceph daemons DUMPABLE flag is cleared by setuid preventing
coredumps (issue#17650 , pr#11736 , Patrick Donnelly)
* build/ops: fixed compilation error when --with-radowsgw=no (issue#18512 ,
pr#12729 , Pan Liu)
* build/ops: fixed the issue when --disable-server, compilation fails.
(issue#18120 , pr#12239 , Pan Liu)
* build/ops: fix undefined crypto references with --with-xio (issue#18133 ,
pr#12296 , Nathan Cutler)
* build/ops: install-deps.sh based on /etc/os-release (issue#18466 ,
issue#18198 , pr#12405 , Jan Fajerski, Nitin A Kamble, Nathan Cutler)
* build/ops: Remove the runtime dependency on lsb_release (issue#17425 ,
pr#11875 , John Coyle, Brad Hubbard)
* build/ops: rpm: /etc/ceph/rbdmap is packaged with executable access rights
(issue#17395 , pr#11855 , Ken Dreyer)
* build/ops: selinux: Allow ceph to manage tmp files (issue#17436 , pr#13048
, Boris Ranto)
* build/ops: systemd: Restart Mon after 10s in case of failure (issue#18635 ,
pr#13058 , Wido den Hollander)
* build/ops: systemd restarts Ceph Mon to quickly after failing to start
(issue#18635 , pr#13184 , Wido den Hollander)
* ceph-disk: fix flake8 errors (issue#17898 , pr#11976 , Ken Dreyer)
* cephfs: fuse client crash when adding a new osd (issue#17270 , pr#11860 ,
John Spray)
* cli: ceph-disk: convert none str to str before printing it (issue#18371 ,
pr#13187 , Kefu Chai)
* client: Fix lookup of "/.." in jewel (issue#18408 , pr#12766 , Jeff Layton)
* client: fix stale entries in command table (issue#17974 , pr#12137 , John
Spray)
* client: populate metadata during mount (issue#18361 , pr#13085 , John Spray)
* cli: implement functionality for adding, editing and removing omap values
with binary keys (issue#18123 , pr#12755 , Jason Dillaman)
* common: Improve linux dcache hash algorithm (issue#17599 , pr#11529 , Yibo
Cai)
* common: utime.h: fix timezone issue in round_to_* funcs. (issue#14862 ,
pr#11508 , Zhao Chao)
* doc: Python Swift client commands in Quick Developer Guide don't match
configuration in vstart.sh (issue#17746 , pr#13043 , Ronak Jain)
* librbd: allow to open an image without opening parent image (issue#18325 ,
pr#13130 , Ricardo Dias)
* librbd: metadata_set API operation should not change global config setting
(issue#18465 , pr#13168 , Mykola Golub)
* librbd: new API method to force break a peer's exclusive lock (issue#15632
, issue#16773 , issue#17188 , issue#16988 , issue#17210 , issue#17251 ,
issue#18429 , issue#17227 , issue#18327 , issue#17015 , pr#12890 , Danny
Al-Gaaf, Mykola Golub, Jason Dillaman)
* librbd: properly order concurrent updates to the object map (issue#16176 ,
pr#12909 , Jason Dillaman)
* librbd: restore journal access when force disabling mirroring (issue#17588
, pr#11916 , Mykola Golub)
* mds: Cannot create deep directories when caps contain path=/somepath
(issue#17858 , pr#12154 , Patrick Donnelly)
* mds: cephfs metadata pool: deep-scrub error omap_digest != best guess
omap_digest (issue#17177 , pr#12380 , Yan, Zheng)
* mds: cephfs test failures (ceph.com/qa is broken, should be
download.ceph.com/qa) (issue#18574 , pr#13023 , John Spray)
* mds: ceph-fuse crash during snapshot tests (issue#18460 , pr#13120 , Yan,
Zheng)
* mds: ceph_volume_client: fix recovery from partial auth update
(issue#17216 , pr#11656 , Ramana
[Group.of.nepali.translators] [Bug 1671117] Re: [SRU] ceph 10.2.6
This bug was fixed in the package ceph - 10.2.6-0ubuntu0.16.10.1
---
ceph (10.2.6-0ubuntu0.16.10.1) yakkety; urgency=medium
* New upstream stable point release (LP: #1671117):
- d/p/osd-limit-omap-data-in-push-op.patch,rgw_rados-creation_time.patch:
Dropped, included upstream.
- d/p/*: Refresh.
-- James Page Thu, 09 Mar 2017 16:21:03 +
** Changed in: ceph (Ubuntu Yakkety)
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/1671117
Title:
[SRU] ceph 10.2.6
Status in Ubuntu Cloud Archive:
Invalid
Status in Ubuntu Cloud Archive mitaka series:
Fix Committed
Status in ceph package in Ubuntu:
Fix Released
Status in ceph source package in Xenial:
Fix Released
Status in ceph source package in Yakkety:
Fix Released
Status in ceph source package in Zesty:
Fix Released
Bug description:
This point release fixes several important bugs in RBD mirroring, RGW
multi-site, CephFS, and RADOS.
We recommend that all v10.2.x users upgrade.
For more detailed information, see the complete changelog[1] and the
release notes[2]
Notable Changes
---
* build/ops: add hostname sanity check to run-{c}make-check.sh (issue#18134 ,
pr#12302 , Nathan Cutler)
* build/ops: add ldap lib to rgw lib deps based on build config (issue#17313
, pr#13183 , Nathan Cutler)
* build/ops: ceph-create-keys loops forever (issue#17753 , pr#11884 , Alfredo
Deza)
* build/ops: ceph daemons DUMPABLE flag is cleared by setuid preventing
coredumps (issue#17650 , pr#11736 , Patrick Donnelly)
* build/ops: fixed compilation error when --with-radowsgw=no (issue#18512 ,
pr#12729 , Pan Liu)
* build/ops: fixed the issue when --disable-server, compilation fails.
(issue#18120 , pr#12239 , Pan Liu)
* build/ops: fix undefined crypto references with --with-xio (issue#18133 ,
pr#12296 , Nathan Cutler)
* build/ops: install-deps.sh based on /etc/os-release (issue#18466 ,
issue#18198 , pr#12405 , Jan Fajerski, Nitin A Kamble, Nathan Cutler)
* build/ops: Remove the runtime dependency on lsb_release (issue#17425 ,
pr#11875 , John Coyle, Brad Hubbard)
* build/ops: rpm: /etc/ceph/rbdmap is packaged with executable access rights
(issue#17395 , pr#11855 , Ken Dreyer)
* build/ops: selinux: Allow ceph to manage tmp files (issue#17436 , pr#13048
, Boris Ranto)
* build/ops: systemd: Restart Mon after 10s in case of failure (issue#18635 ,
pr#13058 , Wido den Hollander)
* build/ops: systemd restarts Ceph Mon to quickly after failing to start
(issue#18635 , pr#13184 , Wido den Hollander)
* ceph-disk: fix flake8 errors (issue#17898 , pr#11976 , Ken Dreyer)
* cephfs: fuse client crash when adding a new osd (issue#17270 , pr#11860 ,
John Spray)
* cli: ceph-disk: convert none str to str before printing it (issue#18371 ,
pr#13187 , Kefu Chai)
* client: Fix lookup of "/.." in jewel (issue#18408 , pr#12766 , Jeff Layton)
* client: fix stale entries in command table (issue#17974 , pr#12137 , John
Spray)
* client: populate metadata during mount (issue#18361 , pr#13085 , John Spray)
* cli: implement functionality for adding, editing and removing omap values
with binary keys (issue#18123 , pr#12755 , Jason Dillaman)
* common: Improve linux dcache hash algorithm (issue#17599 , pr#11529 , Yibo
Cai)
* common: utime.h: fix timezone issue in round_to_* funcs. (issue#14862 ,
pr#11508 , Zhao Chao)
* doc: Python Swift client commands in Quick Developer Guide don't match
configuration in vstart.sh (issue#17746 , pr#13043 , Ronak Jain)
* librbd: allow to open an image without opening parent image (issue#18325 ,
pr#13130 , Ricardo Dias)
* librbd: metadata_set API operation should not change global config setting
(issue#18465 , pr#13168 , Mykola Golub)
* librbd: new API method to force break a peer's exclusive lock (issue#15632
, issue#16773 , issue#17188 , issue#16988 , issue#17210 , issue#17251 ,
issue#18429 , issue#17227 , issue#18327 , issue#17015 , pr#12890 , Danny
Al-Gaaf, Mykola Golub, Jason Dillaman)
* librbd: properly order concurrent updates to the object map (issue#16176 ,
pr#12909 , Jason Dillaman)
* librbd: restore journal access when force disabling mirroring (issue#17588
, pr#11916 , Mykola Golub)
* mds: Cannot create deep directories when caps contain path=/somepath
(issue#17858 , pr#12154 , Patrick Donnelly)
* mds: cephfs metadata pool: deep-scrub error omap_digest != best guess
omap_digest (issue#17177 , pr#12380 , Yan, Zheng)
* mds: cephfs test failures (ceph.com/qa is broken, should be
download.ceph.com/qa) (issue#18574 , pr#13023 , John Spray)
* mds: ceph-fuse crash during snapshot tests (issue#18460 , pr#13120 , Yan,
Zheng)
* mds: ceph_volume_client: fix recovery from partial auth update
(issue#17216 , pr#11656 , Raman
[Group.of.nepali.translators] [Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
** Also affects: checkbox (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/1675091
Title:
Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by
udev
Status in checkbox package in Ubuntu:
New
Status in linux package in Ubuntu:
Confirmed
Status in checkbox source package in Xenial:
New
Status in linux source package in Xenial:
Confirmed
Bug description:
During certification testing on Power8NVL, the network tests for the
Mellanox 40/56G network cards are failing. According to the failure
pasted below, udev/dbus isn't detecting the network card properly, but
NetworkManager is. My feeling is this might be an issue with
UdevadmParser.
ERROR: devices missing - udev showed 7 NETWORK devices, but NetworkManager
saw 8 devices in ('Ethernet', 'Modem')
---[ Devices found by udev
]
Category: NETWORK
Interface: enP1p1s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.0
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.1
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f2
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.2
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP1p1s0f3
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0001:00/0001:00:00.0/0001:01:00.3
ID: [14e4:1657]
Subsystem ID: [1014:0420]
Category: NETWORK
Interface: enP8p1s0d1
Product: MT27500 Family [ConnectX-3]
Vendor: Mellanox Technologies
Driver: mlx4_core (ver: 2.2-1)
Path: /devices/pci0008:00/0008:00:00.0/0008:01:00.0
Category: NETWORK
Interface: enP9p7s0f0
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.0
ID: [14e4:1657]
Subsystem ID: [14e4:1981]
Category: NETWORK
Interface: enP9p7s0f1
Product: NetXtreme BCM5719 Gigabit Ethernet PCIe
Vendor: Broadcom Corporation
Driver: tg3 (ver: Unknown)
Path: /devices/pci0009:00/0009:00:00.0/0009:01:00.0/0009:02:04.0/0009:07:00.1
ID: [14e4:1657]
Subsystem ID: [14e4:1657]
--[ Devices found by Network Manager
]--
Category: Ethernet
Interface: enP1p1s0f3
IP: 10.20.30.54
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f0
IP: 10.20.30.52
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP9p7s0f1
IP: 10.20.30.53
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0
IP: 10.20.30.5
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f0
IP: 10.20.30.56
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP8p1s0d1
IP: 10.20.30.6
Driver: mlx4_core (ver: 2.2-1)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f1
IP: 10.20.30.57
Driver: tg3 (ver: Unknown)
State: Unmanaged
Category: Ethernet
Interface: enP1p1s0f2
IP: 10.20.30.55
Driver: tg3 (ver: Unknown)
State: Unmanaged
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-66-generic 4.4.0-66.87
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic ppc64le
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Mar 21 17:00 seq
crw-rw 1 root audio 116, 33 Mar 21 17:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: ppc64el
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Mar 22 15:59:40 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
PciMultimedia:
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 astdrmfb
ProcKernelCmdLine: root=UUID=a287c2bd-7e5a-488c-8921-5cf86aed177a ro
ProcLoadAvg: 5.79 2.74 1.02 1/1261 881
ProcLocks:
1: POSIX ADVISORY WRITE 4149 00:14:817 0 EOF
2: POSIX ADVISORY
[Group.of.nepali.translators] [Bug 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
This bug was fixed in the package pepperflashplugin-nonfree - 1.8.2ubuntu1.1 --- pepperflashplugin-nonfree (1.8.2ubuntu1.1) xenial-proposed; urgency=medium * Update to use adobe upstream rather than google (LP: #1632870). -- Bhavani Shankar Fri, 24 Feb 2017 19:29:38 +0530 ** Changed in: pepperflashplugin-nonfree (Ubuntu Xenial) Status: Fix Committed => Fix Released ** Changed in: pepperflashplugin-nonfree (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/1632870 Title: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux Status in pepperflashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree source package in Trusty: Fix Released Status in pepperflashplugin-nonfree source package in Xenial: Fix Released Status in pepperflashplugin-nonfree source package in Yakkety: Fix Released Status in pepperflashplugin-nonfree package in Debian: Fix Released Bug description: [Impact] Pepperflashplugin-nonfree is a Debian package, slightly modified for Ubuntu, and available in multiverse, that downloads the PPAPI Flash plugin from Google (up to v1.8.3 in Debian and v1.8.2+nmu1ubuntu1 in Ubuntu 16.10) or Adobe (starting with v1.8.3+nmu1 in Debian and v1.8.3+nmu1ubuntu1 in Ubuntu 17.04), and installs it as /usr/lib /pepperflashplugin-nonfree/libpepflashplayer.so. Versions that download the PPAPI plugin from Google are currently broken since Google decided to unbundle the plugin from Chrome 54, released in late 2016-10. Until that date, ripping the PPAPI plugin from a download of Google Chrome (which comes as a .deb package) was a popular way to get it, and the only possible way on Linux in the early days of the PPAPI plugin, when it was only available to Google. Then Adobe made the Linux PPAPI plugin available to Canonical and on their download site. The Debian package was changed to download the plugin from Adobe, in version 1.8.3+nmu1 on 2017-01-14, and that fix landed in 1.8.3+nmu1ubuntu1 in Ubuntu 17.04 (the current development release) on 2017-01-22. The package is still broken in the published releases: 16.10 16.04 14.04. It could be repaired by merging the changes made between 1.8.3ubuntu1 and 1.8.3+nmu1ubuntu1 into the published releases' versions of the package. This would qualify for an SRU because the bug comes from a change in a web service that made the package stop being installable. This change also causes a security vulnerability in so far as the Flash plugin can no longer be updated (updates were processed by downloading a new version of Google Chrome and extracting the bundled Flash plugin). [Test Case] On Ubuntu < 17.04, installation and reinstallation of pepperflashplugin-nonfree (v < 1.8.3+nmu1ubuntu1) fails. On Ubuntu 17.04 (v = 1.8.3+nmu1ubuntu1), it succeeds. [Regression Potential] I can't think of any. The new version has been in Debian Sid for one month without any report of a regression, so that's a good sign. It was initially tested in debbug 833741. [Why not to SRU] On the one hand, it's bad form to leave an utterly broken package in the published releases when it has been fixed in the development release and works there. Theoretically, SRUs should be performed. On the other hand, pepperflashplugin-nonfree is The Debian's Way to install the PPAPI Flash plugin. Ubuntu users are recommended to install adobe-flashplugin from Canonical's partner repository instead. Not all Ubuntu users are aware of that. See: https://help.ubuntu.com/stable/ubuntu-help/net-install-flash.html https://wiki.ubuntu.com/Chromium/Getting-Flash We can consider intentionally not fixing that package in the published releases, in which case this bug report should be marked Won't Fix in Yakkety, Xenial, Trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1632870/+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 1632870] Re: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux
This bug was fixed in the package pepperflashplugin-nonfree - 1.8.2+nmu1ubuntu1.1 --- pepperflashplugin-nonfree (1.8.2+nmu1ubuntu1.1) yakkety-proposed; urgency=medium * Update to use adobe upstream rather than google (LP: #1632870) * Add alternate dependency on gnupg1 as gnupg is no longer available in yakkety. -- Bhavani Shankar Fri, 24 Feb 2017 18:34:02 +0530 ** Changed in: pepperflashplugin-nonfree (Ubuntu Yakkety) 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/1632870 Title: Package is broken since Google stopped shipping Flash with Chrome 54 for Linux Status in pepperflashplugin-nonfree package in Ubuntu: Fix Released Status in pepperflashplugin-nonfree source package in Trusty: Fix Released Status in pepperflashplugin-nonfree source package in Xenial: Fix Released Status in pepperflashplugin-nonfree source package in Yakkety: Fix Released Status in pepperflashplugin-nonfree package in Debian: Fix Released Bug description: [Impact] Pepperflashplugin-nonfree is a Debian package, slightly modified for Ubuntu, and available in multiverse, that downloads the PPAPI Flash plugin from Google (up to v1.8.3 in Debian and v1.8.2+nmu1ubuntu1 in Ubuntu 16.10) or Adobe (starting with v1.8.3+nmu1 in Debian and v1.8.3+nmu1ubuntu1 in Ubuntu 17.04), and installs it as /usr/lib /pepperflashplugin-nonfree/libpepflashplayer.so. Versions that download the PPAPI plugin from Google are currently broken since Google decided to unbundle the plugin from Chrome 54, released in late 2016-10. Until that date, ripping the PPAPI plugin from a download of Google Chrome (which comes as a .deb package) was a popular way to get it, and the only possible way on Linux in the early days of the PPAPI plugin, when it was only available to Google. Then Adobe made the Linux PPAPI plugin available to Canonical and on their download site. The Debian package was changed to download the plugin from Adobe, in version 1.8.3+nmu1 on 2017-01-14, and that fix landed in 1.8.3+nmu1ubuntu1 in Ubuntu 17.04 (the current development release) on 2017-01-22. The package is still broken in the published releases: 16.10 16.04 14.04. It could be repaired by merging the changes made between 1.8.3ubuntu1 and 1.8.3+nmu1ubuntu1 into the published releases' versions of the package. This would qualify for an SRU because the bug comes from a change in a web service that made the package stop being installable. This change also causes a security vulnerability in so far as the Flash plugin can no longer be updated (updates were processed by downloading a new version of Google Chrome and extracting the bundled Flash plugin). [Test Case] On Ubuntu < 17.04, installation and reinstallation of pepperflashplugin-nonfree (v < 1.8.3+nmu1ubuntu1) fails. On Ubuntu 17.04 (v = 1.8.3+nmu1ubuntu1), it succeeds. [Regression Potential] I can't think of any. The new version has been in Debian Sid for one month without any report of a regression, so that's a good sign. It was initially tested in debbug 833741. [Why not to SRU] On the one hand, it's bad form to leave an utterly broken package in the published releases when it has been fixed in the development release and works there. Theoretically, SRUs should be performed. On the other hand, pepperflashplugin-nonfree is The Debian's Way to install the PPAPI Flash plugin. Ubuntu users are recommended to install adobe-flashplugin from Canonical's partner repository instead. Not all Ubuntu users are aware of that. See: https://help.ubuntu.com/stable/ubuntu-help/net-install-flash.html https://wiki.ubuntu.com/Chromium/Getting-Flash We can consider intentionally not fixing that package in the published releases, in which case this bug report should be marked Won't Fix in Yakkety, Xenial, Trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pepperflashplugin-nonfree/+bug/1632870/+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 1584431] Re: mongosniff crashes on start
** Changed in: mongodb (Ubuntu Trusty)
Status: New => Invalid
** Changed in: mongodb (Ubuntu Xenial)
Status: New => In Progress
** Changed in: mongodb (Ubuntu Yakkety)
Status: New => In Progress
** Changed in: mongodb (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: mongodb (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: mongodb (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: mongodb (Ubuntu Trusty)
Assignee: (unassigned) => Joshua Powers (powersj)
** Changed in: mongodb (Ubuntu Yakkety)
Assignee: (unassigned) => Joshua Powers (powersj)
** Changed in: mongodb (Ubuntu Xenial)
Assignee: (unassigned) => Joshua Powers (powersj)
--
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/1584431
Title:
mongosniff crashes on start
Status in mongodb package in Ubuntu:
Fix Released
Status in mongodb source package in Trusty:
Invalid
Status in mongodb source package in Xenial:
In Progress
Status in mongodb source package in Yakkety:
In Progress
Bug description:
Ubuntu:
* Xenial x64
Packages:
#user@localhost:~$ for i in `dpkg --get-selections|grep -v deinstall|grep
mongo|cut -f1`; do echo $i `sudo apt-cache show $i|sed -n -e 's/^.*Version:
1://p'`; done
* mongodb 2.6.10-0ubuntu1
* mongodb-clients 2.6.10-0ubuntu1
* mongodb-server 2.6.10-0ubuntu1
Steps to reproduce:
1. start service
2. start sniffer
3. start shell
4. crash sniffer
---
user@localhost:~$ sudo service mongodb start
user@localhost:~$ mongo
MongoDB shell version: 2.6.10
connecting to: test
(...)
user@localhost:~$ sudo mongosniff --source NET lo
sniffing... 27017
127.0.0.1:37522 -->> 127.0.0.1:27017 admin.$cmd 60 bytes id:0 0
query: { whatsmyuri: 1 } ntoreturn: 1 ntoskip: 0
2016-05-22T01:26:35.545-0400 Assertion failure messageShouldHaveNs()
src/mongo/db/dbmessage.cpp 82
2016-05-22T01:26:35.553-0400 0xea35a9 0xe397cf 0xe14772 0x86aca8 0x615c13
0x7f614d369ef6 0x7f614d36e9d1 0x7f614d3731fd 0x616a5a 0x5e57a9 0x7f614c71a830
0x614389
mongosniff(_ZN5mongo15printStackTraceERSo+0x39) [0xea35a9]
mongosniff(_ZN5mongo10logContextEPKc+0x21f) [0xe397cf]
mongosniff(_ZN5mongo12verifyFailedEPKcS1_j+0x142) [0xe14772]
mongosniff() [0x86aca8]
mongosniff(_Z10got_packetPhPK11pcap_pkthdrPKh+0x573) [0x615c13]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(+0x5ef6) [0x7f614d369ef6]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(+0xa9d1) [0x7f614d36e9d1]
/usr/lib/x86_64-linux-gnu/libpcap.so.0.8(pcap_loop+0x5d) [0x7f614d3731fd]
mongosniff(_Z8toolMainiPPcS0_+0x69a) [0x616a5a]
mongosniff(main+0x9) [0x5e57a9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f614c71a830]
mongosniff(_start+0x29) [0x614389]
terminate called after throwing an instance of 'mongo::AssertionException'
what(): assertion src/mongo/db/dbmessage.cpp:82
Aborted (core dumped)
user@localhost:~$
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1584431/+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 1675443] [NEW] Update linux-firmware in xenial for 4.10 hwe-edge kernel
Public bug reported: linux-hwe-edge in xenial is in the process of being updated to be based on the 4.10 zesty kernel. Add/update firmware files for this kernel. ** Affects: linux-firmware (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: Invalid ** Affects: linux-firmware (Ubuntu Xenial) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress ** Also affects: linux-firmware (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Invalid ** Changed in: linux-firmware (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux-firmware (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Xenial) Assignee: (unassigned) => Seth Forshee (sforshee) ** Summary changed: - Update linux-firmware in xenial for zesty hwe-edge kernel + Update linux-firmware in xenial for 4.10 hwe-edge kernel -- 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/1675443 Title: Update linux-firmware in xenial for 4.10 hwe-edge kernel Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Xenial: In Progress Bug description: linux-hwe-edge in xenial is in the process of being updated to be based on the 4.10 zesty kernel. Add/update firmware files for this kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1675443/+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 1674944] Re: linux-aws: 4.4.0-1011.20 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 23. March 2017 14:01 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 23. March 2017 14:01 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1674944 Title: linux-aws: 4.4.0-1011.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 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/1674944/+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 1674945] Re: linux-gke: 4.4.0-1008.8 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 23. March 2017 14:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 23. March 2017 14:02 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1674945 Title: linux-gke: 4.4.0-1008.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gke package in Ubuntu: Invalid Status in linux-gke source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 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/1674945/+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 1674941] Re: linux-snapdragon: 4.4.0-1053.57 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 23. March 2017 13:35 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 23. March 2017 13:35 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1674941 Title: linux-snapdragon: 4.4.0-1053.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: 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 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 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/1674941/+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 1674940] Re: linux-raspi2: 4.4.0-1050.57 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Thursday, 23. March 2017 13:04 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Thursday, 23. March 2017 13:04 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- 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/1674940 Title: linux-raspi2: 4.4.0-1050.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: 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 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674938 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/1674940/+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 1675391] [NEW] [SRU] New stable micro release 2.28
Public bug reported: This is an SRU bug to release 2.28 of snapcraft which follows the guidelines defined in the wiki over at https://wiki.ubuntu.com/SnapcraftUpdates The list of bugs and features in this release are defined at https://launchpad.net/snapcraft/+milestone/2.28 and https://launchpad.net/snapcraft/+milestone/2.28 ** Affects: snapcraft (Ubuntu) Importance: Undecided Status: New ** Affects: snapcraft (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: snapcraft (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: snapcraft (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: snapcraft (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: snapcraft (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: snapcraft (Ubuntu Yakkety) 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/1675391 Title: [SRU] New stable micro release 2.28 Status in snapcraft package in Ubuntu: New Status in snapcraft source package in Xenial: New Status in snapcraft source package in Yakkety: New Status in snapcraft source package in Zesty: New Bug description: This is an SRU bug to release 2.28 of snapcraft which follows the guidelines defined in the wiki over at https://wiki.ubuntu.com/SnapcraftUpdates The list of bugs and features in this release are defined at https://launchpad.net/snapcraft/+milestone/2.28 and https://launchpad.net/snapcraft/+milestone/2.28 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapcraft/+bug/1675391/+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 1621340] Re: [SRU]'multipath -r' causes /dev/mapper/ being removed
** Changed in: multipath-tools (Ubuntu Yakkety)
Status: Fix Committed => Fix Released
** Tags removed: sts-sru
** Tags added: sts-sru-done
--
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/1621340
Title:
[SRU]'multipath -r' causes /dev/mapper/ being removed
Status in multipath-tools package in Ubuntu:
Fix Released
Status in multipath-tools source package in Xenial:
Fix Released
Status in multipath-tools source package in Yakkety:
Fix Released
Bug description:
[Impact]
"multipath -r" causes the /dev/mapper/ to disappear momentarily,
which leads to some issue in consumer applications as such OpenStack.
[Test Case]
* connect to an multipath iscsi target
* multipath -r
* /dev/mapper/ disappears momentarily
[Regression Potential]
* None
"multipath -r" causes the /dev/mapper/ to disappear momentarily, which
leads to some issue in consumer applications as such OpenStack. After some
investigation, I found that /dev/mapper/ was deleted by udev during the
reload, and it was re-created soon later by multipathd (livdevmapper code of
cause). Detailed findings are as follows:
For reload in domap (rename as well),
case ACT_RELOAD:
r = dm_addmap_reload(mpp, params);
if (r)
r = dm_simplecmd_noflush(DM_DEVICE_RESUME, mpp->alias,
0, MPATH_UDEV_RELOAD_FLAG);
break;
it passes 0 to dm_simplecmd_noflush as argument for needsync, which
makes dm_task_set_cookie call being skipped in dm_simplecmd,
if (udev_wait_flag && !dm_task_set_cookie(dmt, &cookie,
((conf->daemon)? DM_UDEV_DISABLE_LIBRARY_FALLBACK : 0) | udev_flags)) {
dm_udev_complete(cookie);
goto out;
}
because of the short-circuit evaluation. Thus _do_dm_ioctl in
libdevmapper will add DM_UDEV_DISABLE_DM_RULES_FLAG flag to
dmi->event_nr, and that will eventually be used in the udev rules
(55-dm.rules),
ENV{DM_UDEV_DISABLE_DM_RULES_FLAG}!="1", ENV{DM_NAME}=="?*",
SYMLINK+="mapper/$env{DM_NAME}"
Since the DM_UDEV_DISABLE_DM_RULES_FLAG is set, the rule will not
match. As a result the link is removed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1621340/+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 1585940] Re: [SRU] ERROR "can't get udev device" when iscsi multipath enabled
** Changed in: cloud-archive/mitaka Status: Fix Committed => Fix Released ** Tags removed: sts-sru ** Tags added: sts-sru-done -- 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/1585940 Title: [SRU] ERROR "can't get udev device" when iscsi multipath enabled Status in Ubuntu Cloud Archive: Invalid Status in Ubuntu Cloud Archive mitaka series: Fix Released Status in os-brick: Fix Released Status in python-os-brick package in Ubuntu: Invalid Status in python-os-brick source package in Xenial: Fix Released Bug description: [Impact] * Fallback device detection for multipath connections is currently broken. [Test Case] * Enable cinder/nova multipath but do not make multiple paths available (such that are no /dev/disk/path/by-id/dm* devices) * Create a cinder volume and attach to Nova instance * Check that volume was attached successfully and that /var/log/nova /nova-compute.log does not display the error mentioned below. [Regression Potential] * None SUMMARY: Wrong path used when detecting multipath id ANALYSE: when multipath device path was not found via LUN wwn, os-brick would use device path like below: /dev/disk/by-path/ip-192.168.3.52:3260-iscsi- iqn.1992-04.com.emc:cx.apm00153906536.b5-lun-155 to detect multipath id via 'multipath -l ' but this cause error: : can't get udev device actually, we should use its real path like /dev/sdb, dev/sda to detect the multipath id. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1585940/+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 1637223] Re: Update to newer version of docker-compose >= 1.6
Packages in https://launchpad.net/~mwhudson/+archive/ubuntu/devirt and in the X and Y SRU queues. ** No longer affects: dockerpty (Ubuntu Yakkety) ** Changed in: docker-compose (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: docker-compose (Ubuntu Yakkety) Status: Confirmed => In Progress ** Changed in: dockerpty (Ubuntu Xenial) Status: New => In Progress ** Changed in: python-docker (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: python-docker (Ubuntu Yakkety) Status: Confirmed => 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/1637223 Title: Update to newer version of docker-compose >= 1.6 Status in Ubuntu on IBM z Systems: Confirmed Status in docker-compose package in Ubuntu: Invalid Status in dockerpty package in Ubuntu: New Status in python-docker package in Ubuntu: Invalid Status in docker-compose source package in Xenial: In Progress Status in dockerpty source package in Xenial: In Progress Status in python-docker source package in Xenial: In Progress Status in docker-compose source package in Yakkety: In Progress Status in python-docker source package in Yakkety: In Progress Bug description: [Impact] Ubuntu 16.04.1 does not contain latest docker-compose release needed to handle v2 yml files. As minimum level 1.6 has to be integrated. [Test case] Follow the instructions at https://docs.docker.com/compose/gettingstarted/#step-4-build-and-run-your-app-with-compose, installing docker and docker-compose from the packages. [Regression potential] TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1637223/+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 1637223] Re: Update to newer version of docker-compose >= 1.6
So I had a look and it seems the dependence on python-websocket very weak; only one function in python-docker depends on websocket, and no code in Debian calls it. So I'd be happy to take the zesty versions of python-docker, dockerpty and docker-compose, drop the version from the build-dep on python-websocket and upload to Xenial. (Oh yes, python-docker build-depends on a newer python-backports.ssl- match-hostname but the file it imports from there is exactly the same as in the package in xenial, so we can relax that requirement too). I'll get the packages built in a ppa for testing and into the Xenial queue. Whoever from the SRU team reads this will probably want to check my working with reverse-depends ;-p ** Also affects: dockerpty (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/1637223 Title: Update to newer version of docker-compose >= 1.6 Status in Ubuntu on IBM z Systems: Confirmed Status in docker-compose package in Ubuntu: Invalid Status in dockerpty package in Ubuntu: New Status in python-docker package in Ubuntu: Invalid Status in docker-compose source package in Xenial: Confirmed Status in dockerpty source package in Xenial: New Status in python-docker source package in Xenial: Confirmed Status in docker-compose source package in Yakkety: Confirmed Status in dockerpty source package in Yakkety: New Status in python-docker source package in Yakkety: Confirmed Bug description: Ubuntu 16.04.1 does not contain latest docker-compose release needed to handle v2 yml files. As minimum level 1.6 has to be integrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1637223/+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 1674988] Re: linux-hwe: 4.8.0-44.47~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1674986 phase: Uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Thursday, 23. March 2017 07:31 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1674986 phase: Uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Thursday, 23. March 2017 07:31 UTC -- 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/1674988 Title: linux-hwe: 4.8.0-44.47~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-hwe package in Ubuntu: Invalid Status in linux-hwe source package in Xenial: New Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1674986 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1674988/+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
