Description of problem: Firstboot does not get installed even though it is in the comps group. Version-Release number of selected component (if applicable): Fedora 18 beta TC2 How reproducible: always Steps to Reproduce: 1. Select LXDE during install. 2. Reboot when finished. Actual results: LXDM shows up, but you cannot log in as no user was created. # rpm -q firstboot package firstboot is not installed. Expected results: firstboot Additional info: firstboot is in the lxde-desktop group and according to anaconda-ks.cfg, that group was installed. I am proposing this as a blocker for beta because - It violates an alpha release criterion: "Following on from the previous criterion, after firstboot is completed and on subsequent boots, 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 a working graphical environment without unintended user intervention." - If prevents testing further release criteria like being able to play sound, open a browser etc. We should think about another release criteria: "If a desktop environment was installed, a user must be created and this user must be able to successfully log in." If one does not unlock the root account, one ends up with a useless installation.
Please attach /var/log/anaconda/anaconda.packaging.log from the installed system to this bug report. Thanks.
Created attachment 623541 [details] /var/log/anaconda/anaconda.packaging.log Here you are.
Oh, I see. This is because we default to selecting the GNOME desktop group. Then when you change environments, we first apply your selection and then apply the removal of the GNOME environment. This means that firstboot gets marked for removal after it gets marked for adding. Guess which one wins.
Yeah, I guessed that when looking at the log. I'm afraid we'll face the same problem with a lot more groups. if we follow this logic, the package selection will become completely unpredictable. How did anaconda resolve this in the past?
The package selection and packaging backends were completely different in the past. We just need to be a little less enthusiastic in our removals here. Posting a patch to the list after this test finishes up.
Christoph: we do in fact have a criterion to cover this already, it's right before the one you cited: "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 " It's entirely natural to fall asleep halfway through reading that, but if you fight through it, it does require firstboot to run and be able to create a user account on the first boot after a graphical install. :) +1 blocker.
Discussed at 2012-10-10 blocker review meeting: http://meetbot.fedoraproject.org/fedora-qa/2012-10-10/f18beta-blocker-review-3.2012-10-10-16.05.log.txt . Accepted as a blocker per criterion cited in comment #6 - this will affect KDE installs, so it affects a release-blocking desktop, so blocker.
anaconda-18.15-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.15-1.fc18
Package anaconda-18.15-1.fc18: * 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 anaconda-18.15-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15903/anaconda-18.15-1.fc18 then log in and leave karma (feedback).
anaconda-18.16-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.16-1.fc18
This is fixed with F18 Beta TC4.
anaconda-18.17-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.17-1.fc18
Package anaconda-18.17-1.fc18: * 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 anaconda-18.17-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16295/anaconda-18.17-1.fc18 then log in and leave karma (feedback).
back to VERIFIED. i should really file a bug with Luke that bodhi shouldn't change bugs from VERIFIED to ON_QA...
anaconda-18.18-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.18-1.fc18
Package anaconda-18.18-1.fc18: * 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 anaconda-18.18-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16402/anaconda-18.18-1.fc18 then log in and leave karma (feedback).
anaconda-18.19-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/anaconda-18.19-1.fc18
Package anaconda-18.19-1.fc18: * 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 anaconda-18.19-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16528/anaconda-18.19-1.fc18 then log in and leave karma (feedback).
Fixed, anaconda stable, closing.