selecting 'new partition table' confuses the partitioning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
partman-uboot (Ubuntu) |
Fix Released
|
Medium
|
Colin Watson | ||
Karmic |
Won't Fix
|
Low
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Colin Watson |
Bug Description
Binary package hint: ubiquity
If you do manual partitioning on dove and select 'new partition table', the uboot partition you try to create for booting gets confused about it's mountpoing. I told it to mount as /boot, but when it returned to the partitioning screen, it said it was going to be / instead. If I delete it and do it again, this time it says it's going to be /home (even though I selected /boot again)
If you delete the partitions manually instead of wiping the partition table, then it does not exhibit this behavior.
A possible workaround for this, is to delete it, and select ext2 as the partition type instead of uboot. This should still be able to boot fine, and does not seem to suffer the same problem as when you select uboot type.
ProblemType: Bug
Architecture: armel
Date: Wed Oct 28 13:23:19 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release armel+dove (20091027.2)
Package: ubiquity 2.0.6
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: ubiquity
Uname: Linux 2.6.31-208-dove armv7l
XsessionErrors:
(gnome-
(gnome-
(nautilus:2891): Eel-CRITICAL **: eel_preferences
(polkit-
tags: | added: iso-testing |
Changed in ubiquity (Ubuntu Lucid): | |
milestone: | none → lucid-alpha-3 |
Changed in ubiquity (Ubuntu Karmic): | |
milestone: | none → karmic-updates |
Changed in partman-uboot (Ubuntu Karmic): | |
status: | Triaged → Won't Fix |
Covered in ARM release notes already, and not a big deal anyway