Description of problem: ]$ journalctl -b | grep plymouth dracut: Starting plymouth daemon systemd[1]: Starting Show Plymouth Boot Screen... plymouth[560]: error: unexpectedly disconnected from boot status daemon systemd[1]: plymouth-start.service: Main process exited, code=killed, status=11/SEGV systemd[1]: Failed to start Show Plymouth Boot Screen. systemd[1]: plymouth-start.service: Unit entered failed state. systemd[1]: plymouth-start.service: Failed with result 'signal'. systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. reboot 2. journalctl -b | grep plymouth 3.
Can't reproduce in my cauldron that was last updated yesterday. However, I did not try in a cauldron that was started from 6RC
CC: (none) => marja11, rverschelde
Problem showed up with the new xorg and kernel update. Noticed a new kernel in the build system. system was a clean network install around the first of the month + updates. $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-desktop root=LABEL=cauldron noiswmd nokmsboot vga=794 ipv6.disable=1 audit=0
(In reply to Marja van Waes from comment #1) > Can't reproduce in my cauldron that was last updated yesterday. > > However, I did not try in a cauldron that was started from 6RC Just checked and my test bed node and it does not have the problem. I have opened a kernel bug report that also does not happen on my test bed node. Maybe the clear up on next kernel update.
newest plymouth rpm must have fixed the problem.
Status: NEW => RESOLVEDResolution: (none) => FIXED