Comment # 92 on bug 1169783 from Cliff Zhao

(In reply to Hans-Peter Jansen from comment #91)
> I always use zypper.
> 
...
> 
> solved it for *all* crashing systems. Upstream doesn't want to apply a
> simple fix to prevent a DeviceTimeout=0 setting, hence we might want to deal
> with this in %post or apply a local patch. Probably we just missed to
> install a properly adjusted plymouthd.defaults. But I haven't fully grokked
> the plymouthd.conf and plymouthd.defaults handling, yet, sorry.

This has been discussed. option "DeviceTimeout" could not be pre-defined in the
program because a lot of people install Linux in a server without display
server. In this case the server will wait for an additional meaningless time
when booting to OS. Only the administrator knows how many seconds is
appropriate. and the recommended time is already been set in the config file.
so it could not be modified.
But you said that "plymouthd could crash, if DeviceTimeout is undefined"
because currently, Plymouth config file is migrated to branding package, I will
confirm if it is correct. if there has any problem, I will update.
Thank you!