[Bug 1885254] Re: boot.log scattered with msgs from plymouth even when booted with "noplymouth"

[Günter Neiß]

First: correction of some typos:
replace: 2. What have such megs to do inside boot.log ?
with: 2. What have such msgs to do inside boot.log ?

A, only after sending this bug report, I see that for whatever reason the boot was done with:
"plymouth:debug"

Because I make a system snapshot before any "apt upgrade"..
I am able to see when this has changed..
"plymouth:debug" was added by a system upgrade at 2020-06-23!
The prev. update (done at 2020-06-08) does not contain this (but it even does not contain "noplymouth" ??)
After looking as far as I can, I find that some upgrade before 2019-12-18 must have removed the "noplymouth" that I had added to the boot line I mentioned in my first post.

-- 
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/1885254

Title:
  boot.log scattered with msgs from plymouth even when booted with
  "noplymouth"

Status in plymouth package in Ubuntu:
  New

Bug description:
  System-Information:
  Description:	Ubuntu 14.04.6 LTS
  Release:	14.04
  plymouth:	0.8.8-0ubuntu17.2
  ######################################

  Today I had to reboot my PC bacause Libre-Office-Calc is complainig about a "file in use by unknown..".
  This file resides on a network share (cisfs) and is definitly not "in use"!

  While the system shutdown I see a lot of msg scrolling over the screen
  while the system goes down. Same happens on boot. I look into boot.log
  and see this:

  ######################################
  <start of file>
  [ply-event-loop.c]               ply_event_loop_stop_watching_fd:stopping watching fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:removing destination for fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:stopping watching fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:removing destination for fd 6

  [./ply-boot-client.c]
  ply_boot_client_detach_from_event_loop:detaching from event loop

  Begin: Loading essential drivers ... done.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
  Begin: Running /scripts/local-premount ... done.
  Begin: Running /scripts/local-bottom ... done.
  done.
  Begin: Running /scripts/init-bottom ... [ply-event-loop.c]               ply_event_loop_stop_watching_fd:stopping watching fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:removing destination for fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:stopping watching fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:removing destination for fd 6

  [./ply-boot-client.c]
  ply_boot_client_detach_from_event_loop:detaching from event loop

  done.

   * Starting Read required files in advance[fail]
  <some (usual) lines omitted>

   * Starting configure network device security[ OK ]
  [ply-event-loop.c]               ply_event_loop_stop_watching_fd:stopping watching fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:removing destination for fd 6

   * Starting Mount network filesystems[ OK ]

   * Starting Failsafe Boot Delay[ OK ]
   * Starting SMB/CIFS File Server[ OK ]
  [ply-event-loop.c]               ply_event_loop_stop_watching_fd:stopping watching fd 6

  [ply-event-loop.c]
  ply_event_loop_stop_watching_fd:removing destination for fd 6

  [./ply-boot-client.c]
  ply_boot_client_detach_from_event_loop:detaching from event loop

   * Stopping Mount network filesystems[ OK ]
  <remaining (usual) lines omitted>
  ######################################

  Because I always use "noplymouth" inside the boot-options I am a bit confused.
  1. Why plymouth is still activ (OK, may it's needed and this disables only the splsh screen)
  2. What have such megs to do inside boot.log ?

  Maybe this behaviour (bug) is althougth the reason for some other
  problems I had in the last time with network shares (cisfs).

  For ex.: Nautilus copies only one file and "hangs" on the dir for the remaing files (of that job).
  It seams the operation is done, but nautilus is waiting for something.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: plymouth 0.8.8-0ubuntu17.2
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 26 10:15:30 2020
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  MachineType: System manufacturer System Product Name
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=f508a193-f07a-4368-ac1f-0273229657fc ro plymouth:debug
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic root=UUID=f508a193-f07a-4368-ac1f-0273229657fc ro plymouth:debug
  SourcePackage: plymouth
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/11/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0608
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T SE
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0608:bd11/11/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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