The crash reported in the previous comment is also bug 45200, and has
been fixed in Ubuntu 6.06.1.
The problem here is basically that, in order to ensure consistency of
how we create filesystems, we get partman to do the job; but that can
only be done after going forward from the mountpoints screen, which
means that if you go back to gparted before that then you'll see
filesystems labelled as unknown.
I was going to fix this by rewriting the partitioner from scratch and
having it *entirely* based on partman rather than just half-way, but
unfortunately that didn't make the Edgy feature freeze. My current plan
is to figure out a way to feed the uncommitted state back into gparted
when starting it up.
** Changed in: ubiquity (Ubuntu)
Status: Unconfirmed => Confirmed
** Summary changed:
- [Dapper beta 1] cannot properly delete and create ext3 partition
+ partitioning state not remembered between gparted and mountpoints screens
** Changed in: ubiquity (Ubuntu)
Importance: Medium => High
--
partitioning state not remembered between gparted and mountpoints screens
https://launchpad.net/bugs/40404
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
