Summary: | plymouth-start.service races with gdm.service startup | ||
---|---|---|---|
Product: | plymouth | Reporter: | Daniel Drake <dan> |
Component: | general | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | RESOLVED NOTOURBUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | rstrode |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: | systemd: make sure to only start plymouth is started |
Description
Daniel Drake
2015-03-06 19:34:27 UTC
This could be fixed by making plymouth-start.service Before=gdm.service, or by making gdm.service After=plymouth-start.service. Any preference? i'd say gdm.service should add After=plymouth-start.service since it already has After=plymouth-quit.service in fact, gdm.service should have all the same dependencies plymouth-quit.service has, since gdm.service Conflicts (replaces) plymouth-quit.service Created attachment 114097 [details] [review] systemd: make sure to only start plymouth is started This commit makes sure gdm doesn't start in parallel with plymouth, which could lead to plymouth activating after X is started. Furthermore, GDM is replacing getty@tty1.service and plymouth-quit.service, so it needs to have the same dependencies as them. look right? That looks good, although you might want to avoid eating the blankline above [Service] for cleanliness. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.