[Bug 792652] Re: ubiquity crashed with ValueError in command(): I/O operation on closed file

[vel]

Originally tried to install BlenderBuntu 11.10 onto a USB flash drive
(drive alpha); BIOS doesn't detect it as bootable (skips to default boot
from HD to windows). Thought it was a problem with the drive, tried
installing on 2nd (drive beta - overwriting "security software" included
with drive); still no detection. Burned a boot installation CD and
proceeded to partition both drives wih 6 GB FAT32 6GB ext4 rest swap
(16GB drive alpha), install to... ext4 I'm guessing (no idea if it
succeeded); reboot on install completion and no boot. Retried process
with other USB flash drive and same result.

Gave Ubuntu 12.04 a shot. In Windows, downloaded desktop ISO and utility
linked from Ubuntu website that allowed me to write the image straight
to the USB flash drive (drive alpha - partitioning / formatting from
previous attempt intact). On restart, no boot. Back in windows,
performed the same procedure on drive beta. Reboot... instead of getting
the installation screen that a CDROM bootable installation setup would
give me, it leaves me on the same black screen you see when the BIOS
finishes listing hard drive S.M.A.R.T. info and BIOS IRQ assignments
with a message saying something along the line of "kernel not found" or
path to or something, the next line a colon followed by I guess me
having to enter the path to said kernel. (No previous knowledge of what
a kernel file looked like, so I rebooted).

(omitting various live test runs of U12.04LTS desktop from cd boots)
(omitting attempt to CD-boot, install 12.04 to drive alpha - forgot the outcome)

CD booting the Ubuntu 12.04 installer (onto drive beta), I tell it to
Upgrade existing 11.10 install to 12.04. On the screen after that where
it requires me to hit next, a popup appears and says partition /cdrom
must be unmounted before it can continue... I was like, "Huh?" I thought
I was installing from said CD mount... I click next to disregard, and
the system seemed to hang. Clicking previous, next, hitting the x on the
popup - no sound or activity from any drives or CD. Soft rebooted.

2nd attempt at above install on (beta). Same steps, though this time, my
CD wasn't making any noise (on Ubuntu, it always maxes out the drive rpm
on any reads, it's very noticeable). Chose Upgrade existing 11.10 to
12.04. The next screen, instead of the previous "unmount /cdrom" prompt,
tells me I need to make my partition larger than 2.5 GB to install.
Strange, though, as the next screen which is the partition manager
setup, tells me my USB drive is 6GB FAT32 1GB ext4 1GB something else,
remainder swap (I don't know at what point the middle ext4 turned into
two drives). Also strange is that, on all my previous install attempts
and live sessions, my two FAT32 drives connected through my ancient
Promise ATA 100 raid (not configured for any striping) aren't showing up
in the manager this time. At any rate, deleted the 1/1/rest partitions
(left 6GB FAT32 unchanged) and went something with 6/6/rest
FAT32/ext4/swap. Tried hitting next, gave me "can't install without a
file system yet being defined" message (which I've seen trying from
trying BlenderBuntu manual partitioning - it's always stopped me).
Cleared the message; this time, there's a distinct delay (presumably
from setup updating info from the drives - this never happened when I
tried all my previous manual partitioning with the "file system yet
defined" error) with the cursor in busy mode, before it returns to
normal. I click next, still on the partition manager screen - instead of
getting that same error again - it lets me through... or not, I don't
remember. Next thing was "Ubuntu has met with an error and cannot
continue, please send this to the bugtracker."

Maybe this (part of the) bug's been fixed by now, who knows. All I know
is, my BIOS doesn't like USB flash drives.

Drive alpha: PNY 16GB USB 2.0
Drive beta: Sandisk Cruzer 16GB USB 2.0
Mobo: Gigabyte P35-3SDL rev?? - no BIOSes available that address USB flash/zip drive boot problems

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/792652

Title:
  ubiquity crashed with ValueError in command(): I/O operation on closed
  file

Status in “ubiquity” package in Ubuntu:
  Fix Released
Status in “ubiquity” source package in Oneiric:
  Won't Fix
Status in “ubiquity” source package in Precise:
  Fix Released

Bug description:
  Binary package hint: ubiquity

  I got this problem when I was trying clicking the Install Ubuntu 11.04
  from the desktop on Asus 1215B red.

  TEST CASE
  1. Boot from a Live media
  2. At Ubiquity Greeter click on 'Try Ubuntu' and start a live session
  3. Start ubiquity
  4. Proceed to step 'Prepare'
  5. Click on 'Continue' then quickly click on 'Quit' on the main dialog then 'Quit' on the confirmation dialog before the UI switches to step 'partman'

  Note:
  Timing seems important and you need to repeat steps 3 to 5 and clicking at slightly different moment until it crashes. It is easier to reproduce on low-end hardware than VM.
  Also I reproduced it more often with other languages than english.

  ACTUAL RESULT
  This crash or UI hang

  ProblemType: Crash
  DistroRelease: Ubuntu 11.04
  Package: ubiquity 2.6.10
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: wl
  Architecture: amd64
  Date: Fri Jun  3 21:24:09 2011
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InterpreterPath: /usr/bin/python2.7
  LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  ProcCmdline: /usr/bin/python /usr/lib/ubiquity/bin/ubiquity gtk_ui
  ProcEnviron: Error: [Errno 13] Permission denied: '/proc/3371/environ'
  PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
  SourcePackage: ubiquity
  Title: ubiquity crashed with ValueError in command(): I/O operation on closed file
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/792652/+subscriptions