'getpwnam(): name not found: oem' error in OMAP4 10.10 images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ubiquity
Found on the OMAP 4 image from http://
Tested on a Blaze ES 2.0 board
After replacing the MLO and u-boot.bin files on the FAT partition, the system boots well, expands the rootfs partition, and reboots with no problem. However, the Ubiquity installer fails to execute then:
Traceback (most recent call last):
File "/usr/bin/
dm = DM(vt, display, username)
File "/usr/bin/
self.uid, self.gid = pwd.getpwnam(
KeyError: 'getpwnam(): name not found: oem'
Traceback (most recent call last):
File "/usr/bin/
dm = DM(vt, display, username)
File "/usr/bin/
self.uid, self.gid = pwd.getpwnam(
KeyError: 'getpwnam(): name not found: oem'
Early, it also said:
Checking filesystem before resizing... Done.
sh: X: unknown operand
done
... but this may not be related.
See the attached boot log.
Cheers,
Michael.
This bug was fixed in the package ubiquity - 2.3.19
---------------
ubiquity (2.3.19) maverick; urgency=low
* Make sure /var/lib/ ubiquity/ langpacks gets generated (LP: #630924).
* Fall back to root if the regular user cannot be found in
ubiquity-dm (LP: #640386).
* Properly handle dmimodel() returning the null string.
* Fix bootloader installation test (LP: #640341).
* Set a the respective timezone, both internally and visually, when an
entry is selected from the geonames autocompletion.
-- Evan Dandrea <email address hidden> Thu, 16 Sep 2010 13:22:19 +0100