Using mouse or tab+space to activate the Next button works fine. Using Tab+Enter causes firstboot to exit and gdm to launch. On the next boot firstboot runs again.
abrt says that Xorg crashed:
Feb 21 13:50:40 localhost systemd: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 21 13:50:41 localhost abrt: saved core dump of pid 877 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-1298314241-877.new/coredump (5849088 bytes)
Feb 21 13:50:41 localhost abrtd: Directory 'ccpp-1298314241-877' creation detected
Feb 21 13:50:41 localhost abrtd: Registered Database plugin 'SQLite3'
Feb 21 13:50:41 localhost systemd: Unit firstboot-graphical.service entered failed state.
Feb 21 13:50:42 localhost systemd: Startup finished in 904ms 660us (kernel) + 5s 252ms 649us (initrd) + 38s 54ms 516us (userspace) = 44s 211ms 825us.
Feb 21 13:50:42 localhost abrtd: New crash /var/spool/abrt/ccpp-1298314241-877, processing
Feb 21 13:50:42 localhost abrtd: Registered Action plugin 'RunApp'
Feb 21 13:50:42 localhost abrtd: RunApp('/var/spool/abrt/ccpp-1298314241-877','test x"`cat component`" = x"xorg-x11-server-Xorg" && cp /var/log/Xorg.0.log .')
Feb 21 14:11:24 localhost systemd: firstboot-graphical.service: main process exited, code=exited, status=131
Feb 21 14:11:26 localhost abrt: saved core dump of pid 865 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-1298315485-865.new/coredump (7897088 bytes)
Feb 21 14:11:26 localhost abrtd: Directory 'ccpp-1298315485-865' creation detected
Feb 21 14:11:26 localhost systemd: Unit firstboot-graphical.service entered failed state.
Feb 21 14:11:26 localhost systemd: Startup finished in 900ms 274us (kernel) + 7s 79ms 581us (initrd) + 1min 5s 868ms 285us (userspace) = 1min 13s 848ms 140us.
Feb 21 14:11:26 localhost abrtd: Crash is in database already (dup of /var/spool/abrt/ccpp-1298314241-877)
Feb 21 14:11:26 localhost abrtd: Deleting crash ccpp-1298315485-865 (dup of ccpp-1298314241-877), sending dbus signal
Created attachment 479982 [details]
So this only happens when firstboot is run as a systemd service during boot. I tried running it in Gnome, and Enter works fine. I tried also killing Xorg, and then running firstboot from vt2 in runlevel 5, and pressing Enter works OK too.
When this happens, abrt says that Xorg was killed with signal 11 (SIGSEGV). I don't know what's causing this. Only thing that comes to my mind is that Xorg needs some other service to be running before we run the firstboot service.
Adam, do you know what can be the problem here?
*** Bug 679348 has been marked as a duplicate of this bug. ***
679348, which was marked as a dupe of this, was proposed as F15Alpha, so moving that nomination to this bug.
Patch under review on anaconda-devel-list (see https://www.redhat.com/archives/anaconda-devel-list/2011-February/msg00235.html)
discussed at 2011-02-23 go/no-go meeting: agreed not a blocker as it's eminently workaround-able and if you reboot you get to try again. will document for release.
So I found out firstboot crashes if you press the key "2" on the keyboard, which is not workaround-able (bug #679933). It's caused by the same thing as this "Enter exit", running plymouth. I think it would be nice to have this fix. Who knows what other keys can make firstboot crash or exit.
Yes - since we've already slipped I'd definitely like to take a fix for this into RC2. Proposing NTH.
From alpha blocker meeting:
#agreed 679171 accepted as NTH
RC2 will likely get spun tonight (~6hrs from now) so we need a build in and tested by then to make it. bcl will try to get a build done in time.
* should fix your issue,
* was pushed to the Fedora 15 updates-testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing firstboot-1.117-2.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
We really need testing on the fix (from bcl, thanks) in the next few hours. Unfortunately you may need to spin a live image with the fix included to test it properly, but there may be other ways to do it I hadn't thought of yet.
actually, just doing an install and switching to a vt on first boot to install the updated firstboot, then switching back to firstboot and making it crash should work - it will then respawn itself, using the updated version, and you should no longer be able to crash it.
firstboot-1.117-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
drop commonbugs, as this was fixed for alpha.