Ubiquity cannot be fully preseeded when using oem-config mode

Bug #321341 reported by Twisted Lincoln, Inc.
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubiquity (Ubuntu)
Fix Released
Medium
Colin Watson

Bug Description

Binary package hint: ubiquity

NOTE: tested using Intrepid (8.10)

When using oem-config mode (oem-config/enable=true) along with a preseed file, you cannot preseed all options of Ubiquity. The page in which you would normally select the oem user's password, and the system's hostname is always displayed.

I suspect this is due to the fact that you cannot preseed netcfg values when using Ubiquity. As a result, there is no way to preseed the hostname value that is on this page, causing Ubiquity to always display it.

Looking at the behavior of the same page when not in oem-config mode, it appears that the hostname is by default automatically set (as you type) to "username-desktop" or "username-laptop." As a result, preseeding works just fine when in normal mode. Whatever you specify as the username is simply placed as the first section of the hostname.

I propose that the same is true using oem-config mode: the default hostname in this field should be "oem-desktop" or "oem-laptop." The user could of course override this when in installing normally, but adding this should allow Ubiquity to be fully preseeded in oem-config mode, just like normally.

Related branches

description: updated
Revision history for this message
Colin Watson (cjwatson) wrote :

Committed - thanks for the idea! Of course, we should fix hostname preseeding at some point too.

Changed in ubiquity:
assignee: nobody → kamion
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubiquity - 1.11.5

---------------
ubiquity (1.11.5) jaunty; urgency=low

  [ Evan Dandrea ]
  * Full screen the window when in ONLY_UBIQUITY mode. The extra screen
    real estate makes the timezone map, among other widgets, easier to
    use.
  * Modified the keyboard setup page to produce a more visually obvious
    suggestion.
  * Automatic update of included source packages: grub-installer
    1.36ubuntu1, localechooser 2.09ubuntu1, user-setup 1.23ubuntu8.

  [ Mario Limonciello ]
  * Adjust logic for detecting incomplete language support. Just
    because a package doesn't "exist" doesn't mean that language support
    isn't all there. Some packages don't yet provide language-support-XY
    packages. (LP: #290398)

  [ Colin Watson ]
  * Remove old XFS-on-/boot validation, no longer needed now that
    grub-install has been fixed (LP: #8058).
  * Default hostname to 'oem-laptop' or 'oem-desktop' as appropriate in OEM
    mode, to allow OEM installations to be fully preseeded (thanks, Twisted
    Lincoln, Inc.; LP: #321341).

 -- Evan Dandrea <email address hidden> Wed, 28 Jan 2009 17:00:46 +0000

Changed in ubiquity:
status: Fix Committed → Fix Released
Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

There is either a regression in karmic or this was never fully fixed. It is not possible to perform an automated install in oem-config mode as the "Who are you page?" is still displayed. The hostname field is populated but not disabled like the username. However, I think the real reason this page is being displayed is because its looking for a password for the oem account. Manually seeding the related questions (both using a password and also using no password) seems to have no effect - the page is always displayed.

Changed in ubiquity (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Evan (ev) wrote :

I cannot reproduce this using today's CD (possibly the final 9.10 image). Can you please provide a sample preseed?

Changed in ubiquity (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Brian Pitts (bpitts) wrote :

I cannot reproduce this on 9.10 final.

Revision history for this message
Cody A.W. Somerville (cody-somerville) wrote :

It turns out I was running into another bug (forget the number right now but the issue is the need to re-seed what oem-config seeds to have full automation).

Changed in ubiquity (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.