Comment # 20 on bug 1008489 from M Vermeiden

I am seeing this problem also on Tumbleweed as of now running on a Intel(R)
Core(TM) i5-4570S CPU:

> sudo journalctl -x -b | grep plymouth
-- Subject: Unit plymouth-start.service has begun start-up
-- Unit plymouth-start.service has begun starting up.
-- Subject: Unit plymouth-start.service has finished start-up
-- Unit plymouth-start.service has finished starting up.
-- Subject: Unit systemd-ask-password-plymouth.path has finished start-up
-- Unit systemd-ask-password-plymouth.path has finished starting up.
-- Subject: Unit plymouth-switch-root.service has begun start-up
-- Unit plymouth-switch-root.service has begun starting up.
-- Subject: Unit plymouth-switch-root.service has finished start-up
-- Unit plymouth-switch-root.service has finished starting up.
-- Subject: Unit plymouth-read-write.service has begun start-up
-- Unit plymouth-read-write.service has begun starting up.
-- Subject: Unit plymouth-read-write.service has finished start-up
-- Unit plymouth-read-write.service has finished starting up.
Jun 10 09:30:40 linux-d7n9 systemd[1]: Received SIGRTMIN+20 from PID 273
(plymouthd).
Jun 10 09:30:40 linux-d7n9 systemd[1]: plymouth-start.service: Main process
exited, code=dumped, status=6/ABRT
Jun 10 09:30:40 linux-d7n9 systemd[1]: plymouth-start.service: Unit entered
failed state.
Jun 10 09:30:40 linux-d7n9 systemd[1]: plymouth-start.service: Failed with
result 'core-dump'.
Jun 10 09:30:40 linux-d7n9 systemd-coredump[1330]: Process 273 (plymouthd) of
user 0 dumped core.
-- Subject: Process 273 (plymouthd) dumped core
-- Process 273 (plymouthd) crashed and dumped core.

See also https://forums.opensuse.org/newreply.php?do=postreply&t=522940