plymouth spinner can not show the messages after installation.

[hugh chao]

[Summary]
Before 20.04, when user finished the 1st stage of installation, the message 『please remove the installation medium then reboot』or 『please remove installation medium then press enter』 will be shown on the screen.

But since 20.04, due to the using of plymouth-themes-spinner, the system will still waiting for user to press Enter but without any message, so the system will be likely hanged there.

[Steps to reproduce]
1. Boot the installer with USB sticker
2. Finish the installation.
3. Click the button on the diagram to reboot.

[Expected result]
System reboot and boot to login page.

[Actual result]
Black screen (With vendor and ubuntu logo) and need to press "Enter" to reboot.

[Failure rate]
100%

[Additional information]
" lsb_release -rd

Description: Ubuntu Focal Fossa (development branch)
Release: 20.04

"apt-cache policy plymouth-theme-spinner
plymouth-theme-spinner:
  Installed: 0.9.4git20200109-0ubuntu8
  Candidate: 0.9.4git20200109-0ubuntu8
  Version table:
 *** 0.9.4git20200109-0ubuntu8 100
        100 /var/lib/dpkg/status
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu20
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-03-18 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315)
MachineType: Dell Inc. Latitude 5501
Package: plymouth 0.9.4git20200109-0ubuntu8
PackageArchitecture: amd64
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ed9c1d0b-cfe3-4860-b83e-d2a80d0c0223 ro quiet splash vt.handoff=7
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=ed9c1d0b-cfe3-4860-b83e-d2a80d0c0223 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Tags: focal
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Uname: Linux 5.4.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 08/21/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.name: 018CA2
dmi.board.vendor: Dell Inc.
dmi.board.version: X02
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn018CA2:rvrX02:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5501
dmi.product.sku: 0919
dmi.sys.vendor: Dell Inc.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[lotuspsychje (lotuspsychje)]

Thank you for reporting this bug and make ubuntu better!

To file bugs on ubuntu, please use ubuntu-bug package
to pull relevant info in the bug, so developers can
debug the best way possible.

You can still pull the info with: apport-collect 1867909
at this stage

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[hugh chao (hugh712)]

apport information

[Daniel van Vugt (vanvugt)]

I can reproduce a bug but I want to verify it's the same bug...

When you say:

  [Actual result]
  Black screen and need to press "Enter" to reboot.

Do you mean a totally "black screen", or one with logos? Because I get one with logos and that doesn't seem to have anything spinning. Maybe it's the bgrt theme and not the spinner theme...

Also, the relevant code in casper seems to be unchanged between eoan and focal:

    MSG="Please remove the installation medium, then press ENTER: "
    MSG_FALLBACK="Please remove the installation medium, then reboot."

    if [ "$prompt" ]; then
        if [ -x /bin/plymouth ] && plymouth --ping; then
            chvt 63
            plymouth message --text="$MSG"

So either:

 * one of those commands above are failing; or
 * plymouthd is starting too late to receive the commands (a race); or
 * there's a bug in plymouthd, but I first need to find out how/where plymouthd is being launched. Any idea?

[Daniel van Vugt (vanvugt)]

Any hints about how to debug this? Even if I ssh into the live session, that login still gets killed before this plymouth issue occurs. I seem to have no way of maintaining a shell on the system while the bug happens.

[Łukasz Zemczak (sil2100)]

This feels like a duplicate of LP: #1865161, what do you think? I need to see if Dimitri is still working on this.

[Daniel van Vugt (vanvugt)]

Yes, let's assume so.

[hugh chao (hugh712)]

@Danial

Yes it's with logos, I just update the bug description for #16,
and it seems the same issue as #18, even I keep waiting for 5 mins, the message still not shows up.