Don't know if bug #216483 is a duplicate.
I wrongly thought bug #235134 was a duplicate, where I have given the following solution.
I was having an almost identical error when plugging a usb key, and finally did found that dbus policy was saying both one thing and then the opposite, commenting out the opposite fixed it for me:
More precisely in /etc/dbus-1/system.d/hal.conf it says:
<!-- Allow anyone to invoke methods on the Manager and Device interfaces -->
<policy context="default">
...
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
and later:
<!-- 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>
that I edited to become:
<!-- 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>
So I just commented out the last two deny lines (note the -- at the end too! )
It is unclear to me if latest hal in hardy-updates have still this problem.
Intrepid version (older!?) does not have this problem, because it allows it always.
Don't know if bug #216483 is a duplicate.
I wrongly thought bug #235134 was a duplicate, where I have given the following solution.
I was having an almost identical error when plugging a usb key, and finally did found that dbus policy was saying both one thing and then the opposite, commenting out the opposite fixed it for me:
More precisely in /etc/dbus- 1/system. d/hal.conf it says: "org.freedeskto p.Hal.Device. Volume" />
<!-- Allow anyone to invoke methods on the Manager and Device interfaces -->
<policy context="default">
...
<allow send_interface=
and later: "org.freedeskto p.Hal.Device. SystemPowerMana gement" /> "org.freedeskto p.Hal.Device. VideoAdapterPM" /> "org.freedeskto p.Hal.Device. LaptopPanel" /> "org.freedeskto p.Hal.Device. Volume" /> "org.freedeskto p.Hal.Device. Volume. Crypto" /> "org.freedeskto p.Hal.Device. SystemPowerMana gement" /> "org.freedeskto p.Hal.Device. VideoAdapterPM" /> "org.freedeskto p.Hal.Device. LaptopPanel" /> "org.freedeskto p.Hal.Device. Volume" / --> "org.freedeskto p.Hal.Device. Volume. Crypto" / -->
<!-- Default policy for the exported interfaces -->
<policy context="default">
<deny send_interface=
<deny send_interface=
<deny send_interface=
<deny send_interface=
<deny send_interface=
</policy>
that I edited to become:
<!-- Default policy for the exported interfaces -->
<policy context="default">
<deny send_interface=
<deny send_interface=
<deny send_interface=
<!-- deny send_interface=
<!-- deny send_interface=
</policy>
So I just commented out the last two deny lines (note the -- at the end too! )
It is unclear to me if latest hal in hardy-updates have still this problem.
Intrepid version (older!?) does not have this problem, because it allows it always.