This is documented upstream as fixed in glibc 2.26, which is the version
we will ship in artful; therefore marking as resolved for the devel
series.
** Bug watch added: Sourceware.org Bugzilla #21258
https://sourceware.org/bugzilla/show_bug.cgi?id=21258
** Also affects: glibc via
** Also affects: atop (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: atop (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Tor 0.2.9.11 is now in Xenial and Zesty, marking Xenial as fix released.
** Changed in: tor (Ubuntu Xenial)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
Yakkety is EOL as of July 20, 2017.
** Changed in: xfce4-weather-plugin (Ubuntu Yakkety)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04
** Changed in: cinder/mitaka
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1449062
Title:
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
**
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
**
Can you apply the latest 16.04 updates and confirm this bug is resolved?
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Also
This bug was fixed in the package neutron - 2:8.4.0-0ubuntu5
---
neutron (2:8.4.0-0ubuntu5) xenial; urgency=medium
* d/p/l3-ha-don-t-send-routers-without-_ha_interface.patch: Backport fix for
l3 ha: don't send routers without '_ha_interface' (LP: #1668410)
-- Hua Zhang
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) =>
This bug was fixed in the package tor - 0.2.9.11-1ubuntu1~16.04.1
---
tor (0.2.9.11-1ubuntu1~16.04.1) xenial; urgency=medium
* Backport from Debian Stretch to Xenial. Ubuntu Delta: (LP: #1710753)
- Limit the seccomp build-dependency to [amd64 i386 armhf].
- Drop
** Changed in: kernel-sru-workflow/security-signoff
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
This bug was fixed in the package libqapt - 3.0.2-0ubuntu1.2
---
libqapt (3.0.2-0ubuntu1.2) xenial; urgency=low
* libqapt3 should depend on apt-xapian-index for the package index
access which is required for most operations (LP: #1530523).
-- Simon Quigley
This bug was fixed in the package linux-aws - 4.4.0-1035.44
---
linux-aws (4.4.0-1035.44) xenial; urgency=low
* linux-aws: 4.4.0-1035.44 -proposed tracker (LP: #1716620)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
*** This bug is a duplicate of bug 1716620 ***
https://bugs.launchpad.net/bugs/1716620
This bug was fixed in the package linux-aws - 4.4.0-1035.44
---
linux-aws (4.4.0-1035.44) xenial; urgency=low
* linux-aws: 4.4.0-1035.44 -proposed tracker (LP: #1716620)
[ Ubuntu:
*** This bug is a duplicate of bug 1716620 ***
https://bugs.launchpad.net/bugs/1716620
This bug was fixed in the package linux-aws - 4.4.0-1035.44
---
linux-aws (4.4.0-1035.44) xenial; urgency=low
* linux-aws: 4.4.0-1035.44 -proposed tracker (LP: #1716620)
[ Ubuntu:
This bug was fixed in the package python3.5 - 3.5.2-2ubuntu0~16.04.2
---
python3.5 (3.5.2-2ubuntu0~16.04.2) xenial; urgency=medium
* SRU: LP: #1711724 Fix dict segfault. Issue #27945.
-- Clint Byrum Fri, 18 Aug 2017 10:48:00 -0700
** Changed in: python3.5
This bug was fixed in the package walinuxagent - 2.2.17-0ubuntu1~17.04.1
---
walinuxagent (2.2.17-0ubuntu1~17.04.1) zesty; urgency=medium
* Backport artful version to zesty.
* New upstream release (LP: #1717306).
-- Łukasz 'sil2100' Zemczak Fri, 15
This bug was fixed in the package walinuxagent - 2.2.17-0ubuntu1~16.04.1
---
walinuxagent (2.2.17-0ubuntu1~16.04.1) xenial; urgency=medium
* Backport artful version to xenial.
* New upstream release (LP: #1717306).
-- Łukasz 'sil2100' Zemczak Fri,
This bug was fixed in the package linux - 3.13.0-132.181
---
linux (3.13.0-132.181) trusty; urgency=low
* linux: 3.13.0-132.181 -proposed tracker (LP: #1716634)
* CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length
linux (3.13.0-131.180)
This bug was fixed in the package linux - 3.13.0-132.181
---
linux (3.13.0-132.181) trusty; urgency=low
* linux: 3.13.0-132.181 -proposed tracker (LP: #1716634)
* CVE-2017-1000251
- Bluetooth: Properly check L2CAP config option output buffer length
linux (3.13.0-131.180)
I wasn't awake this morning it seems (or did to omuch at once), so I beg
your pardon and resummarize.
Also I had the chance to try the fs forwarding on a zestyl level
libvirt/qemu and it worked fine.
- The /srv/video rule obviously is just the case reported for a share that
exports this source.
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug is for
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => 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
** 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:
This bug was fixed in the package linux-gcp - 4.10.0-1006.6
---
linux-gcp (4.10.0-1006.6) xenial; urgency=low
* linux-gcp: 4.10.0-1006.6 -proposed tracker (LP: #1716609)
[ Ubuntu: 4.10.0-35.39 ]
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching
This bug was fixed in the package fuse-umfuse-ext2 -
0.4-1.1ubuntu0.17.04.1
---
fuse-umfuse-ext2 (0.4-1.1ubuntu0.17.04.1) zesty; urgency=high
* Correctly release locks in op_link (LP: #1674868).
-- Andrew Caldwell Wed, 22 Mar 2017
19:42:35 +
This bug was fixed in the package fuse-umfuse-ext2 -
0.4-1.1ubuntu0.16.04.1
---
fuse-umfuse-ext2 (0.4-1.1ubuntu0.16.04.1) xenial; urgency=high
* Correctly release locks in op_link (LP: #1674868).
-- Andrew Caldwell Wed, 22 Mar 2017
19:42:35 +
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
*** This bug is a duplicate of bug 1716609 ***
https://bugs.launchpad.net/bugs/1716609
This bug was fixed in the package linux-gcp - 4.10.0-1006.6
---
linux-gcp (4.10.0-1006.6) xenial; urgency=low
* linux-gcp: 4.10.0-1006.6 -proposed tracker (LP: #1716609)
[ Ubuntu:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in:
This bug was fixed in the package snapcraft - 2.34
---
snapcraft (2.34) xenial; urgency=medium
[ Sergio Schvezov ]
* core: cache FileBase entries when a checksum is provided (#1433)
* cli: better error message for missing mksquashfs (#1481)
* core: improve source caching
This bug was fixed in the package snapcraft - 2.34+17.04
---
snapcraft (2.34+17.04) zesty; urgency=medium
[ Sergio Schvezov ]
* core: cache FileBase entries when a checksum is provided (#1433)
* cli: better error message for missing mksquashfs (#1481)
* core: improve source
This bug was fixed in the package python3.6 - 3.6.1-1ubuntu0~17.04.0
---
python3.6 (3.6.1-1ubuntu0~17.04.0) zesty; urgency=medium
* SRU: LP: #1711724 Fix dict segfault. Issue #27945.
-- Clint Byrum Thu, 07 Sep 2017 09:36:03 -0700
** Changed in: python3.6
This bug was fixed in the package python3.5 - 3.5.3-1ubuntu0~17.04.0
---
python3.5 (3.5.3-1ubuntu0~17.04.0) zesty; urgency=medium
* SRU: LP: #1711724 Fix dict segfault. Issue #27945.
-- Clint Byrum Thu, 07 Sep 2017 09:23:57 -0700
** Changed in: python3.5
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux-raspi2 - 4.4.0-1074.82
---
linux-raspi2 (4.4.0-1074.82) xenial; urgency=low
* linux-raspi2: 4.4.0-1074.82 -proposed tracker (LP: #1716618)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
*** This bug is a duplicate of bug 1716619 ***
https://bugs.launchpad.net/bugs/1716619
This bug was fixed in the package linux-snapdragon - 4.4.0-1076.81
---
linux-snapdragon (4.4.0-1076.81) xenial; urgency=low
* linux-snapdragon: 4.4.0-1076.81 -proposed tracker (LP: #1716619)
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
*** This bug is a duplicate of bug 1716613 ***
https://bugs.launchpad.net/bugs/1716613
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing:
*** This bug is a duplicate of bug 1716622 ***
https://bugs.launchpad.net/bugs/1716622
This bug was fixed in the package linux-kvm - 4.4.0-1007.12
---
linux-kvm (4.4.0-1007.12) xenial; urgency=low
* linux-kvm: 4.4.0-1007.12 -proposed tracker (LP: #1716622)
[ Ubuntu:
*** This bug is a duplicate of bug 1716618 ***
https://bugs.launchpad.net/bugs/1716618
This bug was fixed in the package linux-raspi2 - 4.4.0-1074.82
---
linux-raspi2 (4.4.0-1074.82) xenial; urgency=low
* linux-raspi2: 4.4.0-1074.82 -proposed tracker (LP: #1716618)
[
*** This bug is a duplicate of bug 1716622 ***
https://bugs.launchpad.net/bugs/1716622
This bug was fixed in the package linux-kvm - 4.4.0-1007.12
---
linux-kvm (4.4.0-1007.12) xenial; urgency=low
* linux-kvm: 4.4.0-1007.12 -proposed tracker (LP: #1716622)
[ Ubuntu:
*** This bug is a duplicate of bug 1716613 ***
https://bugs.launchpad.net/bugs/1716613
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing:
*** This bug is a duplicate of bug 1716618 ***
https://bugs.launchpad.net/bugs/1716618
This bug was fixed in the package linux-raspi2 - 4.4.0-1074.82
---
linux-raspi2 (4.4.0-1074.82) xenial; urgency=low
* linux-raspi2: 4.4.0-1074.82 -proposed tracker (LP: #1716618)
[
*** This bug is a duplicate of bug 1716621 ***
https://bugs.launchpad.net/bugs/1716621
This bug was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu:
*** This bug is a duplicate of bug 1716621 ***
https://bugs.launchpad.net/bugs/1716621
This bug was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu:
This bug was fixed in the package linux-hwe - 4.10.0-35.39~16.04.1
---
linux-hwe (4.10.0-35.39~16.04.1) xenial; urgency=low
* linux-hwe: 4.10.0-35.39~16.04.1 -proposed tracker (LP: #1716608)
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing:
*** This bug is a duplicate of bug 1716619 ***
https://bugs.launchpad.net/bugs/1716619
This bug was fixed in the package linux-snapdragon - 4.4.0-1076.81
---
linux-snapdragon (4.4.0-1076.81) xenial; urgency=low
* linux-snapdragon: 4.4.0-1076.81 -proposed tracker (LP: #1716619)
This bug was fixed in the package linux - 4.4.0-96.119
---
linux (4.4.0-96.119) xenial; urgency=low
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- s390/mm: no local TLB flush for
This bug was fixed in the package linux-gke - 4.4.0-1031.31
---
linux-gke (4.4.0-1031.31) xenial; urgency=low
* linux-gke: 4.4.0-1031.31 -proposed tracker (LP: #1716621)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
This bug was fixed in the package linux-raspi2 - 4.4.0-1074.82
---
linux-raspi2 (4.4.0-1074.82) xenial; urgency=low
* linux-raspi2: 4.4.0-1074.82 -proposed tracker (LP: #1716618)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic
This bug was fixed in the package linux-kvm - 4.4.0-1007.12
---
linux-kvm (4.4.0-1007.12) xenial; urgency=low
* linux-kvm: 4.4.0-1007.12 -proposed tracker (LP: #1716622)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
* kernel panic -not
This bug was fixed in the package linux-snapdragon - 4.4.0-1076.81
---
linux-snapdragon (4.4.0-1076.81) xenial; urgency=low
* linux-snapdragon: 4.4.0-1076.81 -proposed tracker (LP: #1716619)
[ Ubuntu: 4.4.0-96.119 ]
* linux: 4.4.0-96.119 -proposed tracker (LP: #1716613)
*
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
Didn't see test results coming in after several attempts, might be some issue
to the test infrastructure.
I will just let it through and work with Brad to resolve this.
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => Fix Released
** Changed in:
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
This bug was fixed in the package linux - 4.10.0-35.39
---
linux (4.10.0-35.39) zesty; urgency=low
* linux: 4.10.0-35.39 -proposed tracker (LP: #1716606)
* kernel panic -not syncing: Fatal exception: panic_on_oops (LP: #1708399)
- SAUCE: s390/mm: fix local TLB flushing vs.
4.4.0-96.119 - generic
Regression test CMPL.
http://kernel.ubuntu.com/testing/tracker-index.html
Issue to note in amd64:
monotonic_time - gtod failed
ubuntu_kvm_unit_tests - pku, svm, hyperv_clock failed (smap failed on onza)
ubuntu_lxc - Failed to start networking in ubuntu-cloud container
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Hardware Certification have completed testing this -proposed kernel. No
regressions were observed, results are available here:
http://people.canonical.com/~hwcert/sru-
testing/xenial/4.10.0-35.39~16.04.1/xenial-4.10-proposed-published.html
** Tags added: certification-testing-passed
** Changed
** Changed in: libvirt (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
** Changed in: libvirt (Ubuntu)
Status: Confirmed => In Progress
** Changed in: libvirt (Ubuntu Zesty)
Assignee: ChristianEhrhardt (paelzer) => (unassigned)
--
You received this bug notification because
88 matches
Mail list logo