Ubuntu
plymouth package

Annoying boot messages interfering with splash screen, since upgrading to Jammy

Asked by João Pedro Seara

Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be.

Basically, the flow used to be in 20.04:

GRUB > Splash screen > Login prompt

Currently in 22.04:

GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt

All of those messages already existed in 20.04, the difference is that they were not appearing during boot.

I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

However, the fsck related message, I was not available to get rid of.

Something definitely changed here. To me, these messages are not of enough relevance to be shown at boot by default.

Obviously a minor issue, but important to the whole look and feel of the OS for desktop.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu plymouth Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Erich Eickmeyer (eeickmeyer) said : 		#1

Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Bernard Stafford (bernard010) said : 		#2

Try running a file system check: sudo fsck -y /dev/sda?
Use the appropriate disk # for the check: sda1, sda2, sda3. etc.
The message may disappear.

Removing the disk check from boot:
Add fsck.mode=skip to the Linux line in grub.cfg just before quiet splash.

Revision history for this message
João Pedro Seara (jpseara) said (last edit ): 		#3

Hello, Bernard.

This is the root fs so I had to boot in single user mode to do that. Still, I've done it and it changed nothing.

Adding fsck.mode=skip and loglevel=0 definitely helps, but I don't want to just disable fsck and keep the loglevel so low. This is a problem with the way Plymouth works. The fact that fsck is checking the disk and the fact that those errors are being logged in the kernel logs; these are completely normal. That has always happened before in Focal, the difference is that the splash screen was not being interrupted by that (as it shouldn't).

I've spin up two clean VMs (Focal and Jammy) and it's clear to me now that something has changed, as the problem can be reproduced on a clean installation.

I've added more information in the Lanchpad Bug itself.

Revision history for this message
Daniel van Vugt (vanvugt) said : 		#4

Converted back to a bug: bug 1970069

Can you help with this problem?

Provide an answer of your own, or ask João Pedro Seara for more information if necessary.

To post a message you must log in.