This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
** Changed in: maas
Assignee: Lee Trager (ltrager) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1859656
Title:
[2.6] Unable to reboot s390x KVM machine after initial deploy
Same issue here on ubuntu 21.04, i was wondering why my power emptied
overnight.
❯ sudo cat /sys/power/mem_sleep
[s2idle]
❯ sudo dmesg | grep "suspend entry"
[sudo] password for jeremy:
[ 2739.515120] PM: suspend entry (s2idle)
[22012.050938] PM: suspend entry (s2idle)
--
You received this
It looks like libpam-alreadyloggedin is pulled directly from debian from
the Vcs-Git line so that's why I submitted the fix upstream (still open
and untouched): https://salsa.debian.org/debian/libpam-
alreadyloggedin/-/merge_requests/1
So is libpam-alreadyloggedin now forked from debian and is it
The correct syntax for closing a Launchpad bug report is 'LP: #'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942895
Title:
Build fails on riscv64
To manage notifications about this bug go to:
** Changed in: haproxy (Ubuntu Impish)
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/1940314
Title:
Aug 2021 security update
To manage notifications
The attachment "debdiff_lp1938947_s390-tools_impish.patch" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
The attachment "pocl_debdiff.patch" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and
** Description changed:
GDM 41.alpha can start GNOME wayland sessions when used with the new
NVIDIA drivers 470 which natively support wayland.
It would be good to do proper testing of the new drivers in Impish to
ensure that most of the users can take advantage of the default ubuntu
debdiff for focal
** Description changed:
[Impact]
On Lubuntu systems with more than one sudoer, lxqt-policykit prior to version
0.17.0 crashes due to calling g_object_unref twice on the same object.
[Test Plan]
STEPS TO REPRODUCE
==
1. Boot post-18.04 Lubuntu
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942887
Title:
installing ubuntu 20.04 on vmdk using vmware crashed
To manage notifications about this
** Tags added: focal rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942648
Title:
restart button remains visible in the advanced partitioner after the
bitlocker page is shown
To
Sender: gdm-session-wor
Message: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed.
Priority: 3
I get this error every single time in each boot. And I don't know why.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hui
Was the 5.11.0-34-generic release suppose to have the patch in it?
Thanks
Michael
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935850
Title:
Dell XPS 17 (9710) PCI/internal sound card not
** Description changed:
[Impact]
This netplan SRU contains a backport of the io.netplan.Netplan.Generate()
DBus API, introduced in netplan.io 0.103, that allows calling 'netplan
generate' from within a snap without being blocked by the apparmor
strict-confinement.
[Test Plan]
The
Marking this invalid for maas. As per Adam's comment MAAS streams
(stable, candidate, daily) are GPG signed.
** Changed in: maas
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- A snap, connected to the 'network-setup-control' interface can edit
- files in /etc/netplan/ but it is not able to execute 'netplan generate'
- command successfully.
+ [Impact]
+ This netplan SRU contains a backport of the io.netplan.Netplan.Generate()
DBus API,
--- Comment From boris.m...@de.ibm.com 2021-09-07 11:34 EDT---
Fix released, landed in impish / 21.10, hence closing the bug.
IBM BZ status:->CLOSED
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Public bug reported:
GDM 41.alpha can start GNOME wayland sessions when used with the new
NVIDIA drivers 470 which natively support wayland.
It would be good to do proper testing of the new drivers in Impish to
ensure that most of the users can take advantage of the default ubuntu
desktop
Public bug reported:
Fixing zKVM: Host Key Document Verification - SRU to U20.04LTS
Description:
Fix of genprotimg allowing the tool to verify the validity of IBM Secure
Execution host key documents.
Without that, customers must verify the host key document by themselves,which
is error prone
** Changed in: snapd
Importance: Undecided => Medium
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Status: New => Triaged
** Changed in: snapd (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Also affects: snapd
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873679
Title:
Snap support for non /home homedirs
To manage notifications about
commit was reverted in Focal due to regression. Setting from fix
released -> triaged
** Changed in: linux (Ubuntu Focal)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: bot-stop-nagging
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942902
Title:
Obsolete patch "UBUNTU: SAUCE: ext4: fix directory index node split
corruption"
To manage
Public bug reported:
Since kernel update to 5.11.0-27, nfs is not mounted. I get "mount.nfs:
access denied by server while mounting perso-env.univ-
rennes1.fr:/homedir" error.
If I start with kernel 5.8.0-40 or 5.8.0-55 nfs works fine.
lsb_release -rd
Description:Ubuntu 20.04.3 LTS
Release:
Since 5.13 already landed in impish:
linux-generic | 5.13.0.14.25 | impish
and the patches are also upstream with 5.13,
I'll update the "affects impish" entry as Fix Released
and with that the entire ticket is Fix Released.
** Changed in: linux (Ubuntu Impish)
Status: Fix Committed =>
The backported patches in comments #1 and #2 look reasonable to me. +1
from the security team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928648
Title:
expiring trust anchor compatibility issue
Please find attached a debdiff patch that fixes riscv64 build as seen
here:
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22048127
** Patch added: "pocl_debdiff.patch"
https://bugs.launchpad.net/ubuntu/+source/pocl/+bug/1942895/+attachment/5523518/+files/pocl_debdiff.patch
--
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1942902
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1123.136
---
linux-azure-4.15 (4.15.0-1123.136) bionic; urgency=medium
* bionic/linux-azure-4.15: 4.15.0-1123.136 -proposed tracker (LP:
#1939816)
* VM enter into hung status after triggering a crash (LP: #1882623)
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux-dell300x - 4.15.0-1027.32
---
linux-dell300x (4.15.0-1027.32) bionic; urgency=medium
* bionic/linux-dell300x: 4.15.0-1027.32 -proposed tracker (LP:
#1939817)
* dell300x: rsi wifi and bluetooth crash after suspend and resume
(LP:
This bug was fixed in the package linux - 4.15.0-156.163
---
linux (4.15.0-156.163) bionic; urgency=medium
* bionic/linux: 4.15.0-156.163 -proposed tracker (LP: #1940162)
* linux (LP: #1940564)
- SAUCE: Revert "scsi: core: Cap scsi_host cmd_per_lun at can_queue"
* fails
This bug was fixed in the package linux-azure-5.4 -
5.4.0-1058.60~18.04.1
---
linux-azure-5.4 (5.4.0-1058.60~18.04.1) bionic; urgency=medium
* bionic/linux-azure-5.4: 5.4.0-1058.60~18.04.1 -proposed tracker
(LP: #1942138)
[ Ubuntu: 5.4.0-1058.60 ]
* focal/linux-azure:
** Tags added: sts-sponsor-mfo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942784
Title:
makedumpfile not properly working on focal with 5.11 kernel
To manage notifications about this bug go
Override component to main
libnet-snmp-perl 6.0.1-6 in impish: universe/perl -> main
libnet-snmp-perl 6.0.1-6 in impish amd64: universe/perl/optional/100% -> main
libnet-snmp-perl 6.0.1-6 in impish arm64: universe/perl/optional/100% -> main
libnet-snmp-perl 6.0.1-6 in impish armhf:
** Description changed:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
- UBUNTU: SAUCE: ext4: fix directory index node split corruption
+ UBUNTU: SAUCE: ext4: fix directory index node split corruption
-
Reviewed: https://review.opendev.org/c/openstack/neutron/+/806750
Committed:
https://opendev.org/openstack/neutron/commit/6ac5bc583787b7af6273d5344fcbeef69a48e2e3
Submitter: "Zuul (22348)"
Branch:stable/ussuri
commit 6ac5bc583787b7af6273d5344fcbeef69a48e2e3
Author: Slawek Kaplonski
Date:
I'll evaluate how feasible avocado-framework can be "debianized" for
impish (AKA active devel release), and test.
So that sos4.2 will have the necessary bits for its testing exactly like
upstream does.
Then, I'll review what can be done for stable release. I'm afraid I won't be
able to
Public bug reported:
In order to address https://bugs.launchpad.net/bugs/1933074 the following
SAUCE patch was introduced.
Colin Ian King (1):
UBUNTU: SAUCE: ext4: fix directory index node split corruption
fs/ext4/namei.c | 12 +++-
1 file changed, 7 insertions(+), 5 deletions(-)
pushed to git repo for impish
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f34e9c33209ad9bf3ec807e3b7b9cd22dc8d155d
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[impact]
initial patch for LP: #1938259 was incorrect.
[test case]
this bug is only to revert the previous patch
[regression potential]
any regression would likely be restricted to dell clamshell models
matching the modified config settings
[scope]
the incorrect patch
There are a set of stable release updates pending which will include
this point release - see bug 1941048
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879798
Title:
designate-manage pool update
Public bug reported:
SDCC 4.0.0 has a critical bug involved frame pointers. Compiling with
this version will more than likely cause critical errors on any embedded
application. Anyone installing from the default ubuntu repository would
have no way of knowing this.
The most recent release version
** No longer affects: cloud-utils (Ubuntu Hirsute)
** Also affects: cloud-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu Bionic)
Status: New => Triaged
** Changed in: cloud-utils (Ubuntu Bionic)
Assignee: (unassigned) => Paride
** Summary changed:
- af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B-arm64
+ af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B/F arm64
** Summary changed:
- af_alg07 in crypto / cve-2019-8912 in cve from ubuntu_ltp failed on B/F arm64
+ af_alg07 in
This bug was fixed in the package linux-riscv - 5.11.0-1018.19
---
linux-riscv (5.11.0-1018.19) hirsute; urgency=medium
* hirsute/linux-riscv: 5.11.0-1018.19 -proposed tracker (LP: #1939767)
* Hirsute update: upstream stable patchset 2021-07-28 (LP: #1938340)
- riscv:
This bug was fixed in the package linux-riscv-5.11 -
5.11.0-1018.19~20.04.2
---
linux-riscv-5.11 (5.11.0-1018.19~20.04.2) focal; urgency=medium
* focal/linux-riscv-5.11: 5.11.0-1018.19~20.04.2 -proposed tracker
(LP: #1939766)
[ Ubuntu: 5.11.0-1018.19 ]
*
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
Same here. It works with the 'nosound' parameter.
Weird thing is that it does show the splash screen (logo rotating), but
when it doesn't show the main menu.
I thought it could be a pipewire thing, but don't know for sure. I had
it working on 21.04 when pulseaudio was active, but it could also
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
> We found that Dell Latitude 7420 is not actually fixed, and may cause
Impish to have regression due to the removal of the product name
modalias.
ok, well i guess we have to revert your patch and respin all the
releases then.
please, next time, test your change before things get into -proposed.
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux-azure - 5.11.0-1015.16
---
linux-azure (5.11.0-1015.16) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1015.16 -proposed tracker (LP: #1942116)
* linux-azure: main(): sched_setscheduler(): Operation not permitted
(LP: #1942092)
This bug was fixed in the package linux-azure - 5.4.0-1058.60
---
linux-azure (5.4.0-1058.60) focal; urgency=medium
* focal/linux-azure: 5.4.0-1058.60 -proposed tracker (LP: #1942117)
* linux-azure: main(): sched_setscheduler(): Operation not permitted
(LP: #1942092)
-
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1045.47
---
linux-oem-5.10 (5.10.0-1045.47) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1045.47 -proposed tracker (LP:
#1939806)
* AMDGPU: Fix System hang after resume from suspend (LP: #1940204)
- SAUCE:
This bug was fixed in the package linux - 5.11.0-34.36
---
linux (5.11.0-34.36) hirsute; urgency=medium
* hirsute/linux: 5.11.0-34.36 -proposed tracker (LP: #1941766)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources:
This bug was fixed in the package linux-azure - 5.11.0-1015.16
---
linux-azure (5.11.0-1015.16) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1015.16 -proposed tracker (LP: #1942116)
* linux-azure: main(): sched_setscheduler(): Operation not permitted
(LP: #1942092)
This bug was fixed in the package linux-azure - 5.4.0-1058.60
---
linux-azure (5.4.0-1058.60) focal; urgency=medium
* focal/linux-azure: 5.4.0-1058.60 -proposed tracker (LP: #1942117)
* linux-azure: main(): sched_setscheduler(): Operation not permitted
(LP: #1942092)
-
This bug was fixed in the package linux-azure-5.11 -
5.11.0-1015.16~20.04.1
---
linux-azure-5.11 (5.11.0-1015.16~20.04.1) focal; urgency=medium
* focal/linux-azure-5.11: 5.11.0-1015.16~20.04.1 -proposed tracker
(LP: #1942125)
[ Ubuntu: 5.11.0-1015.16 ]
*
Is it possible to bisect the kernel to find the regression?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942377
Title:
Linux 5.14/4.13.14 fails to boot
To manage notifications about this bug go
Public bug reported:
Ubuntu release: hirsute/impish
pocl gets the host machine cache line size using
getconf(LEVEL1_DCACHE_LINESIZE) and when this value is not defined by
the underlying architecture, glibc returns 0 which is correctly handled
by pocl CMakeLists.txt. But riscv64 defines this
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
This bug was fixed in the package linux - 5.4.0-84.94
---
linux (5.4.0-84.94) focal; urgency=medium
* focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)
* Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
- Revert "ACPI: resources: Add
201 - 300 of 432 matches
Mail list logo