Verification done on noble (Linux Mint 22) with plymouth 24.004.60-1ubuntu7.2 from noble-proposed, on the affected hardware: HP ZBook Studio x360 G5 (Intel i915 eDP-1 + NVIDIA PRIME on-demand) with a StarTech USB32DP4K DisplayLink adapter driven by the evdi DKMS module. All five plymouth packages are at -1ubuntu7.2, dpkg --verify is clean, and the 7.2 plymouthd is the binary in the regenerated initramfs (sha256 match).
To exercise the fix rather than just boot cleanly, I re-armed the crash trigger from the Test Plan: I pulled evdi into the dracut initramfs (force_drivers) and set initial_device_count=4 in modprobe.d, so evdi pre-creates its phantom DRM heads early. On each boot evdi initialised at ~4.3 s (before switch_root, and before plymouth-start at ~4.6 s) with four phantom cards live during the splash -- the terminal-less-head condition this bug is about. I rebooted three times. Result: pass. On all three armed boots the boot-splash plymouthd opened and closed each of the four phantom heads during the splash -- exercising the device-probe path that dereferences the NULL backend->terminal on the unpatched code -- and never crashed or respawned (the only other plymouthd instance per boot is the normal shutdown/reboot splash). plymouth-quit finished cleanly, and coredumpctl shows no plymouthd crash on any of the three boots (nor since). For contrast, with the same trigger disarmed (my day-to-day config sets initial_device_count=0) 7.2 also installs cleanly and boots normally. Caveat on the [Where problems could occur] passphrase-input check: this system unlocks its LUKS root via TPM2 (PCR 7), so the encrypted-disk passphrase splash is never presented on a normal boot and I could not exercise passphrase entry/echo at the splash on this hardware -- that regression path is unverified here. The change only adds NULL guards around the existing terminal-input calls, and the same two commits (63597f92, 5c10072a) are already in plymouth in later Ubuntu releases (plucky 25.04 and the current development release) and in Fedora. On the affected config here the splash ran and handed off to the display manager cleanly. Changing verification-needed-noble to verification-done-noble. ** Tags removed: verification-needed-noble ** Tags added: verification-done-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2103533 Title: plymouth crashes with SIGSEGV in ply_terminal_set_disabled_input() from open_input_source() [drm.so] from ply_renderer_open_input_source() To manage notifications about this bug go to: https://bugs.launchpad.net/plymouth/+bug/2103533/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
