plymouth default logo not showing on boot

Bug #1825640 reported by Dave Goldsbrough on 2019-04-20

This bug report will be marked for expiration in 3 days if no further activity occurs. (find out why)

12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Low
Unassigned

Bug Description

 lsb_release -rd
Description: Ubuntu 18.04.2 LTS
Release: 18.04

apt-cache policy plymouth
plymouth:
  Installed: 0.9.3-1ubuntu7.18.04.1
  Candidate: 0.9.3-1ubuntu7.18.04.1
  Version table:
 *** 0.9.3-1ubuntu7.18.04.1 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.9.3-1ubuntu7 500
        500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu7.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18
Uname: Linux 4.15.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
Date: Sat Apr 20 13:23:02 2019
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
InstallationDate: Installed on 2018-06-17 (307 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Latitude E6430
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=c83fc526-fe19-4163-921d-e21e9ab61807 ro quiet splash vt.handoff=1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=c83fc526-fe19-4163-921d-e21e9ab61807 ro quiet splash vt.handoff=1
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/12/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0H3MT5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd03/12/2013:svnDellInc.:pnLatitudeE6430:pvr01:rvnDellInc.:rn0H3MT5:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6430
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Dave Goldsbrough (daveg-k) wrote :
Dave Goldsbrough (daveg-k) wrote :

Same as Bug #1825509 but different device/laptop

Sebastien Bacher (seb128) wrote :

Thank you for your bug report. What's the issue? Do you get the wrong logo? No logo? A video showing the boot could help there...

Changed in plymouth (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Dave Goldsbrough (daveg-k) wrote :

It is an intermittent bug. Sometimes, boot up is no problem and the Ubuntu splash screen does its usual thing. Other times, (infrequently) normal blank screen boot sequence but without splash screen towards the end - just straight into login prompt. At this point, after logging in all seems fine but after a short time a popup dialog box appears saying there is a problem and asks whether to report or not. The problem is, it is not the normal sort of crash report and there is no confidence that report has been submitted and so I raised this manual bug report.

It is a minor issue, the only effect is on Ubuntu reputation and could be off putting to new users.

Sebastien Bacher (seb128) wrote :

Can you add a journalctl log from a boot having the issue?

Dave Goldsbrough (daveg-k) wrote :

Added journalctl log for April 20 which from memory is when it happened - quite big sorry.

Dave Goldsbrough (daveg-k) wrote :

Just done update and noticed these upgrades; (includes plymouth) Will upgrade and advise if I see bug again.

The following packages will be upgraded:
  gir1.2-mutter-2 gnome-shell gnome-shell-common language-selector-common
  language-selector-gnome libmutter-2-0 libnuma1 libplymouth4 linux-firmware
  login mutter mutter-common passwd plymouth plymouth-label
  plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-text
17 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade.
Need to get 74.0 MB of archives.
After this operation, 24.8 MB of additional disk space will be used.
Do you want to continue? [Y/n]

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers