2015-09-13 10:00 GMT+02:00 Zhang Jingqiang <zh...@outlook.com>:
>> Thank you for the patch! I resolved the issue a bit differently,
>> making use of the SDDM and Plymouth systemd service file features a
>> bit more, and also fixing a few other potential issues in the same
>> run.
>> Could you please check if the new revision of the package fixes this
>> issue for you? (should be installed into the archive really soon)
> Hello,
> plymouth-quit.service is "static", whichcouldn't be enabled.
> It won't "done" without any other service run something equal to
> "plymouth --quit" (I guess).
Not sure what you mean... The SDDM .service-file specifying
After=plymouth-quit.service makes it run after plymouth-quit has been
executed. Since this is a dependency of SDDM, an attemt to start sddm
will invoke plymouth-quit first. The Conflicts directive will ensure
sddm is never started when plymouth-quit is still running. This is
maybe not necessary, since systemd will probably wait a little for
plymouth-quit to become "ready", but I added it to be sure about
Plymouth quitting.
I just checked, the same logic is used by GDM as well, so this should
work... And it works here as well (tested in a VM).
Can you maybe run systemctl list-jobs when sddm is failing to start,
to see if the job is waiting for something?
Cheers,
Matthias
