Hello, experiencing plymouyth crash when i attempt to boot on latest kernel-6.8.10-300.fc40 My system is : Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.10-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × 12th Gen Intel® Core™ i5-1240P Memory: 30,9 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: Intel(R) Client Systems Product Name: NUC12WSKi5 Will attach a picture (sorry about that). Reproducible: Always Steps to Reproduce: 1.Select latest kernel in Grub 2.Boot on it 3.Plymouth crash I used at some point : grubby --args="vconsole.keymap=us" --update-kernel=ALL localectl System Locale: LANG=en_US.UTF-8 VC Keymap: us X11 Layout: us X11 Model: pc86
Created attachment 2034583 [details] stacktrace
I am experiencing a similar issue, with the crashes having begun after upgrading to the asahi kernel v6.8.9 and happening at `ply_terminal_set_disabled_input` instead of `ply_input_device_get_keymap`, in the same library (`libply-splash-core.so`).
Created attachment 2035853 [details] stacktrace2
I am also seeing this occasionally, since updating to FC40. I tested with the 6.8.x and the 6.9.x (which I currently run) but it seems purely random when the crash happens. I will attached the coredump and BT but I am not sure if there is enough data. Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.3-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics
Created attachment 2036059 [details] Dump and BT
After one month of reboots, I think I can safely say that reinstalling the same version of Plymouth solved this issue for me. Note however that in my case the crash happened at `ply_terminal_set_disabled_input` instead of `ply_input_device_get_keymap` like the others have reported.
Created attachment 2040281 [details] Plymouth:debug output This crash happens still, but very randomly. I have attached the plymouth debug output, I am not sure if it of any use though.
Yeah, it's back for me too. I've disabled plymouth as it makes my machine almost unusable boot-wise.
Created attachment 2043507 [details] Photo of the backtrace during boot I just hit this issue as well. Here is a photo of the laptop where it happens, we can see it crashes in ply_input_device_get_keymap as well. Since I have to type my password, this effectively prevents booting.
This looks like upstream bug #245, which was fixed 7 months ago: https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/245 I haven't tried it, but it looks like a new plymouth release, or backporting this patch could help.
I confirm that backporting just the patch 709f21e80199ee51badff2d9b5dc6bae8af2a1a1 "renderers: Do not assume all keyboards have LEDs" is enough to fix the issue.
A PR to the packaging was just opened to propose this: https://src.fedoraproject.org/rpms/plymouth/pull-request/7
FEDORA-2024-d8dd2b90ea (plymouth-24.004.60-14.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2024-d8dd2b90ea
FEDORA-2024-28a0fa28e6 (plymouth-24.004.60-14.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-28a0fa28e6
FEDORA-2024-6cd5abac7b (plymouth-24.004.60-14.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-6cd5abac7b
FEDORA-2024-8ef2fc847c (plymouth-24.004.60-14.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ef2fc847c
The fix does not work for me. However, apparently I was the only person to see the crash at `ply_terminal_set_disabled_input` instead of `ply_input_device_get_keymap`, so it may work for others. Also, since the last time I checked, now plymouth crashes at a third function, `ply_input_device_get_capslock_state`, on my machine, both with revisions 12 and 14.
FEDORA-2024-d8dd2b90ea (plymouth-24.004.60-14.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
@noisycoil For your bug my guess is that we need to backport 63597f92d108237a3ab7d2343a602a95edddd4e5 "ply-terminal: Fix crash on vt-less kernels when checking the enabled state". But I can't reproduce, so I'd be interested to know if that works for you.
Yes, the commit you mentioned may fix the `ply_terminal_set_disabled_input` crash, and yes, I'd be willing to test the fix. However, as I said, right now I crash at `ply_input_device_get_capslock_state` (both revisions 12 and 14), so if I continue crashing there I'm afraid I will not be of much help.
@contact Cherry-picked your commit into the f40 branch, rebuilt the package and crashed again at `ply_input_device_get_capslock_state`. So I don't know if your patch would have fixed my initial crash, but I can't verify it because of the current one.
FEDORA-2024-6cd5abac7b has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-6cd5abac7b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-6cd5abac7b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-28a0fa28e6 has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-28a0fa28e6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-28a0fa28e6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-8ef2fc847c has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-8ef2fc847c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-8ef2fc847c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-28a0fa28e6 (plymouth-24.004.60-14.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2024-8ef2fc847c (plymouth-24.004.60-14.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report.
I confirm that the new package fixes the issue for me. @noisycoil Don't forget to regenerate the initramfs if you did not get a kernel update. If it's the same as the current kernel use `sudo dracut -f`. If it still does not work, could you open a separate issue please? So it's at least tracked.
> Don't forget to regenerate the initramfs @contact I'd already done so to test if it was one of my custom dracut packages interfering (removed the package and regenerated the initramfs, then reinstalled it and regenerated again, did so a few times). The new revision only booted once out of 3-4 tries. However, I just retried to see if anything had changed and just now it booted 4 out of 4 times. So maybe I was just very unlucky during the first tests, but your patch (revision 14) seems to at least have notably improved the situation. If it starts failing again I'll open a new BR. Thanks!
I have not seen the crash since the new update on this F40 box.
FEDORA-2024-6cd5abac7b (plymouth-24.004.60-14.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.