** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with
This bug was fixed in the package plymouth - 24.004.60-1ubuntu6
---
plymouth (24.004.60-1ubuntu6) noble; urgency=medium
* Cherry-pick upstream fixes for consistent default scale selection
that matches what Mutter chooses on the login screen (LP: #2054769)
* plymouth.hook:
This bug was fixed in the package initramfs-tools - 0.142ubuntu23
---
initramfs-tools (0.142ubuntu23) noble; urgency=medium
[ Daniel van Vugt ]
* hooks/framebuffer: Only add simple/tiny framebuffer drivers. This is to
limit the size of initrd when FRAMEBUFFER=y is soon
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in
** Changed in: initramfs-tools (Ubuntu)
Status: Opinion => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools
** Changed in: systemd (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: systemd (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of
** Description changed:
[ Impact ]
Kernel (and systemd) log messages appear during boot for many machines,
when the user should be seeing only the BIOS logo and/or Plymouth splash
screens.
+ [ Workaround ]
+
+ On most machines you can hide the problem by using these kernel
Hmm, no plymouthd isn't starting quite early enough in Noble:
2.799s - plymouthd starts
4.080s - first show-splash attempt (rejected because DRM hasn't started yet)
5.290s - found /dev/dri/card0
5.364s - showing splash screen
What this means is that any attempt to fix the bug in plymouthd itself
** Changed in: plymouth (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with
** Changed in: plymouth (Ubuntu)
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash
Actually, not that scary. I think I can implement a complete solution as
a single kernel patch. Just extend fbcon's deferred takeover feature to
wait until a certain timeout has passed. And if "splash" is present then
you can assume that should be a default of 10 seconds to wait for
Plymouth's 8
I was wrong, the kernel has no interest in "splash" and I suspect it is
plymouth displaying the unwanted messages. Perhaps we're not necessarily
seeing the kernel log though. Are we just seeing systemd messages
(PLY_ENABLE_SYSTEMD_INTEGRATION)? If that's it then we just need to make
sure
This looks more likely to be a kernel bug than plymouth right now. It
would only be a Plymouth bug if plymouthd was the one displaying the
kernel log messages while it waits for DRM to start. Thereafter it
switches to graphics mode.
** Also affects: linux (Ubuntu)
Importance: Undecided
This is a bug. The 'splash' option is configured, but text messages
from the kernel are being shown.
** Changed in: plymouth (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in
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
18 matches
Mail list logo
