[Bug 652916] Re: wrong bug duplication - ubiquity-dm crashed with ValueError in command(): invalid literal for int() with base 10: ''

[Brian Murray]

Looking at this bug and bug 897270 it seems odd to me that the
Traceback.txt doesn't appear in the UbiquitySyslog file at all.
Additionally, looking at all the duplicates the latest version of
ubiquity that this (the traceback disconnect) happened in was version
2.6.10 from Natty and 2.7.10 which is no longer available.  So I'm not
certain this really needs fixing anymore.

Having said that the Traceback.txt in this report is very generic and it
would be helpful to blacklist it as a duplicate signature if possible.

** Changed in: apport (Ubuntu)
       Status: Fix Committed => Incomplete

** Changed in: apport (Ubuntu)
       Status: Incomplete => New

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

Title:
  wrong bug duplication - ubiquity-dm crashed with ValueError in
  command(): invalid literal for int() with base 10: ''

Status in “apport” package in Ubuntu:
  New
Status in “ubiquity” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: ubiquity

  happened on maverick beta from 30th of september when trying to
  install in VirtualBox under 10.04.

  From bug 706395:
  This crash happened while installing natty (daily build from 1/21/2011).

  1. Booted from CD burned with natty-desktop-amd64.iso
  2. Selected "install"
  3. Selected manual partitioning and specified the following:
         Existing /dev/sda10 used for root (/), formatted with ext4.
         Existing /dev/sda7 used for /home (not reformatted)
  4. Clicked the button to install

  The installer dialog said "copying files..."

  Then the purple ubuntu desktop appeared, the new one.
  Seemingly nothing else happened.

  After a while several crash dialogs appeared offering to "Report
  Problem...". One of them led to this crash report.

  The install was apparently part-way through: The new root fs was
  mounted at /target and contained lots of stuff.

  
  ===
  Same on liveCD without installing:
  - Boot from USB
  - Select Try Ubuntu
  - Ubiquity crash when the session starts.

  ProblemType: Crash
  DistroRelease: Ubuntu 10.10
  Package: ubiquity 2.4.4
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  Architecture: i386
  Date: Fri Oct  1 13:20:47 2010
  ExecutablePath: /usr/bin/ubiquity-dm
  InterpreterPath: /usr/bin/python2.6
  LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928)
  ProcCmdline: /usr/bin/python /usr/bin/ubiquity-dm vt7 :0 hostname /usr/bin/ubiquity --greeter --only
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  PythonArgs: ['/usr/bin/ubiquity-dm', 'vt7', ':0', 'hostname', '/usr/bin/ubiquity', '--greeter', '--only']
  SourcePackage: ubiquity
  Title: ubiquity-dm crashed with ValueError in command()
  UserGroups:

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