You are not logged in.
HAL automounting stopped working. I'm pretty sure I had it working before, though I'm pretty sure it stopped working on some HAL update and I had to add some lines somewhere to get it working again, and it seems it happened again.
This is my 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.*">
<return result="yes"/>
</match>
<match action="hal-storage-mount-fixed-extra-options">
<!-- for internal devices mounted with extra options like a wished mount point -->
<return result="yes" />
</match>
<match action="hal-storage-mount-removable-extra-options">
<!-- for external devices mounted with extra options like a wished mount point -->
<return result="yes" />
</match>
</config>
I have tried adding <match user="sokuban"></match> into the file in various positions, but none seemed to work.
If I open up Thunar (NB: I do not have Thunar Volman, Gnome Volman or any Volman installed) and click the "KINGSTON" icon on the left to try and mount it, I get this error message:
Failed to mount "KINGSTON".
Rejected send message, 1 matched rules; type="method_call", sender=":1.33" (uid=1000 pid=2974 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=2829 comm="/usr/sbin/hald)).
However, if I run Thunar in root and try to do the same thing there are no errors.
Last edited by sokuban (2009-11-22 20:46:54)
Offline
Have you tried starting your sessions with Consolekit? I haven't had to look at PolicyKit.conf for months now.
exec dbus-launch --exit-with-session ck-launch-session [session]
Offline
Thanks, that works.
Offline
Have you tried starting your sessions with Consolekit? I haven't had to look at PolicyKit.conf for months now.
exec dbus-launch --exit-with-session ck-launch-session [session]
Hi,
I'm using openbox and pcmanfm and I'm having the same problem with mounting my USB sticks (i.e. I can mount them from pcmanfm when running it as root but not as a normal user). Your suggested solution seems to work for sokuban and I would like to try it -- only I seem to be too stupid to understand your solution
So what do I need to do to "start my session with Consolekit" ??? Your solution appears to me as if I must run the "exec dbus-launch" line from within my openbox autostart.sh file. So I added the line, logged out of openbox and started it again, but nothing changed!?!
Should the line actually look exactly as you wrote it? Or is the "[session]" entry a place-holder for something (such as "openbox" or whatever)?
Thanks in advance for any help -- which will be greatly appreciated,
Dr.U
Offline
Meyithi wrote:Have you tried starting your sessions with Consolekit? I haven't had to look at PolicyKit.conf for months now.
exec dbus-launch --exit-with-session ck-launch-session [session]
Hi,
I'm using openbox and pcmanfm and I'm having the same problem with mounting my USB sticks (i.e. I can mount them from pcmanfm when running it as root but not as a normal user). Your suggested solution seems to work for sokuban and I would like to try it -- only I seem to be too stupid to understand your solutionSo what do I need to do to "start my session with Consolekit" ??? Your solution appears to me as if I must run the "exec dbus-launch" line from within my openbox autostart.sh file. So I added the line, logged out of openbox and started it again, but nothing changed!?!
Should the line actually look exactly as you wrote it? Or is the "[session]" entry a place-holder for something (such as "openbox" or whatever)?
Thanks in advance for any help -- which will be greatly appreciated,
Dr.U
I put that line in my .xinitrc and replaced [session] with my window manager.
Offline
Hi,
Thanks for the quick reply! I have now tried putting various forms of the entry, such as:
dbus-launch --sh-syntax --exit-with-session ck-launch-session openbox
or
dbus-launch --sh-syntax --exit-with-session ck-launch-session openbox-session
in my autostart.sh for openbox, but nothing changes
The exact form in my autostart.sh looks basically like it has always looked (except for the addition of the "ck-launch-session openbox" part, which was previously not present back in the days when I could mount my usb-stick by just clicking on it in pcmanfm...), namely
if which dbus-launch >/dev/null 2>&1 && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session ck-launch-session openbox`
fi
Any other tips that I could try out?
Thanks in advance,
-- Dr.U
Offline
Ive got same problem as described.
When trying to mount my cellphone (SonyEricsson w880i) i get:
Rejected send message, 1 matched rules; type="method_call", sender=":1.96" (uid=1000 pid=16894 comm="pcmanfm) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=2606 comm="/usr/sbin/hald))
And I have worked only some weeks ago.
I use fluxbox so I believe that it will have the same sollution as Dr.U will have to his problem.
Best regards
Hickin
Offline
This is my .xinitrc:
eval $(dbus-launch --sh-syntax --exit-with-session)
exec ck-launch-session startlxde
Replace startlxde with openbox-session or whatever it is you're using and see if things work now.
Offline
Worked, thanks a lot
Offline
Hi,
Thanks for the quick reply! I have now tried putting various forms of the entry, such as:
dbus-launch --sh-syntax --exit-with-session ck-launch-session openbox
or
dbus-launch --sh-syntax --exit-with-session ck-launch-session openbox-session
in my autostart.sh for openbox, but nothing changes
Don't put anything in your autostart.sh; I have no clue what that file is, but it is not what you want unless you start openbox from it. (Well, I just checked, and it seems to be a place where you can put programs you want to run after openbox starts. That is not what you want; you want to run openbox with the above command.)
Put it in your .xinitrc or your .xsession if you use a login manager. I'm not sure whether you use "openbox" or "openbox-session" to run openbox, but it should already say something like "exec something" in your .xinitrc and you put whatever "something" was in the [session] placeholder in the command.
Offline
Hi,
Thank you very much, Gusar and sokuban -- Your tips solved my problem
I removed the entries from openbox's autostart.sh file and have the following in my .xinitrc file:
eval $(dbus-launch --sh-syntax --exit-with-session)
exec ck-launch-session openbox
Now I can plug-in my usb-stick and just click on it in pcmanfm to automatically mount it and open it.
Thanks again,
-- Dr.U
Offline