7.04 Feisty Herd4: gparted: constantly mounting partitions

[jisaac]

"gparted" constantly try to mount all the partitions of my disks. This makes the partitioning process failing.

I tried to make some partition but when applying the modifications "gparted" mounts all the partitions so the modifications can not be applied.

Let me now if you need more informations.

Regards.

[James Henstridge (jamesh)]

Moving over to Ubuntu parted package.

Please report Ubuntu bugs at https://bugs.launchpad.net/ubuntu/+filebug

[Mantas Kriaučiūnas (mantas)]

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

[Mantas Kriaučiūnas (mantas)]

It seems this is a dup of bug #37768

Btw, you should patch upstream solution of this bug, because it's sort of "dirty hack" (look at http://bugzilla.gnome.org/show_bug.cgi?id=324220#c38 for more info):

 Comment #36 from A. Murat Eren (points: 0)
2007-02-19 11:30 UTC [reply]

I'd like to add some extra information. [When Gparted starts it creates]
/usr/share/hal/fdi/policy/gparted-disable-automount.fdi file, [which] causes some problems as you suspected before. Sometimes it remains there even GParted is not running anymore. Because of this file, HAL doesn't automount USB devices properly.

There are similar bug reports in both Fedora's and Pardus's bug tracking systems (I know there is a FIXME in the code, I just wanted to imply that it really needs to be fixed ;)).

[Daniel Hollocher (chogydan)]

#37768 describes this bug for removable usb drives. But this is happening to main drives too.

I was trying to change the size of my main ubuntu partition, and the drive was mounted in the middle of the gparted operation. The file system was left damaged, but it was fixed on restart.

The ISO that I used is only a few days old.

[Alexander Savelyev (ann-notation)]

I second this - I tried to re-partition my *internal* HD using GParted (resize an old partition, create a new one) and I ended up with an error message about the just-created partition being in use. Everything was ok after the restart.

More than that, I can't unmount more than one partition using GParted - it's Ok to unmount the first one, but as soon as I unmount another it does a rescan of my drives and the first partition get mounted again! One may still unmount them using the shell, but this behavior is rather annoying.

[Peter Adolphs (futzilogik)]

External drive or not, this bug seems to be a duplicate of bug #37768. I started GParted from the Feisty live CD, tried to resize an NTFS partition on the built-in SCSI harddisk. This failed at resizing the actual file system (that is, after resizing the partition), obviously because the partition was automatically mounted after the partition has been resized. The problem did not occur with the following workaround:
https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/37768/comments/25