canonical-ubuntu-qa team mailing list archive

[Daniel van Vugt <1970069@xxxxxxxxxxxxxxxxxx>]

A solution, but a bit scary:

1. If "splash" then tell fbcon it's not allowed to take over the
framebuffer:

   fbcon=map:1

2. After plymouth is finished (or even when it's just started and taken
over the framebuffer), tell fbcon it is allowed to use the framebuffer:

   $ con2fbmap 1 0

   This could also be done as a simple ioctl from plymouth itself.

Virtual terminals won't work until you do step 2.

-- 
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen

Status in plymouth package in Ubuntu:
  In Progress

Bug description:
  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".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1970069/+subscriptions