After clicking Try Ubuntu, Plymouth text appears

[Ads20000]

After clicking Try Ubuntu, text from Plymouth appears:
[ OK ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
[ OK ] Reached target Sound Card.

This isn't ideal behavior because Ubuntu should go straight from Try Ubuntu to the desktop session without dropping back to Plymouth text

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperVersion: 1.389
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 5 12:22:21 2018
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1753467

[Launchpad Janitor (janitor)]

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

[Brian Murray (brian-murray)]

I was able to confirm this using today's image in a virtual machine. This bug was first reported with plymouth version 0.9.3-1ubuntu1 which a merge from Debian unstable.

plymouth (0.9.3-1ubuntu1) bionic; urgency=medium

  * Merged from debian unstable (second time ever…) Remaining changes:
    - include ubuntu theme logos:
      themes/ubuntu-logo/*, debian/source/include-binaries.
    - debian/libplymouth4.apport: add Apport hook.
    - Ship ubuntu-logo instead of debian-logo (debian/rules and
      debian/local/plymouth.hook).
    - Ship debian/source_plymouth.apport apport hook (debian/rules).
    - Add plymouth-label as a separate package and makes themes depending on
      it (debian/control, debian/plymouth-label.install,
      debian/plymouth-themes.install).
    - As log-viewer is disabled by default upstream and now in debian, don't
      ship its man page (debian/plymouth.links).
    - Ship plymouth-theme-ubuntu-logo and plymouth-theme-ubuntu-text specific
...

[Steve Langasek (vorlon)]

I don't think this text is "from" plymouth; I think it's from systemd. TTBOMK we actually currently have no integration between systemd and plymouth, such that systemd is writing its own messages to the console; which happens to most of the time be hidden because the console is in graphical mode so you only see the plymouth splash.

What's meant to happen is that we transition from the plymouth splash to the display manager without ever putting the console back into text mode (flicker-free boot). So if we're seeing the plymouth messages, this is failing somehow. The original bug report was with the vboxdrmfb video driver. Brian, which video driver did you see this with?

(I'm not sure how the vboxdrmfb module was in use, since that is not part of the main kernel package and should not be on the live image.)

I'm not sure whether we should also be configuring systemd to not display these boot messages in the live image.

[Brian Murray (brian-murray)]

Here's a video of the problem I'm seeing with the vga driver with kvm.

https://people.canonical.com/~brian/output.mp4