OSError: [Errno 25] Inappropriate ioctl for device

The root cause of this is a missing entry in the upstart init config: /etc/init/oem-config.conf

Specifically, the upstart config is not attaching STDIN to the job.

The attached patch fixes this.

Looks like this was the offending commmit:
http://bazaar.launchpad.net/~ubuntu-installer/ubiquity/trunk/revision/6027

The attachment "instruct upstart to attach STDIN to job" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

This bug was fixed in the package ubiquity - 2.19.5

---------------
ubiquity (2.19.5) utopic; urgency=medium

  * Re-add "console output" stanza to the oem-config upstart job to
    re-instate stdin/stdout. (LP: #1361595)
  * Automatic update of included source packages: netcfg 1.119ubuntu1.
 -- Dimitri John Ledkov <email address hidden> Sun, 31 Aug 2014 23:52:22 +0100

Hello Jamin, or anyone else affected,

Accepted ubiquity into trusty-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubiquity/2.18.8.4 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Chris,

I may be looking in the wrong area, but from the provided link I can only find three binaries built for amd64 (https://launchpad.net/ubuntu/+source/ubiquity/2.18.8.4/+build/6716449):

Binary packages
Binary packages produced by this build:

ubiquity 2.18.8.4
ubiquity-frontend-debconf 2.18.8.4
ubiquity-frontend-gtk 2.18.8.4
Built files
Files resulting from this build:

ubiquity-frontend-debconf_2.18.8.4_amd64.deb (437.8 KiB)
ubiquity-frontend-gtk_2.18.8.4_amd64.deb (84.5 KiB)
ubiquity_2.18.8.4_amd64.deb (4.9 MiB)

However the file in question (/etc/init/oem-config-debconf.conf) is owned by oem-config-debconf, which is not one of the built packages. Furthermore, this is only one of several issues preventing the oem-config package from working on server installations.

As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of ubiquity from trusty-proposed was performed and bug 1417834 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the "verification-failed" tag from this bug report and tag 1417834 "bot-stop-nagging". Thanks!

Removing verification-failed; the fix appears to be good at first glance, but I'll run a more careful test now to be able to mark this verfiication-done if I can.

The OEM installation appears to work properly using trusty-server-amd64.iso, so I'll go ahead and mark this verification-done.

One issue however, which is unrelated to oem-config itself is that I am unable to start an OEM installation straight from the gfxboot menu on the CD (using a VM), something which worked for 14.04.1. One needs to manually add oem-config/enable=true to the boot parameters to get into an OEM install.

This bug was fixed in the package ubiquity - 2.18.8.4

---------------
ubiquity (2.18.8.4) trusty; urgency=medium

  * Re-add "console output" stanza to the oem-config upstart job to
    re-instate stdin/stdout. (LP: #1361595)
 -- Dimitri John Ledkov <email address hidden> Sun, 21 Dec 2014 07:05:55 +0000

The verification of the Stable Release Update for ubiquity has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.