tiomap-dev team mailing list archive

[Launchpad Bug Tracker <640386@xxxxxxxxxxxxxxxxxx>]

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 <evand@xxxxxxxxxx>   Thu, 16 Sep 2010 13:22:19 +0100

** Changed in: ubiquity (Ubuntu)
       Status: New => Fix Released

-- 
'getpwnam(): name not found: oem' error in OMAP4 10.10 images
https://bugs.launchpad.net/bugs/640386
You received this bug notification because you are a member of TI OMAP
Developers, which is a direct subscriber.

Status in “ubiquity” package in Ubuntu: Fix Released

Bug description:
Binary package hint: ubiquity

Found on the OMAP 4 image from http://cdimage.ubuntu.com/ubuntu-netbook/ports/daily-preinstalled/20100916/.
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/ubiquity-dm", line 531, in <module>
    dm = DM(vt, display, username)
  File "/usr/bin/ubiquity-dm", line 94, in __init__
    self.uid, self.gid = pwd.getpwnam(self.username)[2:4]
KeyError: 'getpwnam(): name not found: oem'
Traceback (most recent call last):
  File "/usr/bin/ubiquity-dm", line 531, in <module>
    dm = DM(vt, display, username)
  File "/usr/bin/ubiquity-dm", line 94, in __init__
    self.uid, self.gid = pwd.getpwnam(self.username)[2:4]
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.