Created attachment 356161 [details] /var/log/ Description of problem: can not log in gnome after f12 installed. There is no input box for user to enter user name and password Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. install f12 alpha with DVD 2. after finished installation, reboot 3. For gnome, there is no input box for user to enter user name and password. system log displays that service atd failed. see more details from attached log Actual results: Expected results: Additional info:
Ahh, could this be a result of the firstboot failure bug (which is now fixed in rawhide)? gdm's default config won't allow logins by root user anymore, and since firstboot was failing to start, there was no graphical way to create users to login as from gdm. Liam: I'm curious if this it the problem here. Can you try ... 1. useradd -p '' guest (perhaps from tty2) 2. then attempt to login as that user?
> Liam: I'm curious if this it the problem here. > > Can you try ... > 1. useradd -p '' guest (perhaps from tty2) > 2. then attempt to login as that user? you are right, after added an user, we can log in. I tested this on rawhide 2009-08-11. the issue is the same as before, after installation completed,reboot system,there is no welcome and setting up for first starting as f11, we go to gdm directly, even you click login button,no input box appears as expected.This is by design?At least,we need to prompt user to create an user.
(In reply to comment #2) > This is by design? At least,we need to prompt user to create an > user. You're right Liam, this isn't by design. It appears to be the result of a bug in firstboot (see bug#515419). That issue appears to be resolved now in an updated firstboot package included in rawhide (and F-12-Alpha). If no non-root users exist on the system, I think it's expected that there is nobody to login to gdm as. I'm going to close this issue out as a duplicate of the underlying firstboot issue. Please feel free to comment if there are any concerns. *** This bug has been marked as a duplicate of bug 515419 ***