intramfs Failed: ZSTD-compressed data

[Marc Püschel]

The current updates of Ubuntu 22.04.2 LTS results on boot (black screen) the message "not enough memory, press any key" and after comes any others "error messages" too and then Ubuntu starts!

Maybe this Bug results from the current AMD Kernel Updates on "modern" Prozessors or Update for the Grub or something - i'don't know - there are many System-Updates yesterday and all comes over Ubuntu Store as package

# lsb_release -rd
Description: Ubuntu 22.04.2 LTS
Release: 22.04

# dpkg -l | grep init
ii busybox-initramfs 1:1.30.1-7ubuntu3 amd64 Standalone shell setup for initramfs
ii gnome-initial-setup 42.0.1-1ubuntu2.3 amd64 Initial GNOME system setup helper
ii init 1.62 amd64 metapackage ensuring an init system is installed
ii init-system-helpers 1.62 all helper tools for all init systems
ii initramfs-tools 0.140ubuntu13.1 all generic modular initramfs generator (automation)
ii initramfs-tools-bin 0.140ubuntu13.1 amd64 binaries used by initramfs-tools
ii initramfs-tools-core 0.140ubuntu13.1 all generic modular initramfs generator (core tools)
ii libatopology2:amd64 1.2.6.1-1ubuntu1 amd64 shared library for handling ALSA topology definitions
ii libklibc:amd64 2.0.10-4 amd64 minimal libc subset for use with initramfs
ii lsb-base 11.1.0ubuntu4 all Linux Standard Base init script functionality
ii ncurses-base 6.3-2 all basic terminal type definitions
ii sysvinit-utils 3.01-1ubuntu1 amd64 System-V-like utilities
ii xinit 1.4.1-0ubuntu4 amd64 X server initialisation tool

# dpkg -l | grep zfs
-> brings no information here

# zfs list
-> zfs is not installed here

if you need more system-infos to solve this Bug, please let me know!
The first error means "Not Enough Memory, Please press any key" - you can press any key (but you don't need) and it comes the "intramfs Failed: ZSTD-compressed data ..." and then the Ubuntu Login screen comes up.

Please be patient with me, I'm new to Ubuntu and Launchpad and don't know much about it yet

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/2007743/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Marc Püschel (newcomer-01)]

hope i sort this bug right

[Steve Langasek (vorlon)]

initramfs-tools-ubuntu-core is a package specific to the boot of Ubuntu Core, so unrelated to your issue.

Reassigning to initramfs-tools, which is at least a package that you have installed.

Why does your bug report title mention the use of zstd?

[Marc Püschel (newcomer-01)]

now why the Error message exact this say before Ubuntu starts finally

[Julian Andres Klode (juliank)]

Please include the exact error messages and when they occur, as well as the grub version.

Are you on the latest grub update already (ends in ubuntu14.1)? This includes a lot of fixes for out of memory issues. If not try to upgrade using apt install grub-efi-amd64-signed (apt upgrade might not yet install it due to phasing) and see if that helps.

If you are and it worked before, thanks for letting us know. We are aware of bugs (and fixes for them) in those memory fixes in 14.1 but since those have been tested in lunar for weeks now with no report of issues we decided to roll them out anyway as it fixes booting for the majority and the follow-up patches carry additional regression risks if we push them in without testing.

[Marc Püschel (newcomer-01)]

sorry, this goes too fast (on boot up in the black screen), today I wanted to take a photo of it but i'm too slow.
How can i get in Terminal the current grub version?
grub --version don't work.
And a special boot-error.log i can't find ...

[Marc Püschel (newcomer-01)]

and yes, with the last (current) update comes some grub updates for AMD and now i run in this error

[Marc Püschel (newcomer-01)]

and "Not enough Memory" can't be true, i have 16 GB RAM!

[Marc Püschel (newcomer-01)]

if it helps:

- AMD® Ryzen 5 2400g with radeon vega graphics × 8
- Mainboard is from MSI
- 64 Bit System
- 1 TB SSD-HDD
- Gnome 42.5

[Marc Püschel (newcomer-01)]

is there an command for Terminal to get the latest System updates Details?

[Marc Püschel (newcomer-01)]

ah!

Here

# grub-install --version
grub-install (GRUB) 2.06-2ubuntu7.1

is it this what you mean? Or is there another command in terminal?

[Marc Püschel (newcomer-01)]

why grub-install --version
grub-install (GRUB) 2.06-2ubuntu7.1

says that i have ubuntu7.1 i don't know, i mean to remember, that with the last update i have seen something with ubuntu14.1

[Marc Püschel (newcomer-01)]

so this is what i get when i try to install

# sudo apt-get install grub-efi-amd64-signed

Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
grub-efi-amd64-signed ist schon die neueste Version (1.187.3~22.04.1+2.06-2ubuntu14.1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

Seems that i am already on the newest grub!

[Marc Püschel (newcomer-01)]

@juliank and now?

[Marc Püschel (newcomer-01)]

@juliank do you mean that this bug is addressed from grub? Yesterday comes up some updates in this package over the Ubuntu Software Center ...

[Marc Püschel (newcomer-01)]

doe's this help?

# grep BOOT /var/log/syslog

Feb 12 20:51:51 newcomer01-MS-7A40 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 12 20:51:51 newcomer01-MS-7A40 kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 12 20:51:51 newcomer01-MS-7A40 kernel: [ 0.000000] Unknown kernel command line parameters "splash BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic", will be passed to user space.
Feb 12 20:51:51 newcomer01-MS-7A40 kernel: [ 0.694284] BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic
Feb 13 07:54:28 newcomer01-MS-7A40 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 13 07:54:28 newcomer01-MS-7A40 kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 13 07:54:28 newcomer01-MS-7A40 kernel: [ 0.000000] Unknown kernel command line parameters "splash BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic", will be passed to user space.
Feb 13 07:54:28 newcomer01-MS-7A40 kernel: [ 0.691816] BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic
Feb 13 19:25:30 newcomer01-MS-7A40 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 13 19:25:30 newcomer01-MS-7A40 kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 13 19:25:30 newcomer01-MS-7A40 kernel: [ 0.000000] Unknown kernel command line parameters "splash BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic", will be passed to user space.
Feb 13 19:25:30 newcomer01-MS-7A40 kernel: [ 0.651217] BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic
Feb 14 08:17:55 newcomer01-MS-7A40 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 14 08:17:55 newcomer01-MS-7A40 kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 14 08:17:55 newcomer01-MS-7A40 kernel: [ 0.000000] Unknown kernel command line parameters "splash BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic", will be passed to user space.
Feb 14 08:17:55 newcomer01-MS-7A40 kernel: [ 0.648228] BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic
Feb 15 08:37:10 newcomer01-MS-7A40 kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 15 08:37:10 newcomer01-MS-7A40 kernel: [ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=e1dad91c-4856-4394-a1fd-f440e57524c1 ro quiet splash vt.handoff=7
Feb 15 08:37:10 newcomer01-MS-7A40 kernel: [ 0.000000] Unknown ke...

[Marc Püschel (newcomer-01)]

i see here some "Unknown Kernel command line parameter" Messages ...

[Marc Püschel (newcomer-01)]

i have now checked other syslogs too, but this messages are longer and come's not first with the last update

[Marc Püschel (newcomer-01)]

now i get it!

# grep unpack /var/log/syslog

Feb 12 20:51:51 newcomer01-MS-7A40 kernel: [ 0.215552] Trying to unpack rootfs image as initramfs...
Feb 13 07:54:28 newcomer01-MS-7A40 kernel: [ 0.215715] Trying to unpack rootfs image as initramfs...
Feb 13 19:25:30 newcomer01-MS-7A40 kernel: [ 0.215555] Trying to unpack rootfs image as initramfs...
Feb 14 08:17:55 newcomer01-MS-7A40 kernel: [ 0.215822] Trying to unpack rootfs image as initramfs...
Feb 15 08:37:10 newcomer01-MS-7A40 kernel: [ 0.215801] Trying to unpack rootfs image as initramfs...
Feb 15 09:13:22 newcomer01-MS-7A40 kernel: [ 0.215775] Trying to unpack rootfs image as initramfs...
Feb 16 08:06:10 newcomer01-MS-7A40 kernel: [ 0.215914] Trying to unpack rootfs image as initramfs...
Feb 16 10:55:07 newcomer01-MS-7A40 kernel: [ 0.200350] Trying to unpack rootfs image as initramfs...
Feb 17 08:35:47 newcomer01-MS-7A40 kernel: [ 0.200254] Trying to unpack rootfs image as initramfs...
Feb 17 21:02:15 newcomer01-MS-7A40 kernel: [ 0.200051] Trying to unpack rootfs image as initramfs...
Feb 17 21:02:15 newcomer01-MS-7A40 kernel: [ 0.550924] Initramfs unpacking failed: ZSTD-compressed data is corrupt
Feb 17 21:03:12 newcomer01-MS-7A40 kernel: [ 0.200047] Trying to unpack rootfs image as initramfs...
Feb 17 21:03:12 newcomer01-MS-7A40 kernel: [ 0.550927] Initramfs unpacking failed: ZSTD-compressed data is corrupt
Feb 18 08:50:34 newcomer01-MS-7A40 kernel: [ 0.199951] Trying to unpack rootfs image as initramfs...
Feb 18 08:50:34 newcomer01-MS-7A40 kernel: [ 0.537730] Initramfs unpacking failed: ZSTD-compressed data is corrupt

[Marc Püschel (newcomer-01)]

see:

Feb 18 08:50:34 newcomer01-MS-7A40 kernel: [ 0.199951] Trying to unpack rootfs image as initramfs...
Feb 18 08:50:34 newcomer01-MS-7A40 kernel: [ 0.537730] Initramfs unpacking failed: ZSTD-compressed data is corrupt

[Marc Püschel (newcomer-01)]

oh no, so sorry!!!

# grep error /var/log/syslog

ONLY FROM TODAY!

Feb 18 08:50:34 newcomer01-MS-7A40 systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.
Feb 18 08:50:34 newcomer01-MS-7A40 systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) being skipped.
Feb 18 08:50:36 newcomer01-MS-7A40 gnome-session[1233]: gnome-session-binary[1233]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 18 08:50:36 newcomer01-MS-7A40 gnome-session-binary[1233]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 18 08:50:36 newcomer01-MS-7A40 gnome-session-binary[1233]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 18 08:50:36 newcomer01-MS-7A40 gnome-session[1233]: gnome-session-binary[1233]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 18 08:50:36 newcomer01-MS-7A40 canonical-livepatch.canonical-livepatchd[915]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/f9a21732b35c4a78a2874423734709a2/updates" failed, retrying in 30s.
Feb 18 08:50:40 newcomer01-MS-7A40 hpfax: [1662]: error: Failed to create /var/spool/cups/tmp/.hplip
Feb 18 08:50:49 newcomer01-MS-7A40 tracker-miner-f[1874]: SQLite error: database disk image is malformed (errno: Erfolg)
Feb 18 08:50:49 newcomer01-MS-7A40 tracker-miner-f[1874]: message repeated 5 times: [ SQLite error: database disk image is malformed (errno: Erfolg)]
Feb 18 08:50:50 newcomer01-MS-7A40 gnome-software[2230]: not handling error failed for action refresh: E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy/InRelease #012E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease #012E: Fehlschlag beim Holen von http://de.archive.ubuntu.com/ubuntu/dists/jammy-backports/InRelease #012E: Fehlschlag beim Holen von http://security.ubuntu.com/ubuntu/dists/jammy-security/InRelease #012E: Fehlschlag beim Holen von https://dl.cloudsmith.io/public/balena/etcher/deb/ubuntu/dists/jammy/InRelease #012E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/linuxuprising/apps/ubuntu/dists/jammy/InRelease #012E: Fehlschlag beim Holen von https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu/dists/jammy/InRelease #012E: Fehlschlag beim Holen von https://deb.opera.com/opera-stable/dists/stable/InRelease #012E: Fehlschlag beim Holen von https://linux.teamviewer.com/deb/dists/stable/InRelease #012E: Fehlschlag beim Holen von https://esm.ubuntu.com/apps/ubuntu/dists/jammy-apps-security/InRelease #012E: Fehlschlag beim Holen von https://esm.ubuntu.com/apps/ubuntu/dists/jammy-apps-updates/InRelease #012E: Fehlschlag beim Holen von https://esm.ubuntu.com/infra/ubuntu/dists/jammy-infra-security/InRelease #012E: Fehlschlag beim Holen von https://esm.ubuntu.com/infra/ubuntu/dists/jammy-infra-updates/InRelease #012E: Einige Indexdateien konnten nicht heruntergeladen werden. Sie wurden ignoriert oder alte an ihrer Stell...

[Marc Püschel (newcomer-01)]

I can't send as further error log entries (there are really a lot of!), please tell me what exactly you need to fix the BUGS as soon as possible!

[Marc Püschel (newcomer-01)]

maybe you should set the importance to CRITICAL and maybe push a roll-back

[Julian Andres Klode (juliank)]

I cannot find any "Not Enough Memory" on codesearch.debian.net. I know grub says "out of memory" and AFAIK doesn't ask you to press a key so it's still not clear where you see an error, sorry. Are you sure the message is absolutely identical character by character?

None of the syslog should be relevant here that's way later.

[Julian Andres Klode (juliank)]

Ah I do see ZSTD-compressed data is corrupt in the log, what do you see when you run update-initramfs -u? Any errors? Does it work after running that?

[Julian Andres Klode (juliank)]

Also you see other errors from e.g. your tracker database indicating that filesystem is corrupt. Maybe your hard disk is failing.

[Marc Püschel (newcomer-01)]

when i run

# sudo update-initramfs -u

update-initramfs: Generating /boot/initrd.img-5.19.0-32-generic
I: The initramfs will attempt to resume from /dev/nvme0n1p2
I: (UUID=960398a5-4f66-4d5c-bf25-e3e6389fa930)
I: Set the RESUME variable to override this.

my ssd is failing? On a "new" and relative new installed Ubuntu LTS?

"Not enough Memory" is my translation, i got a similar message in german

[Marc Püschel (newcomer-01)]

sudo update-initramfs -u

don't solve the issue that i never had before the update yesterday!

Here the exact message:

1.)

Fehler: Nicht genügend Speicher.
Beliebige Taste drücken, um fortzusetzen ...

2.) dann folgt
[ 0.550872] Initramfs unpacking failed: ZSTD-compressed data is corrupt
/scripts/local-premount/resume: line 73: wait-for-root: not found
/init: line 73: wait-for-root: not found

[Marc Püschel (newcomer-01)]

"Nicht genügend Speicher" can't be true, 16 GB RAM

https://abload.de/img/bildschirmfotovom202373c43.png

and here GParted:

https://abload.de/img/bildschirmfotovom20238mddm.png

[Marc Püschel (newcomer-01)]

Message 1
-> sorry, little out of focus

https://abload.de/img/img20230218172247hudjk.jpg

Message 2

https://abload.de/img/img20230218172257pvc4f.jpg

after that, the Ubuntu Login Screen comes normally up and i can Login

[Marc Püschel (newcomer-01)]

and you can believe me, all these errors mentioned here, I had before the update yesterday definitely not!

had even just two or three weeks ago Ubuntu 22.04.1 (from a USB-Stick) reinstalled incl. rebuild all of the partition tables

what now?

[Marc Püschel (newcomer-01)]

if you ask me, the current updates should not have been published, apparently there are special cases, like mine, which were not considered - can happen. Is also no reproach!

[Marc Püschel (newcomer-01)]

any news or updates here? i need a fix please.

[Marc Püschel (newcomer-01)]

i have a friend who has exactly the same PC with exactly the same hardware and exactly identical Ubuntu, i advised him not to do the system update, otherwise he will also get this error, i am quite sure.

I can't be the only one with this error ...

[Julian Andres Klode (juliank)]

The update has only been rolled out to 25% of users yet. We cannot revert the update as the "out of memory" fixes are necessary for booting on OEM hardware with 4K screens and need to be in 22.04.2 images. I'm checking if we can halt updates to existing systems.

There always is some risk, equally the old grub binaries can run out of memory and fail to boot if you install nvidia modules, for example.

Please try to downgrade to the old grub version, the debs are:

https://launchpad.net/~canonical-signing/+archive/ubuntu/primary-2022v1/+build/25476437/+files/grub-efi-amd64-signed_1.187.2+2.06-2ubuntu14_amd64.deb

https://launchpad.net/~ubuntu-security-embargoed-shared/+archive/ubuntu/grub2/+build/24848125/+files/grub-efi-amd64-bin_2.06-2ubuntu14_amd64.deb

as linked from

https://launchpad.net/ubuntu/+source/grub2-signed/1.187.2
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.06-2ubuntu14

I'll provide a version with additional patches later this week in a PPA which you can test.

[Julian Andres Klode (juliank)]

But just to be clear, you are saying the error is at least non-fatal and it continues booting just fine with one error, so it's not world ending bad but more a usability issue right now.

[Marc Püschel (newcomer-01)]

well there are some graphic errors and my whole System is "slow" because of that!
I got some errors in syslog with this "information".

Since this Update my error logs are really full!

See this:

Feb 19 15:38:12 newcomer01-MS-7A40 update-notifier-crash[21860]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Feb 19 15:38:12 newcomer01-MS-7A40 update-notifier-crash[21927]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
Feb 19 15:38:13 newcomer01-MS-7A40 update-notifier-crash[21996]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)

Feb 19 11:17:17 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: client bug: event processing lagging behind by 26ms, your system is too slow
Feb 19 11:17:21 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: client bug: event processing lagging behind by 26ms, your system is too slow
Feb 19 11:27:59 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: client bug: event processing lagging behind by 37ms, your system is too slow
Feb 19 11:43:55 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: client bug: event processing lagging behind by 31ms, your system is too slow
Feb 19 11:44:59 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: client bug: event processing lagging behind by 23ms, your system is too slow
Feb 19 11:44:59 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: WARNING: log rate limit exceeded (5 msgs per 60min). Discarding future messages.
Feb 19 13:33:00 newcomer01-MS-7A40 gnome-shell[2037]: libinput error: event4 - Logitech Logitech Illuminated Keyboard: client bug: event processing lagging behind by 25ms, your system is too slow

Feb 19 09:54:59 newcomer01-MS-7A40 gnome-session[1267]: gnome-session-binary[1267]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 19 09:54:59 newcomer01-MS-7A40 gnome-session[1267]: gnome-session-binary[1267]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 19 09:54:59 newcomer01-MS-7A40 gnome-session-binary[1267]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 19 09:54:59 newcomer01-MS-7A40 gnome-session-binary[1267]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Feb 19 09:54:59 newcomer01-MS-7A40 canonical-livepatch.canonical-livepatchd[856]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/f9a21732b35c4a78a2874423734709a2/updates" failed, retrying in 30s.

I'm honestly afraid of it, since that was a lot of updates that probably build on each other. If I now install an older version of Grub, I could get more problems. I would honestly prefer a quick bug fix. I really don't want to have more bugs...

[Marc Püschel (newcomer-01)]

"I'll provide a version with additional patches later this week in a PPA which you can test."

Thank you so much, when i need another ppa let me know please.

[Marc Püschel (newcomer-01)]

@Julian Andres Klode (juliank)

i found out something strange: if i have my external USB hard drive (no linux) plugged in during boot, i don't have the bug. If the external hard drive is not plugged in during boot, I have the bug.

[Marc Püschel (newcomer-01)]

@Julian Andres Klode (juliank)

when is the update coming? You said "later this week in a PPA" and today is already Sunday and so far I have received nothing.

[Marc Püschel (newcomer-01)]

what is the current status of progress here? it would be really nice, if a bugfix will be released soon.

[Julian Andres Klode (juliank)]

Regressions have been reported from the additional fixes in another distribution so I am hesitating a bit and I'm still waiting to hear back about which path to take for fixing a bug on bionic (missing efibootmgr).

So I pivoted to apt work in the meantime while these threads get more clear.

[Marc Püschel (newcomer-01)]

@Julian Andres Klode (juliank)

thanks for getting back. Okay, please keep me up-to-date and do not forget the bug

[Marc Püschel (newcomer-01)]

@Julian Andres Klode (~juliank)

what is the current status of progress here? it would be really nice, if a bugfix will be released soon.

[Marc Püschel (newcomer-01)]

@Julian Andres Klode (~juliank)

what is the current status of progress here? Does anyone working on this? Or should I wait for 23.04.X LTS release and cross my fingers?

[Marc Püschel (newcomer-01)]

now added to this bug:
@Andy Whitcroft (~apw)
@Andy Whitcroft (~apw2)

[Julian Andres Klode (juliank)]

An updated grub is available for testing in 22.10 (and other versions once everything has been published and builds retriggered) in the PPA:

ppa:ubuntu-uefi-team/ubuntu/ppa

This is not trusted by the default Ubuntu key!

To test, you need to import the PPA signing key

https://ppa.launchpadcontent.net/ubuntu-uefi-team/ppa/ubuntu/dists/kinetic/main/uefi/grub2-amd64/current/control/uefi.crt

You can convert it to DER format by running

openssl x509 -in uefi.crt -out uefi.der -outform der

and then importing it into the MOK using

mokutil --import uefi.der

Please make sure to only update grub-efi-amd64-signed and related packages from the PPA and not newer shims or similar changes, and remove the PPA immediately after, then remove the key after a new update has been published in the main archive.

[Marc Püschel (newcomer-01)]

@Julian Andres Klode (~juliank) thank you very much for this information, I appreciate your work very much!

Do I have to do something, or comes this update for 22.04.2 LTS automatically?

I'm honestly afraid of testing it, I could get more problems as before.
Furthermore, I really don't want to have more bugs, hope for your understanding ...
I would honestly prefer a bug fix in public status, can't really believe that I'm the only one who is affected by this Bug ...

[Julian Andres Klode (juliank)]

The grub update has been submitted for signing now

https://bugs.launchpad.net/ubuntu/+source/grub2-unsigned/+bug/2013361