** 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 ubuntu-release-upgrader - 1:17.10.7
---
ubuntu-release-upgrader (1:17.10.7) artful; urgency=medium
* DistUpgrade/DistUpgradeController.py: Provide better instructions when an
upgrade is aborted due to a lack of free space in a partition.
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
Public bug reported:
[Impact]
Sean Feole discovered that if you ifdown/ifup the NIC on an X-Gene 2 system,
the NIC does not come back online. While the interface is reported as up, you
cannot ping the system. In addition to the obvious problems this causes for a
sysadmin, it also breaks
** Also affects: util-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: util-linux (Ubuntu Zesty)
Importance: Undecided
Status: New
--
You received this bug
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 linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux-gcp - 4.10.0-1007.7
---
linux-gcp (4.10.0-1007.7) xenial; urgency=low
* linux-gcp: 4.10.0-1007.7 -proposed tracker (LP: #1718146)
[ Ubuntu: 4.10.0-36.40 ]
* linux: 4.10.0-36.40 -proposed tracker (LP: #1718143)
* Neighbour confirmation
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux - 4.4.0-97.120
---
linux (4.4.0-97.120) xenial; urgency=low
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible deadlock on CPU hot(un)plug (LP: #1670634)
- [Config] s390x -- disable CONFIG_{DM, SCSI}_MQ_DEFAULT
This bug was fixed in the package linux-snapdragon - 4.4.0-1077.82
---
linux-snapdragon (4.4.0-1077.82) xenial; urgency=low
* linux-snapdragon: 4.4.0-1077.82 -proposed tracker (LP: #1718154)
[ Ubuntu: 4.4.0-97.120 ]
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
*
This bug was fixed in the package linux-gke - 4.4.0-1032.32
---
linux-gke (4.4.0-1032.32) xenial; urgency=low
* linux-gke: 4.4.0-1032.32 -proposed tracker (LP: #1718156)
[ Ubuntu: 4.4.0-97.120 ]
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible
This bug was fixed in the package linux-raspi2 - 4.4.0-1075.83
---
linux-raspi2 (4.4.0-1075.83) xenial; urgency=low
* linux-raspi2: 4.4.0-1075.83 -proposed tracker (LP: #1718153)
[ Ubuntu: 4.4.0-97.120 ]
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq:
This bug was fixed in the package linux-kvm - 4.4.0-1008.13
---
linux-kvm (4.4.0-1008.13) xenial; urgency=low
* linux-kvm: 4.4.0-1008.13 -proposed tracker (LP: #1718157)
[ Ubuntu: 4.4.0-97.120 ]
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible
This bug was fixed in the package linux-aws - 4.4.0-1038.47
---
linux-aws (4.4.0-1038.47) xenial; urgency=low
* linux-aws: 4.4.0-1038.47 -proposed tracker (LP: #1720042)
[ Ubuntu: 4.4.0-97.120 ]
* linux: 4.4.0-97.120 -proposed tracker (LP: #1718149)
* blk-mq: possible
** Also affects: linux (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/1594214
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: snapcraft (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to
** Also affects: linux (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/1678477
** Also affects: linux (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/1721455
** Also affects: linux (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/1721511
** Also affects: linux (Ubuntu Zesty)
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/1720977
Ubuntu-hwe-4.10.0-37.41~16.04.1 was released to -security and -updates,
setting tracking bug to 'Fix Released'.
** Changed in: linux-hwe (Ubuntu Xenial)
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
--
You received this
** Also affects: mdadm (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: mdadm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: mdadm (Ubuntu)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Changed in: mdadm (Ubuntu)
Superseded by Ubuntu-hwe-4.10.0-37.41~16.04.1 (which includes Ubuntu-
hwe-4.10.0-36.40~16.04.1).
** Changed in: kernel-sru-workflow/promote-to-updates
Status: New => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Fix Released
--
You received
Public bug reported:
[Impact]
* In xenial, mdadm-waitclean is an init.d script, and it appears that
it doesn't not run late enough. In later releases a systemd-shutdown
script is shipped instead. Which results in wait-clean action executed
later in the shutdown cycle, having more chances to
** Description changed:
- Placeholder
+ This is a new version of snapd.
+
+ The changelog for 2.28.1 is available here
+
https://github.com/snapcore/snapd/blob/2.28.1/packaging/ubuntu-16.04/changelog,
+ the raw git changelog is available here:
+ https://github.com/snapcore/snapd/commits/2.28.1
Public bug reported:
[Impact]
* systemd-shutdown binary is executed to complete system shutdown. In
xenial, it calls sync() after killing all processes, and not before
killing them. This means that processes are racing the SIGKILL/TERM
timeouts to sync all IO to disk. To mitigate this race
This bug was fixed in the package linux - 4.10.0-37.41
---
linux (4.10.0-37.41) zesty; urgency=low
* CVE-2017-1000255
- SAUCE: powerpc/64s: Use emergency stack for kernel TM Bad Thing program
checks
- SAUCE: powerpc/tm: Fix illegal TM state in signal handler
linux
This bug was fixed in the package linux - 4.10.0-37.41
---
linux (4.10.0-37.41) zesty; urgency=low
* CVE-2017-1000255
- SAUCE: powerpc/64s: Use emergency stack for kernel TM Bad Thing program
checks
- SAUCE: powerpc/tm: Fix illegal TM state in signal handler
linux
37 matches
Mail list logo
