Org.freedesktop.hal.power-management.reboot returns no

Hallo,
I'm a new Xfce4 user, and when I reboot as non-root, I get the message
org.freedesktop.hal.power-management.reboot returns no
When asking google, one solution would be to change in /usr/share/PolicyKit/policy/org.freedesktop.hal.power-management.policy
<action id="org.freedesktop.hal.power-management.reboot">
<description>Reboot the system</description>
<message>System policy prevents rebooting the system</message>
<defaults>
<allow_inactive>no</allow_inactive>
<allow_active>yes</allow_active>
</defaults>
</action>
to
<action id="org.freedesktop.hal.power-management.reboot">
<description>Reboot the system</description>
<message>System policy prevents rebooting the system</message>
<defaults>
<allow_any>yes</allow_any>
</defaults>
</action>
But this is only a workaround - what is the meening of "active" and "inactive" in this context, and how can I get "active" to be able to reboot?
Thx, Charly

In this case, "active" and "inactive" refer to the status of the current ConsoleKit session.
Do 'ck-list-sessions' command from a console to see the sessions, you should see a "Active = TRUE"
If however you see no output, then your Xfce session isn't registered with ConsoleKit. This usually happens to people that are using 'startx' to load X (using GDM/KDM should automatically register the ConsoleKit session). Try editing your .xinitrc and change it from 'exec startxfce4' to 'exec ck-launch-session startxfce4'

Similar Messages

Org.freedesktop.Hal.Device.PermissionDeniedByPolicy: hal-storage-mount

When I plugged in my USB stick I got this error. This is weird because I tested another usb stick (where backtrack 3 resides. to boot from), and it worked flawlessly.
An error occurred while accessing 'MY USB STICK', the system responded: org.freedesktop.Hal.Device.PermissionDeniedByPolicy: hal-storage-mount-removable-extra-options no ← (action, result)
What's the matter?

This has been covered here massively in the last few weeks:
http://wiki.archlinux.org/index.php/HAL … utomounter

Hal gnome-power-manager hibernate scripts

Hi All,
I'm having issues hibernating to disk using gnome-power-manager. My user is in the "power" group and I can suspend from a terminal using "sudo hibernate". However, when I attempt to hibernate with gnome-power-manager, i recive an error "Hal failed to hibernate - please see FAQ". When I run g-p-m with no-daemon, it gives an "unspecified error: failed to hibernate". I have the necessary hibernate scripts in /usr/share/hal/scripts (is this the default dir?) and the hal-system-power-hibernate looks as follows:
#!/bin/bash
POWERSAVED_SUSPEND2DISK="dbus-send --system --dest=com.novell.powersave \
--print-reply /com/novell/powersave \
com.novell.powersave.action.SuspendToDisk"
unsupported() {
echo org.freedesktop.Hal.Device.SystemPowerManagement.NotSupported >&2
echo No hibernate script found >&2
exit 1
if [ -x "/usr/sbin/hibernate" ] ; then
echo "wtf"
hibernate
RET=$?
else
unsupported
fi
#Refresh devices as a resume can do funny things
for type in button battery ac_adapter
do
devices=`hal-find-by-capability --capability $type`
for device in $devices
do
dbus-send --system --print-reply --dest=org.freedesktop.Hal \
$device org.freedesktop.Hal.Device.Rescan
done
done
exit $RET
Please let me know what I'm missing or what necessary config files need to be tweaked.

Does suspend to RAM work with gnome-power-manager? On my system I installed powersave from unstable, which is the daemon used by SuSE to do suspend to RAM and suspend to disk.

Gnome-Power-Manager don't save history and statistics

I notice that g-p-m doesn't save history and statistics during a session:
when I reboot the pc I loose every information and the graphs start by 0.
I checked every configuration on gconf-editor, but nothing helped me.
There is the section /apps/gnome-power-manager/info/ but there isn't a schema for any configuration, I don't know what test I could make.
And I don't find the folder ~/.gnome2/gnome-power-manager on my Arch installations.
I found this bug with Ubuntu:
https://bugs.launchpad.net/ubuntu/+sour … bug/302570
So I run lshal | grep battery to have information about my asus eeepc battery.
This is the result:
[root@e3pc luca]# lshal | grep battery
udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
battery.charge_level.current = 20871 (0x5187) (int)
battery.charge_level.design = 51034 (0xc75a) (int)
battery.charge_level.last_full = 50638 (0xc5ce) (int)
battery.charge_level.percentage = 41 (0x29) (int)
battery.charge_level.rate = 16993 (0x4261) (int)
battery.is_rechargeable = true (bool)
battery.model = '901' (string)
battery.present = true (bool)
battery.rechargeable.is_charging = true (bool)
battery.rechargeable.is_discharging = false (bool)
battery.remaining_time = 6306 (0x18a2) (int)
battery.reporting.current = 2691 (0xa83) (int)
battery.reporting.design = 6580 (0x19b4) (int)
battery.reporting.last_full = 6529 (0x1981) (int)
battery.reporting.rate = 2191 (0x88f) (int)
battery.reporting.technology = 'Li-ion' (string)
battery.reporting.unit = 'mAh' (string)
battery.serial = '' (string)
battery.technology = 'lithium-ion' (string)
battery.type = 'primary' (string)
battery.vendor = 'ASUS' (string)
battery.voltage.current = 7756 (0x1e4c) (int)
battery.voltage.design = 8400 (0x20d0) (int)
battery.voltage.unit = 'mV' (string)
info.capabilities = {'battery'} (string list)
info.category = 'battery' (string)
info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0' (string)
Eeepc hasn't the serial. Ok...
But on my hp 6735s there is the serial of the battery while I run "lshal | grep battery".
And it has the same problem.
The version of g-p-m is 2.26.2-1 on both of them.
I had many difficulties to find documentation about this gnome daemon!!
Somebody found a solution?
Thank you all!

up

Gnome-power-manager woes

Hi all. I've been having a few problems with gnome-power-manager on my Dell Vostro since upgrading to Gnome 2.26. I was just wondering if anyone else has been experiencing the same issues:
- When unplugging my laptop, I no longer get any notifications. Gconf is correctly configured.
- When plugging my laptop into the mains, I (usually) get a notification which says words to the effect of: you have unplugged your laptop and it is now discharging. The icon is is correct.
- Closing the lid won't suspend the laptop, unless the laptop has been suspended at least once since coming up using the suspend options from the g-p-m menu or the system->shutdown menu.
I've tried a new gconf setup (removing ~/.gconf* and ~/.gnome*).
Any ideas?

Here is my semi solution:
lid_open.sh
#!/bin/sh
if cat < /proc/acpi/button/lid/LID0/state | grep -q closed
then
sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool false
#lid has been opened
else
sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool true
#lid has been closed
fi
lid_closed.sh
#!/bin/sh
sleep 3
if cat < /proc/acpi/button/lid/LID0/state | grep -q open
then
sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool false
#lid has been opened
else
sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool true
#lid has been closed
fi
Does the job... but still
I would be very thankful if anyone would be able to post a better solution, or, at least, how to make this work automaticaly.
Last edited by Void_Walker (2009-06-29 23:27:36)

Power manager

Hello!
Lenovo model:B575e
Please help me.
How to fix this message battery not installed lenovo.

hi Matrix4478,
It looks like you have a Thinkpad Power Management utility..
If you're running Windows 7, can you try to:
1. Navigate to Control Panel (large icon view) > Programs and Features and uninstall the Thinkpad Power Manager (reboot if necessary).
2. After the reboot, install this Lenovo Power Management utility and observe:
Lenovo Power Management Driver
v1.67.04.05
Article:
IdeaPad - Power Manager reports NO BATTERY IS INSTALLED
Let me know how it goes.
Regards
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Power manager crashes after returning from standby mode.

I have a T400 2767 WU6 running Windows 7 Pro-64bit.. After returning from standby mode, power manager crashes (version 3). All the software installed is supposed to be compatible with win7 pro 64bit.
Any help would be greatly appreciated.

Does this issue appear from the beginning?
Possibly the OS was installed several time ago and now the registry entries are corrupt.
Therefore the system busy egg timer could appear.
Im not 100% sure it will help but possibly you should reinstall the whole OS
On the fresh installed OS all should works much faster

[solved] power management without HAL and pm-utils

hi guys! i got rid of hal and pm-utils, but i'm having some troubles now with the powersaving settings.
i'm using hibernate-script with uswsusp tools to hibernate etc, and laptop-mode-tools with acpi for the power management, but this looks like it isnt working anymore.
for example the screen backlight wont shut down anymore when i close the lid, despite the acpi action scripts are all ok.
far more importantly the cpu fan doen't ever start!! earlier this morning the cpu hit 77°C (while it's normally 40°) but the fan didn't kick in!
what can i do?
EDIT:
wait, maybe it's just the new kernel i've installed this morning! it's some days now that i've uninstalled hal and i think i would have noticed before!
Last edited by v43 (2011-02-23 11:25:10)

disabling laptop-mode-tools temporarily solved the problem. i mean the fan is now spinning free ^^
i'll try reinstalling it or downgrading the kernel later

Gnome Power Manager after Last Upgrade

Hi There,
I just did a pacman -Syu and upgraded lots of packages which also include dbus etc.. I just restarted and puzzled that GNOME Power Manager is a lot different now then it's used to be before the upgrade. First of all, it's systray logo is different. Then it's menu, it's options, everything about it are different. I can't see an upgrade in the pacman.log for gnome-power-manager but it's completely changed..
When I pull the AC power and work on the batteries, it doesn't change the status of the applet. So the applet is very useless right now.. Although it doesn't seem to be an applet while it can't be moved around or I can't change anything about it..
Before the upgrade, I was able to get information by simply right clicking on it selection Information.. But now, even that option is completely changed.. Is there something wrong ?

Hello.
Is the bug fixed already? I have some problems with gnome-power-manager, dbus and hal. After installing Gnome everything was just fine, after I reboot I cannot start HAL:
[root@ichi ~]# /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
[root@ichi ~]# lshal
error: dbus_bus_get: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-power-manager gives msgbox with error about connecting to DBUS.
What is the issue?

Power management messages in system logs

Can anyone tell me why these end up in my system logs? The system has been up for 26 days so this isn't from being rebooted. Thanks!!
Apr 11 04:31:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 04:31:03 myhostname Rev. 2 LSI, Inc. 1064 found.
Apr 11 04:31:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 04:31:03 myhostname mpt0 supports power management.
Apr 11 04:31:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 04:31:03 myhostname mpt0: IOC Operational.
Apr 11 08:31:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 08:31:03 myhostname Rev. 2 LSI, Inc. 1064 found.
Apr 11 08:31:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 08:31:03 myhostname mpt0 supports power management.
Apr 11 08:31:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 08:31:03 myhostname mpt0: IOC Operational.
Apr 11 16:01:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):
Apr 11 16:01:03 myhostname Rev. 2 LSI, Inc. 1064 found.
Apr 11 16:01:03 myhostname scsi: [ID 365881 kern.info] /pci@1e,600000/pci@0/pci@9
/pci@0/scsi@1 (mpt0):

Some information here:
http://bugs.opensolaris.org/view_bug.do;jsessionid=43bb4b26039fb5e8206511c13a2?bug_id=6551882
The LSI 1064 is the SCSI RAID controller chipset - perhaps a cabling/power issue as noted in another post I saw. Look at the above bug report and try checking your power management configuration.

SOLVE strange problem with suspend and resume with gnome-power-manager

I have pm-utils and gnome installed.
Suspending and hibernation works well from the command line ($ pm-hibernate and $ pm-suspend). Resuming works without any problems.
Suspending from gnome "Shutdown dialog" works perfectly as well.
However, if suspending is initiated by gnome-power-manager something strange happens: After pressing the power button resuming switches to hibernation and my laptop turns off. Resuming from disk works fine again.
Now, suspending works fine again if I change and save any config file in /etc/pm/.
Here comes the strange thing: It doesn't really matter what I change as long as I save it.
However, as soon as I reboot resuming fails again the way I described above.
Anyone have a clue what's going on?
I get no error messages and I've tried all sorts of boot entries.
Last edited by mehldutt (2007-12-26 19:42:31)

After some try and error my guess is that "HAL" is responsible for this problem:
I deinstalled ACPID and 'pm-utils' and switched to 'uswsusp'.
I made the appropriate changes to the appropriate hal-scrips
usr/lib/hal/scripts/hal-system-power-suspend:
#!/bin/sh
/sbin/s2ram --force
usr/lib/hal/scripts/hal-system-power-hibernate:
#!/bin/sh
/sbin/s2disk
After these changes I still have the same problem: immidiatly after resuming form suspend (via power-button) my laptop hibernates (s2disk).
However, if I delete all entries in "usr/lib/hal/scripts/hal-system-power-hibernate" resuming from suspend works fine again, but hibernate doesn't of course. So, some script must be calling "usr/lib/hal/scripts/hal-system-power-hibernate" emmediatly after resuming from suspend.
A couple of weeks ago everything worked fine. My guess is that one of the recent hal-updates is causing this.
How can I figure what script is calling "usr/lib/hal/scripts/hal-system-power-hibernate" after resuming from suspend?

Gnome-power-manager and screen brightness

gnome-power-manager appears to be screwing with my ability to adjust the screen brightness. Now there are only two brightness settings that work - the ones defined in gnome-power-manager settings. Using the keyboard shortcuts "works" in that I can increase the brightness one level but then the change gets overridden. Decreasing the brightness sets it at the minimum level then I can get it back without entering gpm settings. This definitely work before the last update and I think for a while after.
Is there anyway I can get it to listen to manual adjustments?
Edit: I think this was due to the latest hal update.
> lshal | grep bright
laptop_panel.brightness_in_hardware = false (bool)
Edit 2:
Found http://ubuntuforums.org/archive/index.php/t-290994.html
Adding "video" to MOD_BLACKLIST in /etc/rc.conf fixed this. This is just a kernel module right? Nothing else will be screwed...?
Last edited by Allan (2007-10-31 11:30:37)

I have Sony Vaio VGN-FZ38M with Nvidia 8400M GT. I used package 'nvclock' (it is in repo) to control lcd brightness, here site with more info: NVClock. Some time ago I also configured Fn keys to work with it (on Ubuntu), but on Arch I didn't manged but I didn't try hard (in general i don't need, my laptop is stationary all the time). Solution I've found somwehere in Ubuntu forums.
edit: typo in address
edit2:
here's the solution from Ubuntu: http://newyork.ubuntuforums.org/showthr … ?t=1004568
Last edited by folletto (2009-06-14 20:58:56)

Myriad of issues (hibernation, microphone, power management, alsa)

Hello!
I've had arch up and running beautifully on my Thinkpad T61 for around six months; everything up until this point worked well - audio, video, networking, internal microphone, etc. I'm currently running SLIM + XFCE4 + Compiz WM. Very happy indeed!
On October 3rd I upgraded a number of packages; like a good archer I read over the list to make sure none were unneeded/would break anything. After the update I shut down. On October 4th, I ran an update again (I can't remember why) and updated some more packages; that finished. I then closed my laptop lid to suspend it; that's when all hell broke loose.
At first I noticed that it wasn't suspending; I can tell by the lights on its lid. I opened it up and saw that it was exactly where I left it. I tried to suspend through the XFCE logout menu and noticed it was missing hibernate and suspend. I thought; that's weird, let's reboot!
Upon reboot, an extremely loud "BEEP" began nonstop - I quickly switched TTYs, went into alsamixer, and tried muting everything. Eventually I found that if I completely lowered the volume on my microphone the beeping stopped. That was weird. I rebooted; but the alsa settings were lost (though they were kept for everything else) on the microphone and the beeping returned. I tried saving the alsa state (alsactl store) and saw that it was saving any changes I made to any channels other than the microphone. Annoying. So I just disabled the internal microphone in the BIOS, for now.
Back to my suspend issue: I knew that I had upgraded pm-utils; so I suspend from CLI to see if it would work. It did. I then thought, it must be an ACPI issue - low and behold, checking the acpi log in real-time showed that the laptop lid wasn't being noticed, nor were my hotkeys. I checked my handler.sh file, and yup - it had reverted to a non-T61 state. Very rude indeed. I then replaced it with the T61 handler.sh from the wiki, and suspend/hibernate worked again, hotkeys, lid closure, etc. However, when resuming from suspend, he loud beeping returns - even though I've disabled microphone in the BIOS.
However, my hibernate/suspend options were still missing from my XFCE log out menu - I did some research on this; I made sure that I was a member of the power users group. I also tried logging in to XFCE as root - same issue. I also noticed that my battery percentage/charging indicator has disappearance from the XFCE notification window; when I set the Power Management properties to "show when battery is detected" it remains hidden; if I set it to "always show" it just shows a power plug.
So I basically have three outstanding issues: My microphone is making a crazy beeping sound & alsa refuses to permanently mute it; suspend & hibernate are missing from XFCE menu (and the Power Management window has no affect - if I push the power button, it shuts down via acpid rather than prompting me as it should), and the battery indicator is missing.
Here is my latest pacman.log
Here is my messages.log
Here is my rc.conf
Any help would be much appreciated! Thanks!
Yochai

I've had similar issues as well with the recent updates. Two things have helped but not completely eliminated all my issues. It should be noted that I'm on a T410 so this may or may not work for you. My kids X61 has had no issue whatsoever.
1) Removed hwclock from DAMONS in rc.conf - this fixed a gnome 3.2 issue.
2) Turned off wireless (hardware switch) before suspend - suspend now works - I don't really feel this is a fix but more on the lines of a workaround until a real solution is found.
You may also want to look at some of the recent suspend threads people are finding different things on different models for the suspend issues at least.

D20 sata disk support advanced power management

My d20 comes with a sata 250 GB WD (WD2500AAJS). I have centos 6 on it now. hiberate seems not working on this box: 1. after hibernate it automatically power up but boot into a black screen with backlight on.
2. pm-suspend.log shows that everything is successful during hibernate stage, except that /usr/lib64/pm-utils/sleep.d/99hd-apm-restore.hook hibernate hibernate: Advanced Power Management not supported by device sda. (the WD disk is the only disk plugged into the system for debugging purpose)
3. hdparm -i /dev/sda returns AdvancedPM = no
My first step is to work on the hiberate/restore problem (leaving auto reboot later). So the problem and log/hdparm messages are consistent that the sata disk does not support apm. how to turn on the apm support? is there any specific option to specify in the BIOS? is there any bit to flip on the hard disk? ... (right now BIOS enables AHCI mode and in native IDE mode, disk connects through Marvell controller)
Thank you very much.
Solved!
Go to Solution.

Hi, psuturtle:
Thank you for quick reply. This is the least I want to hear. It seems much on my own.
Googled around found a couple of related topic:
1. http://wdc.custhelp.com/app/answers/detail/a_id/958/~/how-to-enable-and-disable-pm2-%28power-managem...
Basically, WD sata disk is by default disabled with its APM. It instructs to "place a jumper shut on pins 3 and 4", though I haven't tested it. I don't know how windows circumvent this hd option problem though. On the other hand, if the disk is connected to one of the 3 IDE connectors (for optical drives), suspend/hiberate works fine although having slow I/O after resume (I did this with Fedora 14/15 but haven't tried on centos). So I guess it is Marvell Constroller drive might have some unexpected effort here.
Well, thank you anyway.

[Solved] power management during kde startup not loading

Hi,
after solving one problem here comes another. From on side it's onying, but on the other side I lesrn a lot about my system.
Well this time after the last kde update, I get the following message:
KDE Power Management System could not be initialized. The backend reported the following error:
No valid Power Management backend plugins are available. A new installation might solve this problem.
Please check your system configuration.
So I went to:System Settings>>Power Management and the pane on the right is greyed out and there is a message:
Power Management configuration module could not be loaded. The Power Management Service appears not to be running.
This can be solved by starting or scheduling it inside "Startup and Shutdown"
System Settings>>Startup and Shutdown>>Service Manager, shows that Power management is running.
If I try to start upower manually I get the following message:
/usr/lib/upower/upowerd
(upowerd:30849): UPower-WARNING **: Failed to acquire org.freedesktop.UPower: Connection ":1.77"
is not allowed to own the service "org.freedesktop.UPower" due to security policies in the configuration file
(upowerd:30849): UPower-WARNING **: Could not acquire name; bailing out
I found this post: http://forums.opensuse.org/showthread.p … KDE-4-11-1
where it states tha this was a bug in some previous kde releases.
Well apparently it happened again here.
I read somewhere that it could be because the policykit rules weren't update. I tried to understand policykit conf files but for no avail. I'm twice lefthanded on that matter.
Any takers?
PS.: Checking with journalctl -r I found that upowerd was masked, so I did;
#systemctl unmask upower.service
than I enabled it;
#systemctl enable upower.service
and if you want to start it right away than;
#systemctl start upower.service
Well that's it.
Last edited by camarao (2014-03-12 14:48:20)

Thanks for your answers!
arojas wrote:is the upower daemon running?
Not sure about that. I installed upower but I don't know how to configure it or if any configuration is needed. If I understand official documentation correctly, upower daemon should be started automatically if some application needs it.
cfr wrote:Are you sure that you installed everything necessary for that to work? Which parts of KDE did you install, for example?
I have full KDE installation (# pacman -S kde-meta) so problem should be in my Arch installation, no in KDE itself. I have only installed Arch, Xorg, proprietary Nvidia drivers and KDE so far, so there is only small chance I break or messed up something - it's more likely something I didn't install yet or didn't know how to configure.
Last edited by HungryMonster (2012-07-17 07:52:40)

Org.freedesktop.hal.power-management.reboot returns no

Similar Messages

Maybe you are looking for