linux 4.15.0-20-generic messes up plymouth and no prompt for luks password
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
High
|
Unassigned |
Bug Description
With 4.15.0-19-generic everything works perfect. However, with 4.15.0-20-generic, when I power on the computer, the kde plymouth does not show the textbox to enter the root volume crypts luks password. The logo just stays there like in the attachment.
If I uninstall plymouth and remove quiet and splash from GRUB_CMDLINE_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #1 |
summary: |
- linux 4.15.0-20-generic messes up plymouth and no prompt for cryptfs + linux 4.15.0-20-generic messes up plymouth and no prompt for luks + cryptfs |
summary: |
- linux 4.15.0-20-generic messes up plymouth and no prompt for luks - cryptfs + linux 4.15.0-20-generic messes up plymouth and no textbox prompt for + luks cryptfs |
summary: |
- linux 4.15.0-20-generic messes up plymouth and no textbox prompt for - luks cryptfs + linux 4.15.0-20-generic messes up plymouth and no prompt for luks + password |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #2 |
- working correctly with 4.15.0-20-generic but displays kubuntu instead of ubuntu Edit (279.8 KiB, image/jpeg)
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #3 |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs. | #4 |
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 1768647
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.
Changed in linux (Ubuntu): | |
status: | New → Incomplete |
tags: | added: chaotic |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #5 |
I can reinstall problematic packages to re-test but need specific instructions how to do is successfully.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #6 |
Does this issue go away if you boot back into the -19 kernel?
Changed in linux (Ubuntu): | |
importance: | Undecided → High |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Joseph Salisbury (jsalisbury) wrote : | #7 |
Would it be possible for you to test the latest upstream kernel? Refer to https:/
If this bug is fixed in the mainline kernel, please add the following tag 'kernel-
If the mainline kernel does not fix this bug, please add the tag: 'kernel-
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".
Thanks in advance.
tags: | added: kernel-da-key |
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #8 |
With the -19 kernel it works perfectly. I will try newest version asap.
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #9 |
The problem is with kernel linux-image-
These are the steps to reproduce the issue:
1)
------------------ Start of /etc/default/grub -----------------
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT="0"
#GRUB_HIDDEN_
GRUB_HIDDEN_
GRUB_TIMEOUT=10
GRUB_DISTRIBUTO
GRUB_CMDLINE_
GRUB_CMDLINE_
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM=
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_
# Uncomment to get a beep at grub start
#GRUB_INIT_
------------------ End of /etc/default/grub -----------------
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #10 |
2) Uninstall and install commands as root, so you end up with the problem after last reboot:
apt install plymouth-
apt install plymouth-
apt install plymouth-
apt install plymouth-
apt install plymouth-
apt install plymouth-
apt install plymouth-
apt install plymouth-
apt install plymouth:
nano -w /etc/default/grub
apt install plymouth:
apt install plymouth-
apt --reinstall install plymouth-
shutdown -r now
nano -w /etc/default/grub
update-grub
update-grub2
update-initramfs -u
apt install plymouth-
apt uninstall plymouth-
apt remove plymouth-
apt install plymouth-
apt install plymouth-
shutdown -r now
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #11 |
The experienced issue is: when selecting kernel -20 to boot, it displays the following, and never progresses to ask for luks unlock password (other times just stays there the KDE logo but same thing, no textbox to enter luks password):
Loading Linux 4.15.0-20-generic ...
Loading initial ramdisk ...
_
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #12 |
I don't know which exact files to install on amd64, please help:
$ ls
linux-headers-
linux-image-
$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-
(Reading database ... 331467 files and directories currently installed.)
Preparing to unpack linux-headers-
Unpacking linux-headers-
Selecting previously unselected package linux-image-
Preparing to unpack linux-image-
Unpacking linux-image-
Selecting previously unselected package linux-modules-
Preparing to unpack linux-modules-
Unpacking linux-modules-
dpkg: dependency problems prevent configuration of linux-headers-
linux-
Package linux-headers-
dpkg: error processing package linux-headers-
dependency problems - leaving unconfigured
Setting up linux-modules-
Setting up linux-image-
I: /vmlinuz.old is now a symlink to boot/vmlinuz-
I: /initrd.img.old is now a symlink to boot/initrd.
I: /vmlinuz is now a symlink to boot/vmlinuz-
I: /initrd.img is now a symlink to boot/initrd.
Processing triggers for linux-image-
/etc/kernel/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.17.0-
Consult /var/lib/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.17.0-
Consult /var/lib/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.17.0-
Consult /var/lib/
/etc/kernel/
update-initramfs: Generating /boot/initrd.
/etc/kernel/
Generating grub configuration file ...
Found linux image: /boot/vm...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #13 |
Same problem with 386 packages, please help:
$ ls
linux-headers-
linux-image-
$ sudo dpkg -i *.deb
Selecting previously unselected package linux-headers-
(Reading database ... 331468 files and directories currently installed.)
Preparing to unpack linux-headers-
Unpacking linux-headers-
Selecting previously unselected package linux-image-
Preparing to unpack linux-image-
Unpacking linux-image-
Selecting previously unselected package linux-modules-
Preparing to unpack linux-modules-
Unpacking linux-modules-
dpkg: dependency problems prevent configuration of linux-headers-
linux-
dpkg: error processing package linux-headers-
dependency problems - leaving unconfigured
Setting up linux-modules-
Setting up linux-image-
I: /vmlinuz.old is now a symlink to boot/vmlinuz-
I: /initrd.img.old is now a symlink to boot/initrd.
I: /vmlinuz is now a symlink to boot/vmlinuz-
I: /initrd.img is now a symlink to boot/initrd.
Processing triggers for linux-image-
/etc/kernel/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.17.0-
Consult /var/lib/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.17.0-
Consult /var/lib/
ERROR (dkms apport): kernel package linux-headers-
Error! Bad return status for module build on kernel: 4.17.0-
Consult /var/lib/
/etc/kernel/
update-initramfs: Generating /boot/initrd.
/etc/kernel/
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-
Found initrd image: /boot/initrd.
Fou...
![](/+icing/build/overlay/assets/skins/sam/images/close.gif)
Bump (bump55) wrote : | #14 |
Finally enabled bionic-proposed, and newest kernel 4.15.0-21-generic works again, so I guess it's fixed upstream. This is part of the update log for future reference:
root@ubuntu:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
linux-
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
linux-
The following packages will be upgraded:
gnome-
linux-libc-dev linux-signed-
software-
22 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 197 MB of archives.
After this operation, 335 MB of additional disk space will be used.
Do you want to continue? [Y/n]
tags: | added: kernel-fixed-upstream |
tags: |
added: kernel-da-key. removed: kernel-da-key |
tags: |
added: kernel-da-key removed: kernel-da-key. |
All graphic fanciness should be removed by default by the way, it's only there to cause problems.
https:/ /bugs.launchpad .net/ubuntu/ +source/ plymouth/ +bug/1768651