[Bug 1975421] Re: Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth ignores --no-boot-log flag

[Thomas Weissel]

*** This bug is a duplicate of bug 1970069 ***
    https://bugs.launchpad.net/bugs/1970069

well i'm getting to the roots of this step by step.. but as far as i see
it now i reported a bug where kernel parameters that set the loglevel
are beeing ignored by system daemons that monitor the init process.

the other bug is about plymouth not hiding these messages.

so the headline of this bug should be corrected.. or.. i'll do another report that pinpoints the problem better
because it's probaly not even a plymouth problem ?

** Description changed:

- running a fresh install of kubuntu 22.04 
+ running a fresh install of kubuntu 22.04
  plymouth version: 0.9.5+git20211018-1ubuntu3
  
+ What should happen:
+ no bootmessages should be printed to console in the first place
  
- What should happen:  
- Plymouth should totally cover all bootmessages (no bootmessages should be printed to console in the first place)
+ What actually happens:
+ When Plymouth quits the last 2-3 messages are visible - so some boot messages are printed to console never the less
  
- What actually happens: 
- When Plymouth quits the last 2-3 messages are visible
- 
- on shutdown i get:
+ on shutdown for example i get:
  [OK] Reached target Late Shutdown Services
  [OK] Finished System Power Off
  [OK] Reached target System Power off
  
- 
- it seems to be absolutely impossible to hide all boot messages 
+ it seems to be absolutely impossible to hide all boot messages
  i've done everything from this arch wiki site (and more) to get a silent boot: https://wiki.archlinux.org/title/silent_boot
  (this makes all acpi warnings and more go away.. but the [OK] reached/finished messages are not affected by those kernel parameters (this should also be fixed)
  
- My Kernelparameters: 
- fbcon=nodefer rd.systemd.show_status=false vt.global_cursor_default=0 quiet splash loglevel=3 rd.udev.log_level=3
+ My Kernelparameters:quiet splash fbcon=nodefer rd.systemd.show_status=0
+ systemd.show_status=0 vt.global_cursor_default=0 loglevel=0
+ rd.udev.log_level=0 udev.log_level=0 rd.systemd.log_level=0
+ systemd.log_level=0
  
- 
- What part of the system throws these messages ? i thought it is systemd? 
+ What part of the system throws these messages ? 
+ i thought it is systemd?
  so i even edited files in /usr/lib/systemd/system in order to set the StandardOutput to null for all of the halt and reboot and plymouth scripts
  
  and i edited the plymouth start and stop scripts and added -no-boot-log
  but plymouth totally ignores this flag and still logs everything to
  console and to /var/log/boot.log
  
- 
- this defies the whole purpose of plymouth if plymouth itself spams the console with messages and if it's systemd why doesn't it respect the kernel parameters
+ this defies the whole purpose of plymouth if plymouth itself spams the
+ console with messages and if it's systemd why doesn't it respect the
+ kernel parameters

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1975421

Title:
  Make Plymouth hide ALL messages on boot, reboot, halt. Plymouth
  ignores --no-boot-log flag

Status in plymouth package in Ubuntu:
  New

Bug description:
  running a fresh install of kubuntu 22.04
  plymouth version: 0.9.5+git20211018-1ubuntu3

  What should happen:
  no bootmessages should be printed to console in the first place

  What actually happens:
  When Plymouth quits the last 2-3 messages are visible - so some boot messages are printed to console never the less

  on shutdown for example i get:
  [OK] Reached target Late Shutdown Services
  [OK] Finished System Power Off
  [OK] Reached target System Power off

  it seems to be absolutely impossible to hide all boot messages
  i've done everything from this arch wiki site (and more) to get a silent boot: https://wiki.archlinux.org/title/silent_boot
  (this makes all acpi warnings and more go away.. but the [OK] reached/finished messages are not affected by those kernel parameters (this should also be fixed)

  My Kernelparameters:quiet splash fbcon=nodefer
  rd.systemd.show_status=0 systemd.show_status=0
  vt.global_cursor_default=0 loglevel=0 rd.udev.log_level=0
  udev.log_level=0 rd.systemd.log_level=0 systemd.log_level=0

  What part of the system throws these messages ? 
  i thought it is systemd?
  so i even edited files in /usr/lib/systemd/system in order to set the StandardOutput to null for all of the halt and reboot and plymouth scripts

  and i edited the plymouth start and stop scripts and added -no-boot-
  log but plymouth totally ignores this flag and still logs everything
  to console and to /var/log/boot.log

  this defies the whole purpose of plymouth if plymouth itself spams the
  console with messages and if it's systemd why doesn't it respect the
  kernel parameters

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