Plymouth is stuck on a plain black screen

Bug #2012698 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Plymouth
New
Unknown
plymouth (Ubuntu)
New
Undecided
Unassigned

Bug Description

Plymouth never displays anything -- the boot process is a plain black screen.

Workaround:

Tap Esc once to see text mode.
Tap Esc a second time to get the Plymouth graphical screen.

I only figured that out when I had been waiting too long for the disk decryption prompt.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: plymouth 22.02.122-3ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
Date: Fri Mar 24 13:50:04 2023
DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
InstallationDate: Installed on 2023-03-24 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317)
MachineType: LENOVO 21CBCTO1WW
ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=<set>
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: plymouth
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2023
dmi.bios.release: 1.36
dmi.bios.vendor: LENOVO
dmi.bios.version: N3AET71W (1.36 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CBCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76530 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.17
dmi.modalias: dmi:bvnLENOVO:bvrN3AET71W(1.36):bd01/31/2023:br1.36:efr1.17:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
dmi.product.family: ThinkPad X1 Carbon Gen 10
dmi.product.name: 21CBCTO1WW
dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
dmi.product.version: ThinkPad X1 Carbon Gen 10
dmi.sys.vendor: LENOVO

Revision history for this message
Daniel van Vugt (vanvugt) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Plymouth is just a plain black screen

I'm hoping this is hardware-specific (ADL-P, OLED, whatever). It doesn't seem to happen on other systems running lunar.

tags: added: rls-ll-incoming
Changed in linux (Ubuntu):
milestone: none → ubuntu-23.04
Changed in plymouth (Ubuntu):
milestone: none → ubuntu-23.04
Changed in plymouth (Ubuntu):
assignee: nobody → Daniel van Vugt (vanvugt)
Changed in plymouth (Ubuntu):
status: New → In Progress
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

There is nothing failing according to my plymouth debug log. Also it doesn't seem to occur on any other machine type. So this is on hold awaiting upstream advice.

no longer affects: linux (Ubuntu)
Changed in plymouth (Ubuntu):
status: In Progress → New
Changed in plymouth:
status: Unknown → New
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually I have found that adding an external monitor fixes the issue on the internal screen. So now I know it's not an unreachably low level kernel issue I can investigate the differences.

Changed in plymouth (Ubuntu):
status: New → In Progress
summary: - Plymouth is just a plain black screen
+ Plymouth is stuck on a plain black screen
Changed in plymouth (Ubuntu):
milestone: ubuntu-23.04 → none
status: In Progress → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

Changing to rls-ll-notfixing, there has been no recent activity nor duplicate which suggests it doesn't need to be handle as a rls target issue

tags: added: rls-ll-notfixing
removed: rls-ll-incoming
Changed in plymouth (Ubuntu):
assignee: Daniel van Vugt (vanvugt) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.