Description of problem: Install F15-alpha-tc2 i386 dvd in kvm. After installation and reboot, firstboot welcome page prompted but failed to continue when clicking 'forward'. After clicking, login window prompted with no created user. Version-Release number of selected component (if applicable): firstboot-1.117-1.fc15.i686 How reproducible: Tried once. Steps to Reproduce: 1. Graphical install Alpha RC1 i386 2. Reboot and click 'forword' when firstboot window prompted Actual results: Unable to create user account through firstboot
Created attachment 480100 [details] /var/log/messages
(In reply to comment #1) > Created attachment 480100 [details] > /var/log/messages Feb 22 17:55:12 localhost systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131 Feb 22 17:55:14 localhost systemd[1]: Unit firstboot-graphical.service entered failed state. It looks like firstboot crashed based on the attached /var/log/messages. Can you reproduce this, and look in /tmp for a firstboot crash file? It should be named similar to /tmp/firstboot-<random>. If you find that file, please attach to the bug report. Thanks!
Actually... Feb 22 17:55:12 localhost systemd[1]: firstboot-graphical.service: main process exited, code=exited, status=131 Feb 22 17:55:14 localhost abrt[1091]: saved core dump of pid 971 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-1298415313-971.new/coredump (4009984 bytes) Feb 22 17:55:14 localhost abrtd: Directory 'ccpp-1298415313-971' creation detected Feb 22 17:55:14 localhost abrtd: Registered Database plugin 'SQLite3' Feb 22 17:55:14 localhost systemd[1]: Unit firstboot-graphical.service entered failed state. Xorg under firstboot crashed, but I don't know why. Did you _click_ the Forward button, or did you press Enter? Because I have a similar bug report already.
Discussed with jlaska out-of-meeting-cycle: we think we need more data on this to make a definite call on whether it's a blocker. We need more people to test and see if they hit trouble in firstboot.
(In reply to comment #3) > Xorg under firstboot crashed, but I don't know why. Did you _click_ the Forward > button, or did you press Enter? Because I have a similar bug report already. Oh, also ... can you clarify whether this was against TC2 or RC1?
(In reply to comment #2) > (In reply to comment #1) > > Created attachment 480100 [details] > > /var/log/messages > > Feb 22 17:55:12 localhost systemd[1]: firstboot-graphical.service: main process > exited, code=exited, status=131 > Feb 22 17:55:14 localhost systemd[1]: Unit firstboot-graphical.service entered > failed state. > > It looks like firstboot crashed based on the attached /var/log/messages. Can > you reproduce this, and look in /tmp for a firstboot crash file? It should be > named similar to /tmp/firstboot-<random>. If you find that file, please attach > to the bug report. Thanks! There's no firstboot* file under /tmp.
(In reply to comment #3) > Actually... > > Feb 22 17:55:12 localhost systemd[1]: firstboot-graphical.service: main process > exited, code=exited, status=131 > Feb 22 17:55:14 localhost abrt[1091]: saved core dump of pid 971 > (/usr/bin/Xorg) to /var/spool/abrt/ccpp-1298415313-971.new/coredump (4009984 > bytes) > Feb 22 17:55:14 localhost abrtd: Directory 'ccpp-1298415313-971' creation > detected > Feb 22 17:55:14 localhost abrtd: Registered Database plugin 'SQLite3' > Feb 22 17:55:14 localhost systemd[1]: Unit firstboot-graphical.service entered > failed state. > > Xorg under firstboot crashed, but I don't know why. Did you _click_ the Forward > button, or did you press Enter? Because I have a similar bug report already. I retested today, it's triggered by pressing *Enter* to the Forward button, clicking it can go forward.
*** This bug has been marked as a duplicate of bug 679171 ***
(In reply to comment #5) > (In reply to comment #3) > > Xorg under firstboot crashed, but I don't know why. Did you _click_ the Forward > > button, or did you press Enter? Because I have a similar bug report already. > > Oh, also ... can you clarify whether this was against TC2 or RC1? Firstboot wouldn't start automatically on TC2, but when I updated firstboot and made it run on TC2, this issue still happen.