just installed fedora 18 beta. On firstboot I tried creating additional users from the advanced user creation program. When I finished creating users, I was trying to figure out what to click so I tried file->quit That terminated firstboot and left me without any usable users on the system. Then I was unable to run firstboot again but that's another bug I'll file.
Summary: If you invoke the advanced user dialog in firstboot (system-config-user), it has a File->Quit menu. If you use it, it will also exit firstboot. You will arrive in GDM and there won't be any user created (even though you have created them in the application, according to Aleksandar). After reboot the firstboot is not run again, so the only way how to create a user is from the root console. Closing the dialog using X button works fine. We might want to discuss this in the blocker bug meeting.
I can confirm the behaviour from the source code side. We instantiate the window of System Config Users using python imports and use it as a library. When SCU calls exit from it's menu system, it terminates the containing process - firstboot. There are two possible ways to fix this: 1) we can catch the SystemExit exception from SCU in firstboot and ignore it, that would probably fix the issue 2) firstboot passes firstboot=True to SCU when invoking it and SCU could use that to not quit the application, but only return from the mainloop
We have discovered that this problem appears also in F17. I and adamw used s-c-u to create a user and then introduce the forced exit and our users existed in the final system. I don't know why that didn't work for Aleksander. Currently it seems that the only way to get a system without any user is to open the dialog and the close it "the wrong way".
Discussed at 2012-12-12 blocker review meeting: http://meetbot.fedoraproject.org/fedora-bugzappers/2012-12-12/f18final-blocker-review-4.2012-12-12-17.01.log.txt . Rejected as a blocker: this behaviour is no different from prior releases and our testing indicated that a user created in s-c-u before triggering this bug *does* exist and can be logged in with via gdm. So the impact isn't bad enough for this to be a blocker.
We left NTH status open: there's some concern about poking user creation code in firstboot this late for what is a relatively minor bug, but we may take it, if the fix looks small enough and tests out.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
The firstboot utility is deprecated and no longer developed in Fedora 19 and newer releases. It was replaced by the initial-setup utility with a completely different codebase. If you still have any similar problems with Fedora 19 or later, please file a new bug against initial-setup or gnome-initial-setup if you did a GNOME install.