You are not logged in.
Im having this same error for a few days right now... i read the HAL wiki but the problem persist... tryed a lot of settings in /etc/PolicyKit/PolicyKit.conf with no luck yet...
org.freedesktop.hal.storage.mount-removable no <-- (action, result).
here's my /etc/PolicyKit/PolicyKit.conf file:
<?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 -->
<match action="org.freedesktop.hal.storage.*">
<return result="yes" />
</match>
<match action="org.freedesktop.hal.storage.mount-removable"
<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>
and my fstab...
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
UUID=71d30e9e-9848-46e4-82f9-761e9f64cc34 /sda4 ext3 defaults,noatime 0 1
UUID=be68fc53-e216-4681-8afb-f532a4af91cc swap swap defaults,noatime 0 0
UUID=eab9df0d-f99c-409c-ac0b-32e58142c979 /home ext3 defaults,noatime 0 1
UUID=fce3004a-2e1e-4341-9c16-efe3b2f5be02 / ext3 defaults,noatime 0 1
#UUID=aee55ed4-f539-4095-90e7-9e2b8b93d82f /sdc1 ext3 noauto,exec,rw,async,user,noatime 0 1
#UUID=3436-3133 /mnt/usb1 vfat noauto,exec,rw,async,user,noatime 0 1
#UUID=F4C2-19E5 /mnt/usb2 vfat noauto,exec,rw,async,user,noatime 0 1
Last edited by leo2501 (2009-02-28 04:10:49)
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
-- Antoine de Saint-Exupery
Offline
Well finally found the solution here http://foo-projects.org/pipermail/lunar … 08081.html maybe it's usefull for somebody else...
"org.freedesktop.hal.storage.mount-removable no <-- (action, result)"
There is easy fix for this error. Just define security rules
in /etc/PolicyKit/PolicyKit.conf like these:<config version="0.1">
<match action="org.freedesktop.hal.storage.mount-removable">
<match user="Put user account name here">
<return result="yes"/>
</match>
</match><match action="org.freedesktop.hal.storage.mount-fixed">
<match user="Put user account name here">
<return result="yes"/>
</match>
</match></config>
First rule allows automounting pendrives, the second one is for fixed disks
like hard drives.
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
-- Antoine de Saint-Exupery
Offline
On your original PolicyKit.conf file, you didn't have an open <config>. I'm guessing that's why it wasn't working.
Offline
lol... you're right, sure it was a copy/paste issue of me
Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
-- Antoine de Saint-Exupery
Offline
Hmm strange had the same problem but I have never edited Policykit.info.
Anyway your fix works! Thanks
Offline
Does not work for me. But this does:
Offline
Strangely, leo2501's way worked and the last one didn't though they are similar.
Arch64@MB166
Offline
Thanks that fixed my problem
Offline
Thanks leo, mounting works for me now XD
Offline
Sorry to reopen this after so long, but I had the same problem. Leo's solution stopped me from receiving the "org.freedesktop.hal.storage.mount-removable no <-- (action, result)" error, but now when I double-click the icon of my hard drive I get an error saying "Failed to open directory "OneTouch4 Mini". Permission denied." I tried editing permissions by opening my file manager as root, but allowing my user account read/write access gives me the error "Failed to change file group of "[FILENAME]". Operation not supported. Do you want to skip it?" for every single file.
Offline
See post #5 here (http://bbs.archlinux.org/viewtopic.php? … 38#p585338). That works for me.
Offline
See post #5 here (http://bbs.archlinux.org/viewtopic.php? … 38#p585338). That works for me.
Already tried that, my remaining problem is just one of permissions (I think), but when I try to modify permissions I get an "operation not supported" error. But I'm now juggling two threads, and I've posted more information here: http://bbs.archlinux.org/viewtopic.php? … 50#p585650, so if anyone has further advice please post it there to help keep this forum clean. Thanks!
Offline
thanks, this fixed my problem too
$ sudo nano /etc/PolicyKit/PolicyKit.conf
and wack in your above code.
I thought there was something wrong with hotplugging before!
Offline
None of the suggestions posted here worked the way they should. It's a bit of a compromise to hardcode your username into a global config file. I came across this message on the arch-general mailing list:
Don't modify any policykit or hal configurations, they are fine. All you need to do is register a session with consolekit. If you use KDM (KDE4 versions only) or GDM, this is done automatically.
If you start your session with startx over .xinitrc, you just have to replace:
exec startkde
with
exec ck-launch-session startkde
So in my case in my .xinitrc I put:
exec ck-launch-session startxfce4
Voila, things seem to work fine again!
Offline
Ok first to say... my USB drives all mounted without problems
the problem was when i added the eSATA drive
So i applied the PolicyKit code for the org.freedesktop.hal.storage.mount-fixed and now the eSATA drive mounts fine in /media
the problem is...
unlike my USB drives it DOESN'T appear as an icon on the desktop upon mount
why is that?
Last edited by _saiko (2009-10-08 11:23:34)
cat.7 - where crosstalk is not an issue anymore :'(
Offline
None of the suggestions posted here worked the way they should. It's a bit of a compromise to hardcode your username into a global config file. I came across this message on the arch-general mailing list:
Don't modify any policykit or hal configurations, they are fine. All you need to do is register a session with consolekit. If you use KDM (KDE4 versions only) or GDM, this is done automatically.
If you start your session with startx over .xinitrc, you just have to replace:
exec startkde
with
exec ck-launch-session startkdeSo in my case in my .xinitrc I put:
exec ck-launch-session startxfce4Voila, things seem to work fine again!
Thanks! Works perfect.
Offline
Malnilion wrote:None of the suggestions posted here worked the way they should. It's a bit of a compromise to hardcode your username into a global config file. I came across this message on the arch-general mailing list:
Don't modify any policykit or hal configurations, they are fine. All you need to do is register a session with consolekit. If you use KDM (KDE4 versions only) or GDM, this is done automatically.
If you start your session with startx over .xinitrc, you just have to replace:
exec startkde
with
exec ck-launch-session startkdeSo in my case in my .xinitrc I put:
exec ck-launch-session startxfce4Voila, things seem to work fine again!
Thanks! Works perfect.
This was my issue too.
Linux ArchLinux 3.2.8-1-ARCH
#1 SMP PREEMPT Mon Feb 27 21:51:46 CET 2012 x86_64 AMD FX(tm)-8120 Eight-Core Processor AuthenticAMD GNU/Linux
8192MB DDR3 1300MHz | Asus m5a97 | GeForce GTX 550 Ti | 120 GB SSD
Offline