You are not logged in.
Okay, so after a recent update, I couldn't telly you which one, because I do not mount and umount my USB drive all that often, I am not able to auto-mount drives. I looked around for about 2 and a half hours, and tried just about every HAL trick I could think of, so I thought I would bring it to you guys.
Information:
Using PcmanFm
fstab is not conflicting
I am added to the appropriate groups
I have tried every single fix on the HAL wiki
Symptoms:
I get two error boxes, one after the other, saying, "invalid mount option when attempting to mount fantom" fantom is my external. Then a third message say "error" "directory doesn't exist"
I'm stumped. There's an old ubuntu thread here: http://ubuntuforums.org/archive/index.p … 65843.html
that the guy had the same problem... only one that I found that's the same. My error boxes used to be blank until I did the ntfs-3g fix.
Any thoughts?!
Last edited by MattSmith (2009-05-14 07:07:19)
A thing of beauty is a joy forever
-John Keats
Offline
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">
<!-- See the manual page PolicyKit.conf(5) for file format -->
<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes"/>
</match>
<match action="org.freedesktop.hal.storage.mount-fixed">
<return result="yes"/>
</match>
</config>
Try this config file for /etc/PolicyKit/PolicyKit.conf. I've struggled a long time with hal too (staying with the old 0.5.11-4 hal package), but this has worked for every update after
Last edited by Themaister (2009-05-13 09:36:30)
Offline
the error is unchanged, thanks for tryin tho. I forgot to say that I can manually mount, I dunno if that helps narrow anything down though.
edit: I did restart hal and dbus as well
Last edited by MattSmith (2009-05-13 09:46:03)
A thing of beauty is a joy forever
-John Keats
Offline
any other thoughts guys?
A thing of beauty is a joy forever
-John Keats
Offline
doh, I had this exact same problem but can't remember how I fixed it -- something with the policykit I think, I'll poke around my system a bit and get back to you a little later.
\_\__ __/_/
(oo) ______
(__)\ )\
||‾‾‾‾\|
Offline
Okay, I'm pretty sure it was some combination of the following that fixed it for me. I think the /etc/hal/fdi/policy/preferences.fdi file was the final trick to solving it; found it somewhere on these formus.
Anyway, here are my relevant config files:
/etc/PolicyKit/PolicyKit.conf
<?xml version="1.0" encoding="UTF-8"?> <!-- -*- XML -*- -->
<!DOCTYPE pkconfig PUBLIC "-//freedesktop//DTD PolicyKit Configuration 1.0//EN"
"http://hal.freedesktop.org/releases/PolicyKit/1.0/config.dtd">
<!-- See the manual page PolicyKit.conf(5) for file format -->
<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.eject-removable">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.mount-fixed">
<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>
</config>
/etc/dbus-1/system.d/hal.conf
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
<!-- This configuration file specifies the required security policies
for the HAL to work. -->
<!-- Only root or user hal can own the HAL service -->
<policy user="hal">
<allow own="org.freedesktop.Hal"/>
</policy>
<policy user="root">
<allow own="org.freedesktop.Hal"/>
</policy>
<!-- Default policy for the exported interfaces -->
<policy context="default">
<deny send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<deny send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/>
<deny send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
<deny send_interface="org.freedesktop.Hal.Device.Volume"/>
<deny send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
</policy>
<policy group="power">
<allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
</policy>
<policy group="storage">
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
</policy>
</busconfig>
/etc/hal/fdi/policy/preferences.fdi
<merge key="volume.ignore" type="bool">false</merge>
\_\__ __/_/
(oo) ______
(__)\ )\
||‾‾‾‾\|
Offline
iza, YOU ROCK! dude (chick?) for four posts I dub you man (gal) of the century! I am so so so so so THANKFUL! Aw that was like getting rid of a thorn in my side. HOLY crap! perhaps this should be posted somewhere on the wiki?
The last piece to the puzzle was un doing this (as posted on the PCmanFm wiki page)
NTFS write support
You have to tell PCManFM explicitly how to manage the ntfs-3g driver. It is not difficult, you just have to edit the configuration file at /usr/share/pcmanfm/mount.rules like the following:
File: /usr/share/pcmanfm/mount.rules
[ntfs-3g]
# mount_options=locale=;exec
mount_options=uid=1000;gid=100;fmask=0113;dmask=0002;locale=;exec
Obviously, you can select the permission you want.
I think it was screwing with the permissions you set up in you hal.conf
Thank you so much!
A thing of beauty is a joy forever
-John Keats
Offline