Comment 2 for bug 86851

I can confirm this critical and very annoying bug.

It seems this problem started to be visible after gnome-mount was be integrated into Ubuntu (also can be caused because of hal/libhal changes, related to gnome-mount)

This problem also occurs with Edgy's gparted if you install backported hal+libhal+gnome-mount packages from Feisty.

It seems this bug would be fixed simply to upgrading to new gparted 0.3.x upstream version (look at bug #81185 ):

In GParted-0.3 release notes (2006-09-04, see http://sourceforge.net/project/shownotes.php?release_id=444805&group_id=115843 ) there is a note, that "automountdisabling should work ok now" :

We finally have full move support!! Although it should be considered a bit experimental, our tests worked out perfectly and we didn't see any errors so far.

Bugfixes:
* automountdisabling should work ok now
* fixed some errors with scanning for used sectors on ntfs filesystems

New Features:
* it is now possible to move the start of filesystems.
* much improved progressfeedback during move and copy
* you can now move and copy ntfs filesystems and still boot windows from them
* overall improved progressfeedback (more details you don't want to know about ;) )

Translations (new/updated):
ja, es, vi, gl, nl, de, sv, lt, lv, hu, fi, fr, mk

Changes:
* mostly internal, far more exact calculations of partitiongeometry
* dependencies raised for libparted (now 1.7.1) and gtkmm (now 2.8)
* some trivial HIG stuff..
* due to cleanups the resulting binary is about 15% smaller