[Bug 1400425] Re: how can it solve?

[Seth Arnold]

Interesting, it failed because an 's' was in the md5sums of a package
listing. That almost feels like a hardware error to me, a single flipped
bit could do this. I suggest trying again.

Thanks

-- 
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/1400425

Title:
  how can it solve?

Status in ubiquity package in Ubuntu:
  New

Bug description:
  help me please

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: ubiquity 2.18.7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  Date: Mon Dec  8 23:48:57 2014
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- iso-scan/filename=/images/images/ubuntudesktopamd64.iso maybe-ubiquity
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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