Created attachment 1222166 [details] dmesg This seems similar to https://bugzilla.redhat.com/show_bug.cgi?id=1342673 plymouth-start.service fails on boot with a core dump. The splash screen is briefly shown and then the boot messages are shown scrolling down the screen. GRUB_CMDLINE_LINUX="rd.lvm.lv=fedora/swap rd.lvm.lv=fedora/root rhgb quiet rd.driver.blacklist=nouveau audit=0 plymouth.debug=/dev/kmsg log_buf_len=1M" I attached the dmesg output in case you need that. I'm willing to give more information if you need it. I don't know where the core dump is or I would attach it. The system updates are current as of this morning. plymouth-0.9.3-0.6.20160620git0e65b86c.fc25.x86_64
Created attachment 1222429 [details] plymouth debug log
Kernel version is 4.8.7-300.fc25.x86_64 [me@sirius ~]$ sudo systemctl status plymouth-start.service -l --no-pager ● plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/usr/lib/systemd/system/plymouth-start.service; static; vendor preset: disabled) Active: failed (Result: core-dump) since Mon 2016-11-21 10:27:21 EST; 12min ago Main PID: 328 (code=dumped, signal=ABRT) Nov 21 10:26:44 sirius plymouth[335]: [ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6 Nov 21 10:26:44 sirius plymouth[335]: [ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6 Nov 21 10:26:44 sirius plymouth[335]: [ply-event-loop.c:759] ply_event_loop_stop_watching_fd:stopping watching fd 6 Nov 21 10:26:44 sirius plymouth[335]: [ply-event-loop.c:775] ply_event_loop_stop_watching_fd:removing destination for fd 6 Nov 21 10:26:44 sirius plymouth[335]: [./ply-boot-client.c:795] ply_boot_client_detach_from_event_loop:detaching from event loop Nov 21 10:26:44 sirius systemd[1]: Started Show Plymouth Boot Screen. Nov 21 10:26:51 sirius plymouthd[327]: plymouthd: ply-image.c:210: ply_image_get_width: Assertion `image != NULL' failed. Nov 21 10:27:21 sirius systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=6/ABRT Nov 21 10:27:21 sirius systemd[1]: plymouth-start.service: Unit entered failed state. Nov 21 10:27:21 sirius systemd[1]: plymouth-start.service: Failed with result 'core-dump'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.