Description of problem: The Initial Setup (the first boot utility) needs to run before a login prompt is shown because its purpose is to create user account and setup root password. However, in order to do that, all getty@*.service and serial-getty@*.service services need to wait for it to finish which is impossible to achieve with uknown TTYs and serial TTYs. The reason is that the Before field of the unit file doesn't allow to specify 'getty@*.service' or 'getty@service' (without any particular TTY). Version-Release number of selected component (if applicable): systemd-207.4-fc20 Actual results: No way for a service to specify all (serial-)getty services should wait for it to finish. Expected results: Easy way for a service to specify all (serial-)getty services should wait for it to finish.
Would specifying Before=systemd-user-sessions.service in that service work for you? systemd-user-sessions.service is the thing that actually allows user to log in, both through e.g. ssh and on the console.
(In reply to Zbigniew Jędrzejewski-Szmek from comment #1) That would not work for Vratislav, because he also wants his unit to run After=plymouth-quit-wait.service, which itself runs After=systemd-user-sessions.service, so an ordering loop would appear.
I'd suggest to do what Zbigniew suggested, but in the program to be run simply terminate the plymouth screen directly, so that plymouth-quit-wait.service later on will turn into a NOP... That sounds easiest to me... i.e. to initial-setup add /usr/bin/plymouth --wait and then order it before systemd-user-sessions.service.
(In reply to Lennart Poettering from comment #3) > I'd suggest to do what Zbigniew suggested, but in the program to be run > simply terminate the plymouth screen directly, so that > plymouth-quit-wait.service later on will turn into a NOP... That sounds > easiest to me... > > i.e. to initial-setup add /usr/bin/plymouth --wait and then order it before > systemd-user-sessions.service. Would adding 'ExecStopPost=/usr/bin/plymouth --wait' work the same way? I'd really like to avoid adding some Plymouth-specific code to the initial-setup's code. BTW, initial-setup has a new mantainer now.
(In reply to Vratislav Podzimek from comment #4) > Would adding 'ExecStopPost=/usr/bin/plymouth --wait' work the same way? You mean ExecStartPre ? Yes, it should work the same way.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still an issue even on F22.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Still a (systemd) issue, unfortunately.
Bad bot, no cookie for you! ;-)
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle. Changing version to '25'.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.