Red Hat Bugzilla – Bug 852875
firstboot's service file needs updating for replacement of prefdm.service with per-dm services and systemd presets
Last modified: 2012-09-07 19:18:54 EDT
So we have this whole mess going on where prefdm.service has been replaced with a service file for each DM, a display-manager.service alias, and these new systemd 'presets'.
I don't claim to totally understand what's going on, but I know for sure we need to change this line in firstboot-graphical.service:
somehow. I am not sure if just:
would work (as every *dm.service file is supposed to have Alias=display-manager.service), or if we'd need to do something bigger:
Before=display-manager.service gdm.service kdm.service lxdm.service lightdm.service (etc etc etc)
as I don't know how systemd handles Before/After when it comes to aliases, and the manpage doesn't seem to explain it.
CCing Lennart for info on this.
Marking as an Alpha blocker, because the consequence of this is that firstboot and gdm try to run at the same time on the first boot after install, which is an infringement of "In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. The firstboot utility must be able to create a working user account".
CCing vpodzime as msivak is on vacation by the end of August.
*** Bug 853048 has been marked as a duplicate of this bug. ***
Well, in a quick test just 'Before=display-manager.service' seemed to be enough - I tested by hacking that into firstboot-graphical.service, enabling firstboot, and booting, on a freshly-installed system. firstboot ran and I was able to complete it, gdm didn't pop up over the top.
firstboot-18.2-2.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing firstboot-18.2-2.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Discussed at 2012-09-05 blocker review meeting. Accepted as a blocker per criterion "In most cases, a system installed according to any of the above criteria must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. The firstboot utility must be able to create a working user account".
Two people reported it works in the Bodhi feedback, so setting VERIFIED.
firstboot-18.2-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.