Using the forward/back buttons at firstboot does not allow SELinux options do be changed - it is silently skipped.
Are you seeing a traceback appear in a dialog box when firstboot starts? Is there a /tmp/firstboot* or /root/firstboot* file?
I don't remember seeing any traceback. Certainly no dialog box appears. I've gone past firstboot now, so can't check for those files. You *can* change the SELinux options, but as soon as you push "Next", pushing "Previous" on the next screen skips SELinux for the option before.
It seems that the back button actually jumps over/skips every other completed option.
Hm, I'm not seeing this. Is there any other information you can think of that would be helpful in debugging this?
I am running this from a VMware machine. Perhaps you could run it from there too? http://www.thoughtpolice.co.uk/vmware/#fedora8t1 I can send you the activation code if you want it.
This may be due to irregularities in vmware input handling, such that it's receiving double the mouse clocks or something like that. Are you able to reproduce this on regular hardware? I have not seen this here, nor has anyone in QA.
Irregularities that only occur during firstboot? Hm.. Wouldn't that be a vmware mouse drive issue in Fedora then? I'll manually run firstboot again (if it will let me) and see what happens. I don't have any physical hardware to test this on.
Yeah, I'll admit we're just reaching for things here. However I've had several people test this out on fresh installs and no one has run into this problem, nor have I seen any other bugs about this issue. It seems to me that it must be something unique to your setup, and vmware is what immediately comes to mind.
Running firstboot manually works fine (but tested over vnc..)
When you say that running it manually works, do you mean that you are running it from a command line still inside vmware?
Running firstboot from a fresh install (in vmware) works (also over vnc). I will say that it _did_ skip over License Information once, but I can't reproduce that. What next? :)
(In reply to comment #10) > When you say that running it manually works, do you mean that you are running it > from a command line still inside vmware? $ ssh -CX hostname $ vmware& $ vncviewer then start Workstation, "boot" F8T1, edit /etc/sysconfig/firstboot, then run firstboot.
We are unable to reproduce this with F8 test 2 under vmware. Feel free to reopen this bug if you test with a later release and are still seeing this problem.