+1 for this change. It should be safe because plymouth-splash is only ever started once at boot, so there's no risk of 'and started plymouth-splash' causing a maintainer script hang at package upgrade time.
Since plymouth-splash itself waits for the video device before starting, I think the lightdm start condition can probably be reduced to:
start on ((filesystem
and runlevel [!06]
and started dbus
and started plymouth-splash)
or runlevel PREVLEVEL=S)
+1 for this change. It should be safe because plymouth-splash is only ever started once at boot, so there's no risk of 'and started plymouth-splash' causing a maintainer script hang at package upgrade time.
Since plymouth-splash itself waits for the video device before starting, I think the lightdm start condition can probably be reduced to:
start on ((filesystem
and runlevel [!06]
and started dbus
and started plymouth-splash)
or runlevel PREVLEVEL=S)