Dimitri, I note your comment #106 about secureboot patches upstream. If
I recall correctly, a linux security update came down through Ubuntu
Updater about the same time or just prior to the LTS 20.04.1 updates in
mid September. A number of issues with LTS 20.04.1 appeared following
two "batches" of September Ubuntu updates. To the extent that these
issues may be inter-related -- at least insofar as being triggered by
upstream Linux security change(s) -- please note the bug numbers listed
in post #93 above.

If not relevant to this particular bug, then please disregard in
deference to the other individual bug numbers; if inter-related, then
perhaps this can be helpful.

You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

  initramfs unpacking failed

Status in OEM Priority Project:
Status in grub2 package in Ubuntu:
Status in initramfs-tools package in Ubuntu:
Status in linux package in Ubuntu:

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.


  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to