This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
Still have it, same problem too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1786197
Title:
stack 1.5.1 broken on 18.04 (AesonException)
To manage notifications about this bug go to:
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
--
You received this bug notification because you are a
Public bug reported:
Reported upstream as https://github.com/systemd/systemd/issues/10118
Ubuntu bionic, systemd version 237-3ubuntu10.19
When systemd-networkd is used to manage network bonds, upon systemd-
networkd, bonds are brought down for ~10 seconds affecting connectivity
to the server.
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
Public bug reported:
Upgraded to 19.04.
Can't connect to 2003 server:
rdesktop -g 1024x768 elk
Autoselected keyboard map ru
Failed to negotiate protocol, retrying with plain RDP.
ERROR: Failed to extract public key from certificate
ERROR: recv: Соединение разорвано другой стороной
Although
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.7~16.04.2
---
unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium
* Don't check blacklist too early and report updates from not allowed origins
as kept back. (LP: #1781176)
*
@jarnos #61
this is a separate issue fixed later, calculating upgradable packages leaves
the upgradable packages in the cache, and u-u counts them as the reverse
dependencies of the first kernel to be removed.
This keeps the first kernel on the system, but when there are no upgradable
packages
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Invalid
** Changed in: kernel-sru-workflow/security-signoff
Status: New => Invalid
** Changed in: kernel-sru-workflow
Status: In
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1826161
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: New => Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1826165
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
Unfortunately, I can't be sure, because I use Ubuntu 18.04 and I don't
want to change the system, especially not the LTS version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825609
Title:
Scilab
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reaches end-of-life today.
Do you still see the bug in a later supported
Good to know. I start all my abbreviations with a semicolon ";". I've
never used a colon though.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1221514
Title:
AutoKey-GTK: Hot Keys and Abbreviations
** Summary changed:
- calc: move cell does not update row sum
+ [upstream] calc: move cell does not update row sum
** Changed in: libreoffice (Ubuntu)
Status: New => Fix Released
** Changed in: libreoffice (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reaches end-of-life today.
Do you still see the bug in a later supported
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817258
Title:
"numastat" doesn't display correct information for the
** Changed in: ubuntu-power-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794055
Title:
[Witherspoon-DD2.2][Ubu 18.10] [4.18.0-7-generic ] OS
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Interesting that you have no cinder-ceph volume at all from libvirt's
POV.
We no more have to look at/inside the guest (e.g. lsblk).
The breaking point seems to be between openstack and libvirt.
Openstack thinks it has told libvirt to attach the volume
| volumes_attached |
Timo, opened upstream as suggested:
https://bugs.freedesktop.org/show_bug.cgi?id=110511
** Bug watch added: freedesktop.org Bugzilla #110511
https://bugs.freedesktop.org/show_bug.cgi?id=110511
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** 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
** Summary changed:
- linux-snapdragon: -proposed tracker
+ linux-snapdragon: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
** Changed in: kernel-sru-workflow/promote-signing-to-proposed
Status: Fix Released => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822830
Title:
linux-fips: 4.4.0-1008.10 -proposed
Timo, it seems I can install windows 10 on a usb flash for installation. Will
try that.
Ref:
https://www.howtogeek.com/244678/you-dont-need-a-product-key-to-install-and-use-windows-10/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-security
Status: New => Confirmed
** Changed in: kernel-sru-workflow/promote-to-security
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap)
** Changed in: kernel-sru-workflow/promote-to-security
Status: Invalid => New
** Changed in: kernel-sru-workflow/security-signoff
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I am however betting this is not a hw bug due to the way the flickering changed
with the kernel upgrade. Compare the first video posted in this report and now:
https://photos.app.goo.gl/tpmTGWVJXpChoERz6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826385
Title:
ftrace in ubuntu_kernel_selftests hang
Public bug reported:
This issue is a bit strange.
The test has passed with Cosmic 4.18.0-18.19 generic kernel on AMD64
node during our SRU testing process.
https://pastebin.ubuntu.com/p/HN2vN6fCXn/
However, Tyler found that this test will hang after:
[30] Kretprobe dynamic event with maxactive
We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.
Ubuntu 14.04 (trusty) reaches end-of-life today.
Do you still see the bug in a later supported
** Changed in: df-libreoffice
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826052
Title:
[upstream] LibreOffice on Ubuntu 19.04 screws up text paragraph
styling
maybe it would, yes..
anyway, best to file a bug upstream and link it here
** Summary changed:
- Dell XPS 13 9380 flickering (Intel Kaby Lake)
+ Dell XPS 13 9380 flickering (Whiskey Lake)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016
Is this still an issue for anyone in a later Ubuntu release?
** Changed in: hundredpapercuts
Status: Confirmed => Incomplete
** Changed in: totem (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: totem
Status:
Hummm, I have almost zero experience with windows. Is there a windows
version that I can install for free - windows 10 maybe?
Also, if the machine is faulty wouldn't it flicker during BIOS setup as
well?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
This seems to be a duplicate of bug 123054, which means it's fixed, and
the fix will be part of 6.2.4.
*** This bug has been marked as a duplicate of bug 123054 ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Incomplete
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
** 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
** Description changed:
This bug will contain status and test results related to a kernel source
Tested just now (25 April, 10:00 UTC) and a query to the service with
the "geoclue" key returns a valid location. I wonder if someone already
increased the quota for that key and the issue can be considered solved,
or if it's just a lucky coincidence and the daily limit was reset before
I tried.
This bug was fixed in the package shadow - 1:4.2-3.1ubuntu5.4
---
shadow (1:4.2-3.1ubuntu5.4) xenial; urgency=medium
* patches/1012_extrausers_chfn.patch:
- add --extrausers option to "chfn" (LP: #1495580)
* debian/patches/1013_extrausers_deluser.patch:
- add --extrausers
The verification of the Stable Release Update for shadow has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Upstream report is a duplicate of #551365
which was closed "RESOLVED NOTABUG" on 2008-09-09
In new interface the order of buttons does not change when
running Totem full screen so marking this as being fixed.
** Changed in: totem (Ubuntu)
Status: Triaged => Fix Released
--
You received
This bug was fixed in the package shadow - 1:4.2-3.1ubuntu5.4
---
shadow (1:4.2-3.1ubuntu5.4) xenial; urgency=medium
* patches/1012_extrausers_chfn.patch:
- add --extrausers option to "chfn" (LP: #1495580)
* debian/patches/1013_extrausers_deluser.patch:
- add --extrausers
Please excuse the previous post, it's a bug with AutoKey not liking non
alphanumeric abbreviations. Updated abbreviation from "dp:s" (deploy
staging) to "dps" and it works fine now. Just a little FYI for anyone
landing here.
--
You received this bug notification because you are a member of
This bug was fixed in the package numactl - 2.0.11-2.1ubuntu0.1
---
numactl (2.0.11-2.1ubuntu0.1) bionic; urgency=medium
* d/p/lp1817258-Segment-fault-when-numa-nodes-not-sequential-or-cont.patch:
fix segfault on uncommon numa node setups (LP: #1817258)
*
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug will contain
This bug was fixed in the package linux-firmware - 1.173.5
---
linux-firmware (1.173.5) bionic; urgency=medium
* To add power setting bin file for SAR support (QCA6174) (LP: #1817817)
- ath10k: QCA6174 hw3.0: update board-2.bin
* iwlwifi Intel 8265 firmware crashing on
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
This bug was fixed in the package shadow - 1:4.2-3.1ubuntu5.4
---
shadow (1:4.2-3.1ubuntu5.4) xenial; urgency=medium
* patches/1012_extrausers_chfn.patch:
- add --extrausers option to "chfn" (LP: #1495580)
* debian/patches/1013_extrausers_deluser.patch:
- add --extrausers
This bug was fixed in the package linux-firmware - 1.173.5
---
linux-firmware (1.173.5) bionic; urgency=medium
* To add power setting bin file for SAR support (QCA6174) (LP: #1817817)
- ath10k: QCA6174 hw3.0: update board-2.bin
* iwlwifi Intel 8265 firmware crashing on
The verification of the Stable Release Update for numactl has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
This bug was fixed in the package linux-firmware - 1.173.5
---
linux-firmware (1.173.5) bionic; urgency=medium
* To add power setting bin file for SAR support (QCA6174) (LP: #1817817)
- ath10k: QCA6174 hw3.0: update board-2.bin
* iwlwifi Intel 8265 firmware crashing on
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
** Attachment added: "pike-proposed.png"
https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1821896/+attachment/5258947/+files/pike-proposed.png
** Tags removed: verification-pike-needed
** Tags added: verification-pike-done
--
You received this bug notification because you are a member
This bug was fixed in the package numactl - 2.0.11-2.1ubuntu0.1
---
numactl (2.0.11-2.1ubuntu0.1) bionic; urgency=medium
* d/p/lp1817258-Segment-fault-when-numa-nodes-not-sequential-or-cont.patch:
fix segfault on uncommon numa node setups (LP: #1817258)
*
501 - 600 of 815 matches
Mail list logo
