Hal automount cdrom/dvd not working.

shazeal · 2008-12-01 07:10:42

Im a bit of a nub with HAL, I normally just install it and it works, and I rarely use dvd/cds for anything other than burning off some files.

Anyway, I put in a DVD and thunar spits out

Failed to mount DVD, org.freedesktop.hal.storage.mount-removable no <-- (action, result).

I thought maybe it was just thunar as I am using the git version, so I installed pcmanfm, same deal, it just spits out some random errors.

So I do the obvious and check groups, yup Im in optical/storage and so is hal. There are no logged errors anywhere, so Im guessing its the PolicyKit?

Packages installed.

dbus 1.2.4-1
dbus-core 1.2.4-1
dbus-glib 0.76-1
dbus-python 0.83.0-2
hal 0.5.11-7
hal-info 0.20081022-1
policykit 0.9-7

Any ideas on what might be causing hal to deny mounting the removable media? Ive googled/wikied/seached and cant find anything related.

shazeal · 2008-12-01 07:14:30

Ok, false alarm.

 downgrading package hal (0.5.11-7 => 0.5.11-4)

Fixes it, hal from testing spazzing out by the looks.

shazeal · 2008-12-01 07:20:14

Diff of 0.5.11-4 vs 0.5.11-7

--- hal.conf    2008-12-01 20:17:39.000000000 +1300
+++ /etc/dbus-1/system.d/hal.conf       2008-12-01 05:51:24.000000000 +1300
@@ -37,27 +37,9 @@
           receive_sender="org.freedesktop.Hal"/>
   </policy>
 
-  <!-- Default policy for the exported interfaces -->
+  <!-- Default policy for the exported interfaces; if PolicyKit is not used
+       for access control you will need to modify this -->
   <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>
-
-  <!-- You can change this to a more suitable user, or make per-group -->
-  <policy user="0">
     <allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
     <allow send_interface="org.freedesktop.Hal.Device.VideoAdapterPM"/>
     <allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>

szym · 2008-12-01 18:36:20

Same here. Can't mount USB drives, SD cards, or even hard drives. Interestingly, CDs work fine.

byte · 2008-12-01 18:52:09

http://bugs.archlinux.org/task/12221

jamtat · 2008-12-09 22:14:43

I have this same problem. Applies to all insertable media I've tried, from USB flash drives to CD's/DVD's. I have hal 0.5.11-4, btw. This started to happen after a recent pacman -Syu. Prior to that auto-mounting was working just fine. Suggestions on how to fix it?

James

fwojciec · 2008-12-09 23:27:22

I posted this solution in the bug report mentioned above, but I'll post it again here... This solution work if you start x using xinitrc/startx:
This is exactly what I had to do in order for permissions to work correctly using hal/policykit:

1) Add this to /etc/pam.d/login

session optional pam_ck_connector.so

2) Prefix all session started from xinitrc with "ck-launch-session"; so my openbox .xinitrc looks like this, for example:

exec ck-launch-session openbox-session

3) Restart hal/log out fully and log back in (or just restart to be 100% sure)

Permissions should work fine without making any changes to PolicyKit.conf.

ST.x · 2008-12-23 16:12:18

fwojciec wrote:

I posted this solution in the bug report mentioned above, but I'll post it again here... This solution work if you start x using xinitrc/startx:
This is exactly what I had to do in order for permissions to work correctly using hal/policykit:
1) Add this to /etc/pam.d/login
session optional pam_ck_connector.so
2) Prefix all session started from xinitrc with "ck-launch-session"; so my openbox .xinitrc looks like this, for example:
exec ck-launch-session openbox-session
3) Restart hal/log out fully and log back in (or just restart to be 100% sure)
Permissions should work fine without making any changes to PolicyKit.conf.

Thanks that works. Im using hal 0.5.11-7 from testing.

grey · 2009-02-16 11:45:19

Thanks fwojciec!

It worked for me as well.

Army · 2009-02-16 11:47:16

Seems like this line in /etc/pam.d/login isn't even needed! But I think it's not bad to have it.

Rokixz · 2009-02-16 13:50:05

fwojciec you p0wn3d Everything's working now

newgargamel · 2009-03-17 11:02:35

but what about kdm users? how to apply it to kdm?
thanks in advance!

Slack · 2009-03-22 16:33:14

Thanks fwojciec, now all removable devices works fines

ras0ir · 2009-03-22 22:17:25

newgargamel wrote:

but what about kdm users? how to apply it to kdm?
thanks in advance!

KDM (and GDM) can automatically run ck-launch-session, you dont need to do anything extra.

Godofgrunts · 2009-10-01 08:27:45

Hate to revive an old thread, but I've tried this method and it's not working for me.

I'm using Slim and Openbox

Using
hal 0.5.13-2
dbus 1.2.16-1
pcmanfm 0.5.1-2

Mustard · 2010-03-14 06:39:46

fwojciec wrote:

I posted this solution in the bug report mentioned above, but I'll post it again here... This solution work if you start x using xinitrc/startx:
This is exactly what I had to do in order for permissions to work correctly using hal/policykit:
1) Add this to /etc/pam.d/login
session optional pam_ck_connector.so
2) Prefix all session started from xinitrc with "ck-launch-session"; so my openbox .xinitrc looks like this, for example:
exec ck-launch-session openbox-session
3) Restart hal/log out fully and log back in (or just restart to be 100% sure)
Permissions should work fine without making any changes to PolicyKit.conf.

The above worked for me. Many thanks!!

SaVVa · 2010-03-18 22:31:58

session optional pam_ck_connector.so

worked for me fine! thanks a lot
ps
compiz-standalone + pcmanfm + cairo-dock

hseu · 2010-05-03 20:24:03

fwojciec wrote:

I posted this solution in the bug report mentioned above, but I'll post it again here... This solution work if you start x using xinitrc/startx:
This is exactly what I had to do in order for permissions to work correctly using hal/policykit:
1) Add this to /etc/pam.d/login
session optional pam_ck_connector.so
2) Prefix all session started from xinitrc with "ck-launch-session"; so my openbox .xinitrc looks like this, for example:
exec ck-launch-session openbox-session
3) Restart hal/log out fully and log back in (or just restart to be 100% sure)
Permissions should work fine without making any changes to PolicyKit.conf.

Perfect! Thank you very much !

Arch Linux

#1 2008-12-01 07:10:42

Hal automount cdrom/dvd not working.

#2 2008-12-01 07:14:30

Re: Hal automount cdrom/dvd not working.

#3 2008-12-01 07:20:14

Re: Hal automount cdrom/dvd not working.

#4 2008-12-01 18:36:20

Re: Hal automount cdrom/dvd not working.

#5 2008-12-01 18:52:09

Re: Hal automount cdrom/dvd not working.

#6 2008-12-09 22:14:43

Re: Hal automount cdrom/dvd not working.

#7 2008-12-09 23:27:22

Re: Hal automount cdrom/dvd not working.

#8 2008-12-23 16:12:18

Re: Hal automount cdrom/dvd not working.

#9 2009-02-16 11:45:19

Re: Hal automount cdrom/dvd not working.

#10 2009-02-16 11:47:16

Re: Hal automount cdrom/dvd not working.

#11 2009-02-16 13:50:05

Re: Hal automount cdrom/dvd not working.

#12 2009-03-17 11:02:35

Re: Hal automount cdrom/dvd not working.

#13 2009-03-22 16:33:14

Re: Hal automount cdrom/dvd not working.

#14 2009-03-22 22:17:25

Re: Hal automount cdrom/dvd not working.

#15 2009-10-01 08:27:45

Re: Hal automount cdrom/dvd not working.

#16 2010-03-14 06:39:46

Re: Hal automount cdrom/dvd not working.

#17 2010-03-18 22:31:58

Re: Hal automount cdrom/dvd not working.

#18 2010-05-03 20:24:03

Re: Hal automount cdrom/dvd not working.

Board footer