Ubiquity feisty herd 3 selection of hard drive not correct

[Peter Liedler]

Binary package hint: ubiquity-frontend-kde

When testing herd 3 feisty fawn in a vmware player the two disks that are set up are correctly displayed.
Wehn I leave the options to the default selection, so that the standard formatting would be performed on /dev/hda the next steps all display /dev/hdb

See attatched screenshots. Do you need any further information?

[Colin Watson (cjwatson)]

Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance.

[Colin Watson (cjwatson)]

ubiquity (1.3.26) feisty; urgency=low

  * Make acquire_lock properly atomic (LP: #90391).
  * New partitioner: Remove the disk bar placeholder in UIs; we'll probably
    have to do without the disk bar for Feisty at this point.
  * KDE frontend: Fix disk selection handling in automatic partitioner so
    that we stop always selecting the last disk no matter what (LP: #83010).
  * Reluctantly print error messages from main program to stdout rather than
    stderr, as gksudo swallows them otherwise.
  * Drop dependencies on gparted and qtparted. Instead, print a helpful
    error message if --old-partitioner is used but these programs are not
    installed.
  * Automatic update of included source packages: partconf 1.19build1.

 -- Colin Watson <email address hidden> Thu, 8 Mar 2007 12:32:38 +0000

[vsespb (vi1tsr)]

I had same issue with Ubuntu 10.04 @ year 2010.
I lost part some part of my data and a bit of health.
Are you sure it's fixed ?

Seems there are messages dated 2011 about same issue
http://www.kubuntuforums.net/showthread.php?54338-worst-linux-install-ever

[Colin Watson (cjwatson)]

There's no point following up to such an old bug about a new issue; it's almost certainly a very different root cause. Filing a new bug is easier and less likely to create confusion, so please file a new bug with complete logs.