FS#7042 - Hal-system-power-suspend refuses to work

Attached to Project: Arch Linux
Opened by Dawid Wróbel (cromo) - Tuesday, 01 May 2007, 10:14 GMT
Last edited by Jan de Groot (JGC) - Monday, 18 June 2007, 10:07 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 0.8 Voodoo
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I am not sure if this is related to hal exactly, but 'sudo /usr/lib/hal/scripts/hal-system-power-suspend' says:
"org.freedesktop.Hal.Device.UnknownError
No back-end for your operating system"

Looking at the script it seems it makes usage of uname. I saw some feedback on the forums that 'uname -a' when running 2.6.21 causes kernel hang up, so I though this might be similar problem. (although uname -a works fine here)

kernel26 2.6.21.1-5, Hal 0.5.9-1.
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 18 June 2007, 10:07 GMT
Reason for closing:  Fixed
Additional comments about closing:  pm-utils is in the repos now, next version of hal will depend on it as soon as pm-utils goes to extra.
Comment by Jan de Groot (JGC) - Tuesday, 01 May 2007, 10:50 GMT
You need either powersave or pm-utils to make this working. Also, these scripts are not meant to be called from the commandline, they're not in /usr/lib/hal for nothing.
Comment by Dawid Wróbel (cromo) - Tuesday, 01 May 2007, 11:07 GMT
The whole problem comes from kpowersave 0.7.2 (that doesn't depend on powersave daemon anymore and does all the stuff with HAL). It stopped performing system suspending with recent kernel & hal updates, even though suspending does work with "echo mem >> /sys/power/state". I do realize that these scripts should not be called from commandline but AFIK these are the scripts that are run by hal after kpowersave tells it to suspend. The hal-system-power-suspend should find out it's running under linux and call hal-system-power-suspend-linux scrupt, but it does not. OTOH running hal-system-power-suspend-linux explicitly works just fine (!) and does the suspending.

Regarding the powersaved daemon or pm-utils - AFIK this is not true. These can be used by HAL scripts but are not mandatory. If you have a look at hal-system-power-suspend-linux script you'll see that there is a fallback "echo mem >> ..." method used if none of the powersaved, hibernate-scripts or pm-utils are found in the system. And, as I said above, that hal-system-power-suspend-linux script does work correctly suspending using the "echo mem >> ..." method.
Comment by Dawid Wróbel (cromo) - Tuesday, 01 May 2007, 11:12 GMT
Also I think that we should bring pm-utils to archlinux. Back in the days I did my own pkgbuild for it, but for unknown reason hal was not making use of it. Don't really remember what exactly was it about, I didn't investigate too much. pm-utils will soon be released as stable (if it has not been already); this could be a good reason for putting it to archlinux :)
Comment by Dawid Wróbel (cromo) - Tuesday, 01 May 2007, 12:10 GMT
Also I think that we should bring pm-utils to archlinux. Back in the days I did my own pkgbuild for it, but for unknown reason hal was not making use of it. Don't really remember what exactly was it about, I didn't investigate too much. pm-utils will soon be released as stable (if it has not been already); this could be a good reason for putting it to archlinux :)
Comment by Dawid Wróbel (cromo) - Monday, 18 June 2007, 09:28 GMT
OK, I got it fixed. The problem was actually about the user not being in a 'power' group, and this is needed by dbus to fulfill the default policy. Please, add an postinstall information to pm-utils about it.

Loading...