When booting I get "Starting Show Plymouth Boot Screen failed, see
'systemctl status plymouth-start.service' for details." The plymouth
seems to work fine though. Here is more information:
$ systemctl status plymouth-start.service
plymouth-start.service - Show Plymouth Boot Screen
Loaded: loaded (/lib/systemd/system/plymouth-start.service)
Active: failed since Sat, 11 Jun 2011 11:50:58 +0200; 24min ago
Process: 765 ExecStart=/sbin/plymouthd --mode=boot
--pid-file=/run/plymouth/pid (code=exited, status=69)
CGroup: name=systemd:/system/plymouth-start.service
$ systemctl show plymouth-start.service
Id=plymouth-start.service
Names=plymouth-start.service
Wants=systemd-ask-password-plymouth.path
WantedBy=sysinit.target
Before=systemd-ask-password-plymouth.service plymouth-quit.service
plymouth-quit-wait.service
After=systemd-vconsole-setup.service udev-settle.service
Description=Show Plymouth Boot Screen
LoadState=loaded
ActiveState=failed
SubState=failed
FragmentPath=/lib/systemd/system/plymouth-start.service
InactiveExitTimestamp=Sat, 11 Jun 2011 11:50:58 +0200
InactiveExitTimestampMonotonic=15973156
ActiveEnterTimestampMonotonic=0
ActiveExitTimestampMonotonic=0
InactiveEnterTimestamp=Sat, 11 Jun 2011 11:50:58 +0200
InactiveEnterTimestampMonotonic=16069157
CanStart=yes
CanStop=yes
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=no
OnFailureIsolate=no
IgnoreOnIsolate=no
DefaultControlGroup=name=systemd:/system/plymouth-start.service
ControlGroup=cpu:/system/plymouth-start.service
name=systemd:/system/plymouth-start.service
NeedDaemonReload=no
JobTimeoutUSec=0
ConditionTimestamp=Sat, 11 Jun 2011 11:50:58 +0200
ConditionTimestampMonotonic=15957342
ConditionResult=yes
Type=forking
Restart=no
NotifyAccess=none
RestartUSec=100ms
TimeoutUSec=1min 30s
ExecStart={ path=/sbin/plymouthd ; argv[]=/sbin/plymouthd --mode=boot
--pid-file=/run/plymouth/pid ; ignore=no ; start_time=[n/a] ;
stop_time=[Sat, 11 Jun 2011 11:50:58 +0200] ; pid=765 ; code=exited ;
statu
ExecStartPost={ path=/bin/plymouth ; argv[]=/bin/plymouth
--show-splash ; ignore=yes ; start_time=[n/a] ; stop_time=[n/a] ;
pid=0 ; code=(null) ; status=0/ }
UMask=0002
LimitCPU=18446744073709551615
LimitFSIZE=18446744073709551615
LimitDATA=18446744073709551615
LimitSTACK=18446744073709551615
LimitCORE=18446744073709551615
LimitRSS=18446744073709551615
LimitNOFILE=1024
LimitAS=18446744073709551615
LimitNPROC=30044
LimitMEMLOCK=65536
LimitLOCKS=18446744073709551615
LimitSIGPENDING=30044
LimitMSGQUEUE=819200
LimitNICE=0
LimitRTPRIO=0
LimitRTTIME=18446744073709551615
OOMScoreAdjust=0
Nice=0
IOScheduling=0
CPUSchedulingPolicy=0
CPUSchedulingPriority=0
TimerSlackNSec=50000
CPUSchedulingResetOnFork=no
NonBlocking=no
StandardInput=null
StandardOutput=inherit
StandardError=inherit
SyslogPriority=30
SyslogLevelPrefix=yes
SecureBits=0
CapabilityBoundingSet=18446744073709551615
MountFlags=1048576
PrivateTmp=no
SameProcessGroup=no
KillMode=control-group
KillSignal=15
PermissionsStartOnly=no
RootDirectoryStartOnly=no
RemainAfterExit=no
GuessMainPID=yes
ExecMainStartTimestampMonotonic=0
ExecMainExitTimestampMonotonic=0
ExecMainPID=0
ExecMainCode=0
ExecMainStatus=0
MainPID=0
ControlPID=0
SysVStartPriority=-1
FsckPassNo=0
Should I be worried about this? A bug report?
--joshua
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
