You are not logged in.
I'm not sure when this started happening, but HAL seems to be not behaving properly on my laptop, and I don't exactly know why. My USB mouse works just fine, but if I plug in a USB drive and try to mount it (If this is relevant at all, I am using XFCE), I get this:
Rejected send message, 1 matched rules; type="method_call", sender=":1.39" (uid=1000 pid=11437 comm="exo-mount) interface="org.freedesktop.Hal.Device.Volume" member="Mount" error name="(unset)" requested_reply=0 destination="org.freedesktop.Hal" (uid=0 pid=3194 comm="/usr/sbin/hald)).
I have seen that someplace recommends editing /etc/dbus-1/system.d/hal.conf but I'm not exactly sure where to proceed here. I see these sections in the file:
<policy context="default">
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.DBus.Introspectable"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.DBus.Properties" />
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Manager"/>
</policy>
<policy at_console="true">
[Snipped... you don't need to see all of this -Leftylink]
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.Volume"/>
[Snipped]
</policy>
So I don't know if the problem is somewhere in here, or somewhere else.
Also, the power manager in XFCE has had most of its options disabled (When laptop lid is closed, do this, or when power button is pressed, do this).
If I try to hibernate using the XFCE exit menu, I get this response:
Suspend and Hibernate are only supported through HAL, which is unavailable
But, if I use sudo pm-suspend to do it, it works perfectly.
I'm not sure exactly what happened and I haven't made any configuration changes to HAL or anything, so some pointers would be greatly appreciated here.
Last edited by leftylink (2009-11-23 01:44:35)
Offline
Are you "at console"? If you are, there should be an entry for your user in /var/run/console.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
Ok, how do you start XFCE
with gdm or kdm you shouldnt have any policykit errors
with startx, make sure you have :
exec ck-launch-session startxfce
Offline
startxfce4 is how I start xfce.
And, er... /var/run/console doesn't exist at all.
Offline
startxfce4 is how I start xfce.
And, er... /var/run/console doesn't exist at all.
Then you need to add ck-launch-session, as the above poster suggested,
as in
exec ck-launch-session startxfce4
Offline
Perfect! Problem solved. Thanks for the help, all.
This isn't absolutely necessary, but would someone be so kind as to explain what happened? I haven't changed how I start up my computer or any of the configuration files, so I assume something changed with HAL and I missed the memo or something. What happened, and what is this exec ck-launch-session stuff?
Offline
The latest hal upgrade changed the way permissions are granted to use "at_console" rules. Have a look at /etc/dbus-1/system.d/hal.conf . at_console means that you are running a consolekit session. Some login managers (gdm, kdm) will start a session for you. If you aren't using them, you have to do it yourself by adding ck-launch-session to the start command of your desktop environment.
Good ideas do not need lots of lies told about them in order to gain public acceptance.
Offline
previously it was possible to hack out HAL+DBUS without consolekit, now it has become mandatory
.-. ,---,---.--.
| |__ \ \ \ \`//.
`----'`--'`--'`--'
Offline
previously it was possible to hack out HAL+DBUS without consolekit, now it has become mandatory
It's not mandatory, it's just the default configuration now. You can still write appropriate dbus rules that give permissions based on groups instead of relying on consolekit's "at_console".
Offline
Yes, the code bellow can solve the mount problem.
exec ck-launch-sessions startxfce4
but I want to know if there is any other solution while I am starting the desktop just with startxfce4 command from console.
and by the way, it seems the new exo still can't recognize CJK names in removable media(USB etc.). why are the pactches not accepted by the developer? the codes of patch sucks? I have no idea. I am not a programmer, so i don't understand the code. But I think the patch codes give implications for solve that problem. then why not solving it?
Hope the next release of exo could work with CJK on the fly. I really hate to install the patched exo form AUR each time the exo upgraded.:rolleyes:
Last edited by neoanima (2009-12-01 04:51:54)
Offline
Hi! I'm using slim and xfce4
I launch xfce with "exec ck-launch-sessions startxfce4"
but still can't suspend or hibernate...
Any ideas? Thanks
Offline
I managed to solve it (as well as automount) by adding this to /etc/dbus-1/system.d/hal.conf :
<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>
Offline
I am using XFCE/Slim as well and didn't get any love with the "ck-launch-session", but adding the policy that swiftscythe mentioned above did the trick for me. Additionally, it should be noted that your user account will need to belong to the groups "storage" and "power" for the policy to work as expected.
Swill
And you ate the whole... wheel of cheese? How'd you do that? Heck, I'm not even mad; that's amazing.
Offline