Public bug reported:
The starfive and laptop kernels are obsolete, on mantic release version
still, and should be removed per discussion with kernel team on
Mattermost.
$ reverse-depends src:linux-starfive # some reverse-depends bug
$ reverse-depends src:linux-laptop
No reverse dependencies
Uploaded procps with the file; leaving gamemode task open because maybe
dynamic enhancements there still make some sense in 24.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2057792
I'm agreeing with desktop in following Fedora to bump to 1048576, the
precedence makes this safe, and this I consider this a bug fix for
crashing software and not a feature request.
** Changed in: procps (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Status:
Subscribing Canonical desktop team to get their input.
Basically the ask is to ship this file:
https://src.fedoraproject.org/rpms/systemd/blob/f39/f/10-map-count.conf
I believe if we do it should be shipped in procps; or possibly, gamemode
should set that option?
** Also affects: procps
Oh but please don't use `[trusted=yes]`, just add the repository with
add-apt-repository ppa:ubuntu-uefi-team/backports-build.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2051999
There doesn't seem to be anything to sponsor here, so I'm unsubscribing
ubuntu-sponsors. Please make sure to keep your ubuntu-sponsors
subscriptions current so we don't waste time in complex multi package
bugs trying to figure out if there's anything to do for us.
--
You received this bug
Waiting for 6.5.13 to actually build but on 6.6.0-14 from proposed now
which is based on 6.6.3 which probably has all the fancy patches too
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
These ones I don't remember seeing before:
[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed to initialize parser -125!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045899
Title:
More
I saw similar messages in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032386 but that
only caused hangs and not block the entire desktop (and Firefox is good
now so I don't know)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "OlderDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045899/+attachment/5727266/+files/OlderDmesg.txt
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Public bug reported:
I think running the Mattermost snap forced to Wayland rendering
*eventually* seems to crash amdgpu, it recovers at the kernel level but
the GUI doesn't actually recover and I also can switch tty with the
keyboard.
I have attached the two crashes from yesterday, they look
Unsubscribing ubuntu-sponsors, please resubscribe when you have new
debdiff(s).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2042902
Title:
ucm2: soundwire: add rt713 SDCA
update-initramfs -c call by kernel postinst hook is not covered, but we
need to make sure the initramfs is there at kernel configuration point
because we need it to be there when updating boot loaders.
e.g. if we triggered both in that case, update-grub could run before
update-initramfs.
if we
Draft fix for update-grub: https://salsa.debian.org/grub-
team/grub/-/merge_requests/46
Still need to take care of grub-install at some point, haven't figured
out the best approach there yet.
** Changed in: grub2 (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Chan
@Andy I'm unassigning you and changing the bug status as the initramfs
part has been resolved, update-initramfs does
if [ -n "$DPKG_MAINTSCRIPT_PACKAGE" ] && [ $# = 1 ] && [ "$1" = -u ]; then
if dpkg-trigger --no-await update-initramfs; then
** Tags removed: rls-jj-incoming
** Tags added: foundations-todo
** Changed in: systemd (Ubuntu Jammy)
Assignee: (unassigned) => Nick Rosbrook (enr0n)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags removed: rls-mm-incoming
** Changed in: systemd (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2036968
Title:
Mantic minimized/minimal
** Also affects: grub2 (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2-unsigned (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: grub2 (Ubuntu Jammy)
Another occurence in latest boot.
Actually the same call chain it seems.
** Attachment added: "Dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5700876/+files/Dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages,
FWIW, this was after this morning's UEFI firmware update.
Devices that have been updated successfully:
• Battery (1.1.6 →
Public bug reported:
I was locking my screen, so my gnome-shell got killed
(https://bugs.launchpad.net/ubuntu/+bug/2034619) but this time I logged
in again and opened firefox and then everything froze except cursor and
magic sysrq.
(Of course after sysrq-b I rebooted and my USB hub failed to
Complete journal from 15:40 to 16:00
** Attachment added: "JournalAt1540To1600.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2035028/+attachment/5699730/+files/JournalAt1540To1600.log
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
In 6.5.0-4-generic, tried switching Momentum 4 wireless headphones
between headset and handsfree profiles and I think also ended up cycling
it on/off, causing a kernel bug in the memory management.
Sep 08 15:54:45 jak-t14-g3 kernel: [ cut here ]
Sep
There doesn't appear to be anything to sponsor here (yet?), so
unsubscribing ubuntu-sponsors. You may resubscribe once there's a
debdiff that needs sponsoring by us.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
Right so it seems we forgot to bump the size requirements in ubuntu-
release-upgrader when bumping them in the installer in bug 1959971, you
probably should not have been able to upgrade. Albeit the size it seems
is determined from the initramfs that is in /boot.
We also don't seem to acccount
** Also affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- APT installs 3 kernels at once so /boot runs out of free space left and
partition size does not increase alongside with newer ubuntu versions
+ Bump minimum /boot size in
We generally don't know how much space is going to be needed. APT only
keeps 2 kernel versions around, and the /boot partition is sized
accordingly for 3.
If you override this by marking kernels as manually installed, or
manually installing other versions you need to ensure that there is
enough
** Changed in: thermald (Ubuntu Jammy)
Status: Incomplete => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1995606
Title:
Upgrade thermald to 2.5.1 for Jammy (22.04)
The bug description does not match the requirements for an SRU,
particularly "low" is no reasonable answer to "where problems could
occur"
** Changed in: thermald (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Kernel
Unsubscribing ubuntu-sponsors as this seems done except for this
firmware-sof kinetic tag which is New and I hereby mark Incomplete as
it's not clear if there's anything left to do there to me
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Unsubscribing ubuntu-sponsors as this seems done except for this
firmware-sof kinetic tag which is New and I hereby mark Incomplete as
it's not clear if there's anything left to do there to me
** Changed in: firmware-sof (Ubuntu Kinetic)
Status: New => Incomplete
--
You received this
I don't see anything sponsorable for backport-iwlwifi-dkms/focal and the
other tasks are in various done states, so I am going to mark this task
Incomplete and unsubscribe ubuntu sponsors.
** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
Status: New => Incomplete
--
You received this
Unsubscribing Ubuntu Sponsors, as this issue seems to be fairly complex
and the patch seems controversial and incomplete.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to libatasmart in Ubuntu.
https://bugs.launchpad.net/bugs/1581594
*** This bug is a duplicate of bug 1936857 ***
https://bugs.launchpad.net/bugs/1936857
** This bug has been marked a duplicate of bug 1936857
grub-install: error: efibootmgr: not found.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
I'm going to set this to Won't Fix because that seems to be an important
part of the solver logic, and the workarounds - running upgrade first,
or using ubuntu-drivers - are easy to do and the potential for
regression significantly outweighs them.
This will get solved eventually by a nicer solver
** Changed in: apt (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not install
I think we debugged this recently but I'm not sure where the end result
of this is that we do not mark packages for removal that have an upgrade
available, hence we end up without a removal request after the first
stage solver, and the Conflicts solver that runs after can't solve that.
--
You
Reproduced issue and dumped test case into https://salsa.debian.org/apt-
team/apt-tests/-/blob/main/edsp/fail-ubuntu-1992513.edsp.log for future
analysis when doing solver work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not install nvidia-driver-470-server if nvidia-
Please decide whether you are reporting a missing sound driver or the
grub-install crash, you can't put two bugs into one report.
Regarding the grub crash it's curious but an issue in the firmware
variable handling, not grub.
** Package changed: grub2-signed (Ubuntu) => linux (Ubuntu)
**
Actually let me reassign to Linux and mark incomplete.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2007286
Title:
Ubuntu does not clean out old kernel module files (in /lib/modules)
There can be many reasons why files remain. Did you purge the packages
for those Linux versions? Did you do any dkms modules.
This is not a bug in apt, apt is not responsible for those files.
** Changed in: apt (Ubuntu)
Status: New => Invalid
** Package changed: apt (Ubuntu) => linux
This fix will be included in grub2-unsigned/2.06-2ubuntu14.1 for
kinetic, jammy, focal, bionic. Binaries have been built in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
for kinetic.
Signing request: https://answers.launchpad.net/canonical-signing-
jobs/+question/704589
The entire upload will be uploaded to all older releases but we do have
a security upload already in the unapproved queues that should go out
first, but that needs approving those first, them passing the SRU
verification, a resigning against the new signing key the new shim
needs, and finally
The term you're looking for is workaround, not triage or fixes. Triage
is the process of understanding the bug and marking it the correct
things.
Not using the same language as everyone else and writing very long
comments makes it hard to understand.
First I thought you reported an out of memory
Hi ybdjkfd I don't really understand what you are doing and how it's
relevant. This issue should be fixed in lunar-proposed 2.06-2ubuntu16,
please only add comments if you have meaningful insights regarding the
verification of that update.
--
You received this bug notification because you are a
** Changed in: grub2-unsigned (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: grub2-signed (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I see it was marked Fix released for linux (Ubuntu), however it's not
actually fixed in lunar, not even the update from kinetic-proposed has
been copied up to lunar-proposed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17
I have now picked all the rhboot patches in 2.06-2ubuntu16~ppa1 in
https://launchpad.net/~ubuntu-uefi-team/+archive/ubuntu/ppa/+packages
and will boot that before uploading to the archive.
This *should* allow initrds over 4GB but obviously bugs could be there.
The important bit is that we are now
I think kernel team needs patch sent to ML, but I don't do a lot of
kernel stuff. FWIW, here's the log from 6.1-rc5 which includes the fix:
Nov 29 20:03:28 jak-t14-g3 kernel: PM: suspend exit
Nov 29 20:03:28 jak-t14-g3 kernel: ath11k_pci :02:00.0: BAR 0: assigned
[mem 0x8000-0x801f
Dear kernel bot, this bug has enough info, and there's a patch upstream
that's part of 6.1 that fixes the issue.
Though I can say I now hit a failure to restart the device / load
firmware after a 2nd resume.
This is likely another race; if you just suspend by echo mem >
/sys/power/state in a
@Craig The limit in Debian is actually much lower than in Ubuntu even,
but fixing it there is even harder as that misses a lot more patches.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Well surely not more than the past year, this is not a new bug after
all, the regression was introduced with the initial boothole update when
we did the one grub split.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in
Actions: cherry-pick two patches for kinetic and upload new upstream
release to lunar.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990964
Title:
FTBFS on kinetic
Status in linux
** Changed in: grub2-signed (Ubuntu Bionic)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: grub2-signed (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: grub2-unsigned (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
** Changed in: grub2-signed (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Kernel
Packages,
** Tags added: fr-2934
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Really the workaround is to set MODULES=dep in /etc/initramfs-
tools/initramfs.conf, this yields a much smaller initramfs (but you
can't take out the disk and boot it in another machine), disabling
secure boot or sgx should not be doing anything.
** Also affects: grub2-unsigned (Ubuntu)
** Tags removed: foundations-triage-discuss
** Tags added: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1992513
Title:
apt will not
It does yeah, and obviously that's a solver bug that's going to need
some more work to root cause.
** Changed in: apt (Ubuntu)
Status: Incomplete => Triaged
** Changed in: apt (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
** Changed in: grub2-signed (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1991676
Title:
Package grub-efi-arm64-signed
On my kinetic system, /dev has nosuid, but no noexec.
** Tags added: foundations-triage-discuss
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1991975
Title:
dev file system is mounted
Is there anything left to do here?
** Changed in: klibc (Ubuntu Bionic)
Status: New => Incomplete
** Changed in: klibc (Ubuntu Cosmic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
OK the patch set here is broken, we gotta do this from scratch properly.
So I'm going to start cherry picking the rhboot patches for memory
management. I have applied so far from bug 1989446 the backport of "Try
to pick better locations for kernel and initrd" and cherry-picked from
rhboot the
Our goal should be to merge the entire patch series into kinetic, worst
case, kinetic will not be installable for some users. This means we will
have decent results from people trying that in the next 4 weeks (by Oct
27 the release has been out 1 week).
In the meantime, next week we should push
@jeremyszu (os369510) Did you see #90, it seems your patch would cause
boot failures on older system unable to handle this memory range.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
We believe the kernel handles RAs itself, adding a task for it.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: dpkg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1984203
Title:
/var/run/reboot-required not created after installing new kernel
Yes, grub will be fixed eventually, but we are blocked by the security
update not being out yet. This is not a blocker for enabling upgrades to
22.04.1, as it only affects a small number of systems and grub fixes
itself by using the previous kernel version if the new one fails.
--
You received
*** This bug is a duplicate of bug 1842320 ***
https://bugs.launchpad.net/bugs/1842320
** This bug has been marked a duplicate of bug 1842320
Out of Memory on boot with 5.2.0 kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Here's the 5.15 log, the 5.19 one was attached by apport as
CurrentDmesg.txt already.
** Attachment added: "dmesg-5.15.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981449/+attachment/5602675/+files/dmesg-5.15.txt
** Changed in: linux (Ubuntu)
Status: Incomplete =>
There seems to be an invalid hash presented in MokX, it fails to import
that and then doesn't load MokX (which seems reasonable). I need to
recheck with 5.15 if it still boots, maybe firmware got corrupted or
something (or 5.19 loads the key from the wrong place).
$ mokutil --list-enrolled --mokx
In case you wonder: Yes I have the ubuntu UEFI PPA key in db as I needed
to test out shims signed from there :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1981449
Title:
5.19 kernel
In the logs I see different values for MOKvar from efi: so maybe it's
calculating something wrongly (or it's just not that stable).
jak@jak-t480s:~:master$ journalctl -k | grep MOK -i
Jul 12 15:14:51 jak-t480s kernel: efi: TPMFinalLog=0xbb592000 SMBIOS=0xba693000
SMBIOS 3.0=0xba69
Public bug reported:
The 5.19 kernel only reads the db and dbx keys:
jak@jak-t480s:~:master$ journalctl -b -1 -k | grep integrity
Jul 09 21:34:14 jak-t480s kernel: integrity: Platform Keyring initialized
Jul 09 21:34:14 jak-t480s kernel: integrity: Machine keyring initialized
Jul 09 21:34:14
You didn't remove all the 177 packages, the headers package or so pulls
in a kernel and then apt switches to the unsigned one.
I'm going to reassign this to Linux, as we should ensure that doesn't
happen by not allowing unsigned to satisfy those dependencies.
** Package changed: grub2-signed
nds on the value of
LC_COLLATE/LANG
Status in grub2 package in Ubuntu:
New
Bug description:
Hi,
As discussed with Julian Andres Klode on IRC, there are cases where the value
of grub-efi/install_devices is affected by the value of LC_COLLATE.
This is caused by this unique sort: ht
** No longer affects: grub2-unsigned (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm iso pxe boot kernel panic on Ampere Mt. Jade
Status
Though maybe you also need to unapply efi-implemented-LoadFile2-initrd-
loading-protocol-fo.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967562
Title:
jammy beta (220330) arm
To figure out if it's the new loader code, remove efi-implement-
grub_efi_run_image.patch (or the grub-core/loader/efi/linux.c hunk) or
enable secure boot (if available). The new code path on insecure systems
uses the upstream loader + LoadFile2 support, as is necessary for
RISC-V.
--
You
Ping! Releasing with broken WiFi after suspend & resume, with patches
lying around for over a month, feels like a disservice to our users.
** Tags added: rls-jj-incoming
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Confirmed =>
Will we see these fixes cherry-picked in a 5.15.0-24 kernel or so soon?
The linux-firmware package has been ready for a while now with the new
firmware
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Package changed: grub2 (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1964626
Title:
Unable to launch 5.15.0-22-generic kernel (or its recovery mode)
Hi, this works, yes. Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1962471
Title:
iwlwifi fails after suspend (Failed to start RT ucode: -110)
Status in linux package in
*** This bug is a duplicate of bug 1962471 ***
https://bugs.launchpad.net/bugs/1962471
** This bug has been marked a duplicate of bug 1962471
iwlwifi fails after suspend (Failed to start RT ucode: -110)
--
You received this bug notification because you are a member of Kernel
Packages,
** Description changed:
See attachments.
- This is a regression from earlier kernel versions which worked fine.
+ This is a regression from earlier kernel versions which worked fine, but
+ I don't know at which point precisely it broke - with 5.15 perhaps?
+ Laptop was running 24/7 mostly in
Public bug reported:
See attachments.
This is a regression from earlier kernel versions which worked fine.
It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
concrete product number)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
Dmesg with failure
** Attachment added: "LastBoot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1962472/+attachment/5564171/+files/LastBoot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
See attachments.
This is a regression from earlier kernel versions which worked fine.
It's a ThinkPad T480s upgraded with an AX210 or AX211 (don't have
concrete product number)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-22-generic 5.15.0-22.22
My side question is what prevents arm64 from having the amd64 approach
where AFAIUI the image is compressed but starts with a small stub that
decompresses it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
Compressed kernel images were introduced in bug 1384955 to work around
some limits on old u-boot systems. This in turn broke grub-check-
signatures, meaning that while cloud images booted in secure boot, you
could not upgrade grub or install new kernels on secure systems as
Public bug reported:
system failed to suspend, see attached logs
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-19-generic 5.13.0-19.19
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode
Various dkms weirdness
"Error! The module acpi-call 1.1.0 is not currently installed."
But there are also like 3 services failing to start in the log, so maybe
the system is just misconfigured somewhere that affects all of them.
The bug also indicates that EFI variables are not supported by the
** Package changed: shim-signed (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1941963
Title:
package shim-signed 1.40.7+15.4-0ubuntu9 failed to
There are three possible causes
- firmware bug
- kernel bug
- user error (read-only variables), though why does that give I/O rather than
ENOSPACE
I'm going to reassign this one to linux for a check on the kernel side,
but I suspect it's a firmware issue.
** Package changed: shim-signed
cpu-checker (0.7-1.2) experimental; urgency=medium
will be synced shortly with those changes
** Changed in: cpu-checker (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to cpu-checker in Ubuntu.
Yes, of course if you don't install the fixed version you still have the
broken one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
https://bugs.launchpad.net/bugs/1923150
Title:
unexpected error
Marking the packaging tags as invalid, as the bug is fixed in apt 2.0.4
which is in the 20.04.2 images. This bug was tracked as bug 1871268 back
when it was being fixed.
** Changed in: apt (Ubuntu)
Status: Incomplete => Invalid
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
I mean 2.0.4, of course, which is included in the current LTS images
(20.04.2); your image is the previous version (20.04.1)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in Ubuntu.
It seems you are not using libapt-pkg6.0 in version 2.1.10ubuntu0.2 or
later? This issue was fixed in that version.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
1 - 100 of 299 matches
Mail list logo
