Public bug reported:
After last night's system update, gdm3 can no longer start a display
server. Looking into it, I found there was a failure building a new
initramfs. Running kernel 4.18.0-25-lowlatency. Here's the error
message. Have to type it in by hand as I'm using a pseudotty console on
the affected machine.
# update-initramfs -u -v
[blah blah]
Calling hook plymouth
Adding binary /usr/lib/x86_64-linux-gnu/plymouth//script.so
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1
Removing /boot/initrd-img-4.18.0-25-lowlatency.dpkg-bak
update-initramfs: failed for /boot/initrd.img-4.18.0-25-lowlatency with 1
#
Please note the double slash between "plymouth//script.so" which is in
the text of the error message.
I did attempt to reinstall plymouth.
# apt-get install --reinstall plymouth-*
which worked, in that it reinstalled, but did not succeed in rebuilding
the kernel initramdisk.
** Affects: plymouth (Ubuntu)
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/1836717
Title:
Ubuntu-18.04.2 nightly system update caused plymouth initramfs failure
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1836717/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
