[Bug 657397] Re: Install alongside option displays incorrect device designations
Erick Brunzell
lbsolost at yahoo.com
Fri Sep 23 16:15:50 UTC 2011
@ Dave Walker,
I think we'd be foolish to rip into ubiquity this late in Oneiric for
such a relatively minor bug. Note what I said in post #2:
#1: If someone is really paying attention they can either choose the
advanced option or quit the install.
#2: If they're not paying attention the install seems to do the right
thing anyway so they'll never know.
I'd much prefer this be looked at again in P ;^)
IMHO the most serious bug in ubiquity is bug 766265, and even with that,
I'd hate to see ubiquity torn into this late in the process.
I've tested extensively, beyond the prescribed iso-testing criteria,
with Oneiric Beta 2 and I've found no conditions under which we'd cause
a loss of data as we did with bug 655950. I think we must never risk
such a thing again, unless it's very early in the Alpha stage of
development when only experienced testers should be installing
recklessly.
Many thanks, Lance.
--
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/657397
Title:
Install alongside option displays incorrect device designations
Status in “ubiquity” package in Ubuntu:
Triaged
Status in “ubiquity” source package in Natty:
Won't Fix
Status in “ubiquity” source package in Oneiric:
Triaged
Bug description:
Binary package hint: ubiquity
While iso-testing the Maverick final I noticed that after choosing the
auto-resize option the gui that allows you to "resize" using the
"slider" displays incorrect device info.
First of all here's what I started with:
lance at lance-desktop:~$ sudo parted /dev/sdb print
[sudo] password for lance:
Model: ATA WDC WD800JB-00JJ (scsi)
Disk /dev/sdb: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 11.5GB 11.5GB primary ext4 boot
2 11.5GB 23.0GB 11.5GB primary ext4
3 23.0GB 56.1GB 33.1GB primary ext4
4 56.1GB 80.0GB 24.0GB extended
5 56.1GB 77.7GB 21.7GB logical ext4
6 77.7GB 80.0GB 2297MB logical linux-swap(v1)
That is three 10.10's, the one on sdb1 has a separate /home on sdb5,
the other two on sdb2 and sdb3 have no separate /home. They all share
the same swap.
During installation the gui showed that it was going to resize sdb3 to
16.8GB and create a ne16.3GB sdb4. Of course that would not be
possible since I have three primary partitions and an extended,
regardless this is what it really did:
ubuntu at ubuntu:~$ sudo parted /dev/sdb print
Model: ATA WDC WD800JB-00JJ (scsi)
Disk /dev/sdb: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 11.5GB 11.5GB primary ext4 boot
2 11.5GB 23.0GB 11.5GB primary ext4
3 23.0GB 39.8GB 16.8GB primary ext4
4 39.8GB 80.0GB 40.3GB extended
7 39.8GB 55.3GB 15.6GB logical ext4
8 55.3GB 56.1GB 730MB logical linux-swap(v1)
5 56.1GB 77.7GB 21.7GB logical ext4
6 77.7GB 80.0GB 2297MB logical linux-swap(v1)
As you can see it actually resized everything quite well. Darn
impressive I must say!
So it's simply a matter of the gui showing improper info and I'd
consider that very low priority.
At any rate I wanted apport to collect info for the devs, but I'll add
more comments later after I get into a more comfortable modified
Ubuntu that suits my vision ;^)
Overall I'm very impressed with the new ubiquity.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubiquity 2.4.8
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Oct 9 11:58:05 2010
LiveMediaBuild: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/657397/+subscriptions
More information about the foundations-bugs
mailing list