On 14/09/15 14:27, Zhang Jingqiang wrote: >>> 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? > No tty is available when waiting for plymouth-quit (5 minutes +, no timeout > set), I will check later with log level set to debug.
In the latest upload of sddm (0.12.0-3) I've modified the service file after long session of tests. I've started them with the version in testing (0.12.0-1), and plymouth worked fine with most of the themes but, not with glow spinfinity and spinner. Using the version from unstable it produced the breakage almost always. It seems that the one of the important points is that display managers are supposed to start after the quit-wait plymouth service, and not the -quit one. gdm3 has some special code to handle the status of plymouth once started while sddm doesn't handle this correctly. Please check, and if you can still reproduce the issue with sddm 0.12.0-3, please reopen the bug. Happy hacking, -- "The sooner you start to code, the longer the program will take." -- Roy Carlson Saludos /\/\ /\ >< `/
signature.asc
Description: OpenPGP digital signature
