(xubuntu 8.04rc) Failed to mount various units

[Mr.Seduction]

Binary package hint: gparted

During opening of "gparted":
Failed to mount "10G Volume".
org.freedesktop.hal.storage.mount-fixed auth_admin_keep_always <-- (action, result).

Failed to mount "394M Volume".
org.freedesktop.hal.storage.mount-fixed auth_admin_keep_always <-- (action, result).

And others.

During an creation of new partition gparted shows:
Failed to mount "/org/freedesktop/Hal/devices/volume_uuid_71e3c412_2c84_4a5d_a871_98c305cdf922".

Please refer my other bug report https://bugs.launchpad.net/ubuntu/+bug/220945
It can are correlated.

ProblemType: Bug
Architecture: amd64
Date: Wed Apr 23 11:59:39 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gparted
NonfreeKernelModules: nvidia
Package: gparted 0.3.5-1ubuntu3 [modified: usr/bin/gparted]
PackageArchitecture: amd64
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: gparted
Uname: Linux 2.6.24-16-generic x86_64

[Charlie Kravetz (cjkgeek)]

I can confirm this behavior. When gparted is started, it appears to try to mount all available partitions, and gives an error message for every partition it fails to mount.

I would not expect gparted to attempt to mount any partitions that are not already mounted. If I started gparted, I probably want to do something to those unmounted partitions, and should not have to unmount them to work.

Thanks for reporting this bug. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

[Curtis Gedak (gedakc)]

My guess is that this problem is related to a spelling mistake in the lock name taken to prevent auto-mounting of partitions. If so then this bug was solved in GParted 0.4.3.

See GParted Bug:
http://bugzilla.gnome.org/show_bug.cgi?id=571347