On 17.11.2010 14:09, Florian Kriener wrote:
> On Wednesday 17 November 2010 14:04:58 you wrote:
>> This bugs also affects pm-utils (from experimental), because somehow
>> pm- powersave is called from
>> hal-system-power-set-power-save(-linux). The script
>> hal-system-power-set-power-save reads "true" or "false" from
>> standard input into $value. However, it always reads "false" on my
>> system (KDE4). This breaks pm-powersave, since now "pm-powersave
>> false" is called when on battery and on ac power.
>
> However, hal reports the status correctly:
>
> $ lshal | grep adapter
> udi = '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_AC'
> ac_adapter.present = false (bool)
> info.capabilities = {'ac_adapter'} (string list)
> info.category = 'ac_adapter' (string)
> info.udi =
> '/org/freedesktop/Hal/devices/computer_power_supply_ac_adapter_AC' (string)
>
> Is this still the same bug, or should I file a new?Not sure. could you add some debug information to hal-system-power-set-power-save(-linux) to see if hal calls pm-powersave correctly? pm-powersave (both unstable and experimental) uses on_ac_power from powermgmt-base to get the ac status, so please check what this tool reports: on_ac_power # on_ac_power && echo yes || echo no Yet keep in mind, that on_ac_power is only called when pm-powersave is called without an argument. Right now it looks more like the bug is outside of pm-utils and pm-powersave is not called with the right argument. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
