core22 "20250210" causes plymouth-show-run.service failure on rpi2

[omar-selo]

To reproduce:

1. Provision a rpi2 with http://cdimage.ubuntu.com/ubuntu-core/22/dangerous-stable/pending/ubuntu-core-22-armhf+raspi.img.xz
2. Switch core22 to beta sudo snap refresh --channel latest/beta then wait for reboot
3. Look at failing services sudo systemctl list-units --failed and observe that plymouth-show-run.service failed

Logs:

$ sudo systemctl list-units --failed
  UNIT                      LOAD   ACTIVE SUB    DESCRIPTION            
● plymouth-show-run.service loaded failed failed Display state on splash

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

$ sudo journalctl --unit plymouth-show-run.service
Feb 19 09:28:05 ubuntu systemd[1]: Starting Display state on splash...
Feb 19 09:28:25 ubuntu systemd[1]: plymouth-show-run.service: start operation timed out. Terminating.
Feb 19 09:28:25 ubuntu systemd[1]: plymouth-show-run.service: Failed with result 'timeout'.
Feb 19 09:28:25 ubuntu systemd[1]: Failed to start Display state on splash.

[pieqq]

After some discussion with other colleagues, it looks like this failure started happening with core22 20240408. See for instance this submission on C3 for a Raspberry Pi 2 running UC22 with kernel 5.15.0-1058-raspi.

List of installed snaps:

Snap	Version	Revision	Channel	Confinement	Devmode	Developer	Date
checkbox	4.0.0-dev333	7711	uc22/beta	strict	True	ce-certification-qa	July 3, 2024
checkbox22	4.0.0-dev333	1012	latest/beta	strict	False	ce-certification-qa	July 3, 2024
core22	20240408	1384	latest/stable	strict	False	canonical	July 3, 2024
docker	24.0.5	2919	stable	strict	False	canonical	July 3, 2024
pi	22-2	133		strict	False	canonical	July 3, 2024
pi-kernel	5.15.0-1058.61	870	22/beta	strict	False	canonical	July 3, 2024
snapd	2.63	21762	latest/stable	strict	False	canonical	July 3, 2024

Post-cold/warn-boot failed systemd units:

Found 1 failed units

Failed units:
  UNIT                      LOAD   ACTIVE SUB    DESCRIPTION
● plymouth-show-run.service loaded failed failed Display state on splash

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
1 loaded units listed.

I'm now wondering if this could be an issue with RPis because they need an actual screen to be plugged to the HDMI connector in order to start exposing anything, which might not be the case for this specific Rpi2 in our lab.

[boukeas]

Starting from core22 version 20251009, this issue has also started appearing on:

• RPi3
• RPi Zero 2