| Summary: | When booting the machine, systemd complains that plymouth-start.service failed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frédéric "LpSolit" Buclin <LpSolit> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | minor | ||
| Priority: | Low | CC: | mageia, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | systemd-37-17.mga2.src.rpm | CVE: | |
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 2120 | ||
|
Manuel Hiebel
2011-10-29 16:53:37 CEST
Blocks:
(none) =>
2120 IIUC, Colin said the other day this and some other "failed" messages while booting can be ignored, therefore setting priority to low and severity to minor. This particular failed message is still there. First cc'ing Colin, in case I misunderstood him, and then assigning to maintainer Priority:
Normal =>
Low
Marja Van Waes
2011-12-22 20:05:47 CET
Assignee:
bugsquad =>
dmorganec I don't think this will be a problem any more now that we are using Dracut for initrd generation which has graceful handover to systemd for dealing with plymouth (i.e. the /run folder is mounted and this is checked in the plymouth unit systemd uses. So with that in mind, I'm closing this ticket. Fee free to reopen if you still have problems with it. Status:
NEW =>
RESOLVED |
$ systemctl status plymouth-start.service plymouth-start.service - Show Plymouth Boot Screen Loaded: loaded (/lib/systemd/system/plymouth-start.service; static) Active: failed since Sat, 29 Oct 2011 13:56:59 +0200; 9min ago Process: 88 ExecStart=/sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid (code=exited, status=69) CGroup: name=systemd:/system/plymouth-start.service