tried to reinstall Precise alpha 1 on exisiting install-installer crash

[Dale Beaudoin]

installer crash

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ubiquity 2.9.5
ProcVersionSignature: Ubuntu 3.2.0-2.5-generic 3.2.0-rc3
Uname: Linux 3.2.0-2-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CasperVersion: 1.292
Date: Sat Jan 7 16:03:51 2012
LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcEnviron:
 LANGUAGE=en_CA.UTF-8
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu Foundations Team Bug Bot (crichton)]

Exception during installation:
Dec 7 14:55:19 ubuntu install.py: Traceback (most recent call last):
Dec 7 14:55:19 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 656, in <module>
Dec 7 14:55:19 ubuntu install.py: install.run()
Dec 7 14:55:19 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 130, in run
Dec 7 14:55:19 ubuntu install.py: self.copy_all()
Dec 7 14:55:19 ubuntu install.py: File "/usr/share/ubiquity/install.py", line 423, in copy_all
Dec 7 14:55:19 ubuntu install.py: install_misc.copy_file(self.db, sourcepath, targetpath, md5_check)
Dec 7 14:55:19 ubuntu install.py: File "/usr/lib/ubiquity/ubiquity/install_misc.py", line 621, in copy_file
Dec 7 14:55:19 ubuntu install.py: targetfh.write(buf)
Dec 7 14:55:19 ubuntu install.py: IOError: [Errno 22] Invalid argument
Dec 7 14:55:19 ubuntu install.py:
Dec 7 15:02:38 ubuntu ubiquity:
Dec 7 15:02:38 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:38 ubuntu ubiquity:
Dec 7 15:02:38 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:38 ubuntu ubiquity:
Dec 7 15:02:38 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:38 ubuntu ubiquity:
Dec 7 15:02:38 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:39 ubuntu ubiquity:
Dec 7 15:02:39 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:39 ubuntu ubiquity:
Dec 7 15:02:39 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:39 ubuntu ubiquity:
Dec 7 15:02:39 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:02:39 ubuntu ubiquity:
Dec 7 15:02:39 ubuntu ubiquity: (firefox:9503): Gtk-WARNING **: Unable to locate theme engine in module_path: "pixmap",
Dec 7 15:04:37 ubuntu ubiquity[3796]: log-output -t ubiquity apport-bug ubiquity
Dec 7 15:04:38 ubuntu ubiquity[3796]: Reverting lockdown of the desktop environment.
Dec 7 15:04:44 ubuntu ubiquity[3796]: Reverting lockdown of the desktop environment.
Dec 7 15:04:59 ubuntu acpid: client connected from 9630[0:0]
Dec 7 15:04:59 ubuntu acpid: 1 client rule loaded
Dec 7 15:05:08 ubuntu gnome-session[9645]: WARNING: Session 'ubuntu' runnable check failed: Exited with code 1
Dec 7 15:05:40 ubuntu gnome-session[9645]: WARNING: Could not launch application 'gdu-notification-daemon.desktop': Unable to start application: Failed to execute child process "/usr/lib/i386-linux-gnu/gdu-notification-daemon" (No such file or directory)
Jan 7 10:15:29 ubuntu kernel: imklog 5.8.6, log source = /proc/kmsg started.
Jan 7 10:15:29 ubuntu rsyslogd: [origin software="rsyslogd" swVersion="5.8.6" x-pid="2160" x-info="http://www.rsyslog.com"] start
Jan 7 10:15:29 ubuntu rsyslogd: rsyslogd's groupid changed to 103
Jan 7 10:15:29 ubuntu rsyslogd: rsyslogd's userid changed to 101
J...

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 894768, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.