poor error handling - lack of recovery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oem-config (Ubuntu) |
Fix Released
|
Medium
|
Colin Watson |
Bug Description
Binary package hint: oem-config
I installed gutsy 20071016.1 i386 d-i in oem mode in English (with auto-resize of another gutsy test install):
During the oem boot I:
* Fiddled a bit with the Software Sources to remove the CD entry
* Installed libadns1-bin using Synaptic
* Created a user called "guest" using System / Administration / Users and Groups, in the most obvious way
Then I double-clicked on "prepare for shipping to end-user" which appeared to work, and rebooted.
When I rebooted the usual "enter your details" dialogue appeared as expected. I provided my language (Dutch), keyboard (British English) and timezone (Language) and was asked for my name and username and password.
When I confirmed my entering the password for the second time, the X server died immediately (black screen) and I was presented with a gdm prompt. The user and password I had provided during user firstboot did not work (I didn't try the guest user). I rebooted into the other install for forensics and found that the main admin user did not exist.
I am filing another bug about the fact that this problem was apparently caused by the fact that I created a user during the OEM preparation which I think ought to be supported.
This bug is about the fact that the oem firstboot program crashed leaving me with an unuseable setup. When the oem firstboot fails it ought to at least present the user with a useful error message and preferably it should try to avoid getting into a situation where the install is irrecoverably broken when it fails.
Related branches
Changed in oem-config: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
Changed in oem-config: | |
assignee: | nobody → kamion |
status: | Confirmed → Fix Committed |
The other bug I refer to, about support for oem-created users, is bug 153310.