After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 491109 - Don't create file gparted-disable-automount.fdi
Don't create file gparted-disable-automount.fdi
Status: RESOLVED DUPLICATE of bug 324220
Product: gparted
Classification: Other
Component: application
0.3.4
Other All
: Normal normal
: ---
Assigned To: gparted maintainers alias
gparted maintainers alias
Depends on:
Blocks:
 
 
Reported: 2007-10-28 16:06 UTC by freggy1
Modified: 2008-04-09 19:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description freggy1 2007-10-28 16:06:51 UTC
Please describe the problem:
If you start gparted, a file gparted-disable-automount.fdi is created which disables hal automounting of removable disks. The problem is that if for some reason GParted is not closed correctly, this file is not removed, and so automounting is completely broken until the user starts and closes GParted again.

Steps to reproduce:
1. Start GParted
2. Hard reset your computer while GParted is running
3. Once your system has rebooted, connect a removable disk


Actual results:
The disk is not mounted anymore

Expected results:


Does this happen every time?


Other information:
Please don't disable hal automounting, rather add an option in GParted to eject removable devices, and propose this option if a certain operation requires the partitions to be unmounted.
Comment 1 Pacho Ramos 2007-12-11 19:45:14 UTC
Mandriva bug:
http://qa.mandriva.com/show_bug.cgi?id=34018

fcrozat gave also this interesting info that maybe could help:
They should lock mount interfaces using dbus, as explained in
http://people.freedesktop.org/~david/hal-spec/hal-spec.html#locking


Thanks a lot for fixing this
Comment 2 Laurent de Trogoff 2007-12-13 17:59:52 UTC
Well, I am not the dev of GParted, only LiveCD maintainer.
Any way I know why Plors did this : when creating a new partition, if hal is not disabled, the fresh created partition is auto-mounted by the system, and this makes gparted to crash...
Comment 3 Dick Gevers 2008-01-05 16:42:39 UTC
It crashes anyway, so that makes no difference:
See: http://bugzilla.gnome.org/show_bug.cgi?id=468598
Comment 4 Pacho Ramos 2008-01-05 21:31:20 UTC
Fedora currently launches gparted with:
/usr/bin/hal-lock --interface org.freedesktop.Hal.Device.Storage  --exclusive --run /usr/sbin/gparted

And patches it for not using gparted-disable-automount.fdi
Comment 5 Gour 2008-02-05 13:54:05 UTC
(In reply to comment #0)
> Please describe the problem:
> If you start gparted, a file gparted-disable-automount.fdi is created which
> disables hal automounting of removable disks. The problem is that if for some
> reason GParted is not closed correctly, this file is not removed, and so
> automounting is completely broken until the user starts and closes GParted
> again.

I second that - spent whole morning trying to debug why automount suddenly stopped working in Xfce with thunar.

Once I had issue with gparted scr**ing my ext3 partition on laptop and today wasted too many hours with this issue, so, gparted won't see my system again :-/


Sincerely,
Gour
Comment 6 Curtis Gedak 2008-04-09 19:38:52 UTC

*** This bug has been marked as a duplicate of 324220 ***