Arch Linux

Any error messages?

no errors. after authorization nothing happens

I'm seeing the same behavior here going from hal 0.5.11-4 to 0.5.11-7.

Same issue here, going from hal 0.5.11-4 to 0.5.11-7.

I got the error. Although I'm authorized indefinitely, my request is refused.

[benutzer@zepto ~]$ polkit-auth --explicit-detail
org.freedesktop.hal.storage.mount-fixed
Authorized: Yes
Scope: Indefinitely
Obtained: Tue Feb 3 23:38:51 2009 from benutzer (uid 1000)

[benutzer@zepto ~]$ gnome-mount -v -t -d /dev/sda10
gnome-mount 0.8
** (gnome-mount:7833): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_f1c66eec_8a22_4bcb_8b5e_971cf7fe4889
** (gnome-mount:7833): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_f1c66eec_8a22_4bcb_8b5e_971cf7fe4889 with mount_point='', fstype='', num_options=0
** Message: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_f1c66eec_8a22_4bcb_8b5e_971cf7fe4889
org.freedesktop.Hal.Device.PermissionDeniedByPolicy : org.freedesktop.hal.storage.mount-fixed auth_admin_keep_always <-- (action, result)

But if I authorize every active session:

[benutzer@zepto ~]$ polkit-action --action org.freedesktop.hal.storage.mount-fixed
action_id: org.freedesktop.hal.storage.mount-fixed
description: Mount file systems from internal drives.
message: System policy prevents mounting internal media
default_any: no
default_inactive: no
default_active: yes (factory default: auth_admin_keep_always)

[benutzer@zepto ~]$ gnome-mount -v -t -d /dev/sda10
gnome-mount 0.8
** (gnome-mount:8006): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_f1c66eec_8a22_4bcb_8b5e_971cf7fe4889
** (gnome-mount:8006): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_f1c66eec_8a22_4bcb_8b5e_971cf7fe4889 with mount_point='', fstype='', num_options=0
Mounted /dev/sda10 at "/media/disk"

Same pbm here: hal mounting of ntfs drives does not work since update from 0.5.11-4 to 0.5.11-7

kde mounting fails with error message:
org.freedesktop.Hal.Device.PermissionDeniedByPolicy: hal-storage-mount-removable-extra-options no <-- (action,result)

I use extra options to use ntfs-3g instead ntfs for ntfs volumes mounting.
I tried editing PolicyKit.conf to authorize extra-options but it does not work.

I forgot to mention that my architecture is x86_64.

I have by 2 days the same kind of problem, with kde 4.3svn and dolphin. Hal version: 0.5.11-7

I can mount the ntfs partition only with root privileges.

Same problem here with gnome and hal 0.5.11-7

I had the same error:

org.freedesktop.Hal.Device.PermissionDeniedByPolicy: hal-storage-mount-removable-extra-options no <-- (action,result)

I solved adding these lines in /etc/PolicyKit/PolicyKit.conf :

<match user="$USER">
<match action="org.freedesktop.hal.storage.*">
<return result="yes"/>
</match>
<match action="hal-storage-mount-fixed-extra-options">
<return result="yes" />
</match>
<match action="hal-storage-mount-removable-extra-options">
<return result="yes" />
</match>
</match>

baghera solution solved the problem for me,
I forgot to put the action hal-storage-mount-removable-extra-options in PolicyKit.conf this morning.
thx!

it doesn't work for me :(

Same problem here after upgrade to 0.5.11-7. Running x86_64 and Gnome.

The suggested workaround did not help.

I suffer the same problem, but I cannot mount even USB HDDs formatted with NTFS.
I'm runnin i686 and KDE 4.2 (KDEmod), and the solution suggested by baghera didn't work for me.

The solution outlined in this post, solved the issue for me: http://bbs.archlinux.org/viewtopic.php?pid=495438#p495438

that's it. polkit-action doesn't output any hal-storage-mount-fixed-extra-options and hal-storage-mount-removable-extra-options

TheFiddler: that doesn't work for me, I get this:
"An error ocurred while accesing 'Volume (ntfs)', the system responded: org.freedesktop.Hal.Device.Volume.UnknownFilesystemType: Unknown file system 'ntfs-3g'"

@Stephen, Sergio & Marco: in the workaround given by baghera, did you replace $USER by your actual user name?

@Jean-Christophe: Yes, that is necessary.

@Sergio: Make sure the ntfs-3g package is installed from extra.

You're right, I thought ntfs-3g was installed :'(
Now it's working fine, thank you very much!

@Jean Crhistophe
yes, i did

I had the same problem. Going from hal 0.5.11-4 to 0.5.11-7.

I downgraded hal from 0.5.11-7 to 0.5.11-3. There are some instructions in BBS and Arch's Wiki to try to fix this, but the workaround didn't help with me too and I thought downgrade was easier than edit some files or change PolicyKit settings.

I think that a good thing was policykit/hal to keep the old settings from hal 0.5.11-4.

there is a bug in hal and the fix is already commited. we need to wait the next version of hal.

related bug: http://bugs.archlinux.org/task/13410
the patch "ntfs-mount-fix.patch" used to build hal package adds an undefined policykit action.

I thought it will be fixed in git but this isn't fixed in 0.5.12git20090406.46dc48-2 even the ntfs-mount-fix.path isn't applied

What's the status on this, assuming that the user is allowed to mount it by policykit (use consolekit's ck-launch-session or just plain gdm/kdm to gain those privileges)

using gdm to login into gnome,is asking for password but never mount it.

Is this with ntfs-3g installed? Installing ntfs-3g adds a hal fdi file that switches the filesystem type from ntfs to ntfs-3g.

yes,it's installed.

This bug is not NTFS specific it also applies to ext2/3/4 partitions. Look at my comment (the 5th one), there I pointed out what the problem is. You can mount if you allow everyone to mount fixed media in PolicyKit.

If you try to mount an internal (fixed) partition, HAL will return "auth_admin_keep_always". GNOME then tries to authenticate the user, you have to enter root's password and you get authenticated in PolicyKit! But HAL just ignores this explicit authentication and still says you have to authenticate.

See also http://hal.freedesktop.org/docs/PolicyKit/model-theory-of-operation.html

I think it is a bug in HAL, as for other applications PolicyKit works fine. I would be very glad, if this bug could get fixed. I did some research but could not find what is causing this strange behaviour.