When I attempt to mount or unmount a USB drive is thwarted with following
error message:

"Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
Removable Media' and currently mounted at /mnt/memory could not be
unmounted.
Unmounting failed due to the following error:
A security policy in place prevents this sender from sending this message to
this recipient, see message bus configuration file (rejected message had
interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error
name "(unset)" destination "org.freedesktop.Hal")"

I have looked around for a config file but No Joy.

Red Rocket wrote:

> When I attempt to mount or unmount a USB drive is thwarted with following
> error message:
>
> "Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
> Removable Media' and currently mounted at /mnt/memory could not be
> unmounted.
> Unmounting failed due to the following error:
> A security policy in place prevents this sender from sending this message
> to this recipient, see message bus configuration file (rejected message
> had interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error
> name "(unset)" destination "org.freedesktop.Hal")"
>
> I have looked around for a config file but No Joy.

I had something similar to this when I installed my dvd burner as a second
drive. The cd burner would work fine but the dvd was a no-go for launch
until I added it to the fstab.
Might wanna reboot the machine with the stick in it, and run dmsg | less to
see where it is being found and add that line to the fstab.

MikeinAK

MikeinAK wrote:

> Red Rocket wrote:
>> error message:
>> "Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
>> Removable Media' and currently mounted at /mnt/memory could not be
>> unmounted.
>> Unmounting failed due to the following error:
>> A security policy in place prevents this sender from sending this message
>> to this recipient, see message bus configuration file (rejected message
>> had interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error
>> name "(unset)" destination "org.freedesktop.Hal")"

>> I have looked around for a config file but No Joy.

> I had something similar to this when I installed my dvd burner as a second
> drive. The cd burner would work fine but the dvd was a no-go for launch
> until I added it to the fstab.
> Might wanna reboot the machine with the stick in it, and run dmsg | less
> to see where it is being found and add that line to the fstab.

Thanks for your reply but that isn't it.

A similar message comes up either when mounting or unmounting USB memory/hds
or cd/dvd discs.

The funny thing is that utility works for users, just not root.

Anybody have any idea about where I can change that behavior?

Thanks

blazar.jet@gmail.com wrote:
> MikeinAK wrote:
>
>> Red Rocket wrote:
>>> error message:
>>> "Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
>>> Removable Media' and currently mounted at /mnt/memory could not be
>>> unmounted.
>>> Unmounting failed due to the following error:
>>> A security policy in place prevents this sender from sending this message
>>> to this recipient, see message bus configuration file (rejected message
>>> had interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error
>>> name "(unset)" destination "org.freedesktop.Hal")"
>...
>
> Thanks for your reply but that isn't it.
>
> A similar message comes up either when mounting or unmounting USB memory/hds
> or cd/dvd discs.
>
> The funny thing is that utility works for users, just not root.

I think that message is from HAL and D-Bus, new at Slackware 12.0, if so I
don't think you have been running it for years...

When I got that "security policy prevents ..." message on trying a
removable device, that convinced me to get rid of HAL and D-Bus and go back
to the old way.

ljb wrote:

> blazar.jet@gmail.com wrote:
>> MikeinAK wrote:
>>
>>> Red Rocket wrote:
>>>> error message:
>>>> "Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
>>>> Removable Media' and currently mounted at /mnt/memory could not be
>>>> unmounted.
>>>> Unmounting failed due to the following error:
>>>> A security policy in place prevents this sender from sending this
>>>> message to this recipient, see message bus configuration file (rejected
>>>> message had interface "org.freedesktop.Hal.Device.Volume" member
>>>> "Unmount" error name "(unset)" destination "org.freedesktop.Hal")"
>>...
>>
>> Thanks for your reply but that isn't it.
>>
>> A similar message comes up either when mounting or unmounting USB
>> memory/hds or cd/dvd discs.
>>
>> The funny thing is that utility works for users, just not root.

> I think that message is from HAL and D-Bus, new at Slackware 12.0, if so I
> don't think you have been running it for years...

I never said I was.

> When I got that "security policy prevents ..." message on trying a
> removable device, that convinced me to get rid of HAL and D-Bus and go
> back to the old way.

Well, I would rather get it functioning than just ignore it.

So anybody else have any ideas?

On 2007-08-08, Red Rocket <blazar.jet@gmail.com> wrote:
> When I attempt to mount or unmount a USB drive is thwarted with following
> error message:
>
> "Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
> Removable Media' and currently mounted at /mnt/memory could not be
> unmounted.
> Unmounting failed due to the following error:
> A security policy in place prevents this sender from sending this message to
> this recipient, see message bus configuration file (rejected message had
> interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error
> name "(unset)" destination "org.freedesktop.Hal")"
>
> I have looked around for a config file but No Joy.


Add your user account to the plugdev group.
There is a thread on the LinuxQuestions.org Slackware forum
(started by me) that details some other 'gotchas' associated
with it. However, it seems to me that you should start with
the CHANGES_AND_HINTS.TXT file on your Slackware install
media.

To all:
This whole DBUS/HAL thing really isn't black magic, nor is it
being forced on you. First, if you prefer the "old" behavior
of adding devices to /etc/fstab with appropriate uid/gid/users
or whatever options, then by all means, continue - you don't
even have to disable HAL (and you'd already know that if you'd
read CHANGES_AND_HINTS.TXT). Second, be sure to add your user
account to the plugdev group. That means add it to the 'plugdev'
line in /etc/group. Yes, I know that shadow adds console users
to the plugdev group on login, but that's not enough (in fact,
it's completely useless, but that's detailed in the LQ thread
I mentioned earlier). While you're adding your user account to
various groups, go ahead and put it in cdrom and power.
Third, logout and back in, and restart the messagebus service.
Alternatively, it might be simpler to reboot, but that's your
call.

RW

On 2007-08-08, Red Rocket <blazar.jet@gmail.com> wrote:
>
> A similar message comes up either when mounting or unmounting USB memory/hds
> or cd/dvd discs.
>
> The funny thing is that utility works for users, just not root.


That's because root is not in the plugdev group.
As far as DBUS is concerned, root is just another user.
If that user isn't in the plugdev group, then permission
is denied.

RW

Robby Workman wrote:

> On 2007-08-08, Red Rocket <blazar.jet@gmail.com> wrote:
>>
>> A similar message comes up either when mounting or unmounting USB
>> memory/hds or cd/dvd discs.
>>
>> The funny thing is that utility works for users, just not root.
>
>
> That's because root is not in the plugdev group.
> As far as DBUS is concerned, root is just another user.
> If that user isn't in the plugdev group, then permission
> is denied.

?

Strange.

I will try that.

Thanks

Robby Workman wrote:

> On 2007-08-08, Red Rocket <blazar.jet@gmail.com> wrote:
>> When I attempt to mount or unmount a USB drive is thwarted with following
>> error message:
>>
>> "Unfortunately, the device system:/media/sdc1 (/dev/sdc1) named '1.0G
>> Removable Media' and currently mounted at /mnt/memory could not be
>> unmounted.
>> Unmounting failed due to the following error:
>> A security policy in place prevents this sender from sending this message
>> to this recipient, see message bus configuration file (rejected message
>> had interface "org.freedesktop.Hal.Device.Volume" member "Unmount" error
>> name "(unset)" destination "org.freedesktop.Hal")"
>>
>> I have looked around for a config file but No Joy.
>
>
> Add your user account to the plugdev group.
> There is a thread on the LinuxQuestions.org Slackware forum
> (started by me) that details some other 'gotchas' associated
> with it. However, it seems to me that you should start with
> the CHANGES_AND_HINTS.TXT file on your Slackware install
> media.
>
> To all:
> This whole DBUS/HAL thing really isn't black magic, nor is it
> being forced on you. First, if you prefer the "old" behavior
> of adding devices to /etc/fstab with appropriate uid/gid/users
> or whatever options, then by all means, continue - you don't
> even have to disable HAL (and you'd already know that if you'd
> read CHANGES_AND_HINTS.TXT). Second, be sure to add your user
> account to the plugdev group. That means add it to the 'plugdev'
> line in /etc/group. Yes, I know that shadow adds console users
> to the plugdev group on login, but that's not enough (in fact,
> it's completely useless, but that's detailed in the LQ thread
> I mentioned earlier). While you're adding your user account to
> various groups, go ahead and put it in cdrom and power.
> Third, logout and back in, and restart the messagebus service.
> Alternatively, it might be simpler to reboot, but that's your
> call.
>
> RW

Thanks for the extra explanation.

I did read through Hints and do, sort of, understand what Pat is saying.

I will read it again with your explanation in mind AND I will look for your
thread on the Slackware forum.

Red Rocket <blazar.jet@gmail.com> wrote:
>> That's because root is not in the plugdev group.

> Strange.
>
> I will try that.

Maybe this is now turning into a matter of philosophy, but I would not try
that. If you want to mount things as root I would prefer to do it the old
fashioned way from a command line with something like "mount /dev/sda1
/mnt/whatever".

DBUS and HAL are making life easier for normal users logged in to a
graphical environment. A nice and simple dialog lets a user mount and
umount devices without having to care about things like which device name
a usb stick was given by the system.

However, I see no use or need for this functionality in the root account.
I would not want to start kde or X as root. Kde and X should be started as
a normal user, if that user later needs root priveleges that should be
solved with su or sudo in a terminal window. The root account is far to
powerful for letting it fool around in a "point, click and
oops"-environment like kde.

regards Henrik
--
The address in the header is only to prevent spam. My real address is:
hc1(at)poolhem.se Examples of addresses which go to spammers:
root@localhost postmaster@localhost