Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#30283 - [upower]RunPowersaveCommand=false does'nt inhibit upower's call to pm-powersave after suspend

Attached to Project: Arch Linux
Opened by Federico (nierro) - Wednesday, 13 June 2012, 21:00 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 24 July 2012, 15:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:It seems that upower, even if i set RunPowersaveCommand=false in /etc/Upower/Upower.conf, will go on running pm-powersave after suspend/hibernation, while it won't run any pm-powersave command if i plug in or unplug ac adapter(that is what i expected). This is somehow related to this bug i opened: https://bugs.archlinux.org/task/29974 .

Additional info:
* package version(s): pm-utils 1.4.1-4, xfce4-power-manager 1.2.0-2 and upower 0.9.16-1
The log files are the same as the above bug linked.


Steps to reproduce:
Set RunPowersaveCommand to false. Kill acpid. Touch a blank file in /etc/pm/sleep.d/00powersave . Now we have inhibit every call to pm-powersave after suspend.
Now try to suspend through pm-suspend 5-6-7 times in a row, and i got my pm-powersave script set to false (it is set to false even if i'm on battery, that was my old bug report, probably because upower is locked in some parts during pm-suspend, and can't understand the state of the machine).
Tried with echo mem > /sys/power/state too, and it happened again.
Finally, killed upower, and tried again. Everything works.
What i want to gain: -> remove acpid and finally rely only on upower and pm-utils. But this call made by upower to pm-powersave false causes sometimes to lost my power management!
This task depends upon

Closed by  Gaetan Bisson (vesath)
Tuesday, 24 July 2012, 15:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Federico reports this is fixed with upower-0.9.17
Comment by Federico (nierro) - Thursday, 14 June 2012, 07:25 GMT
As far as i understand, my problem about power management were born because of upower, that:
#1 bug (i think): tries to set the powersave for the machine after suspend/hibernation, even if it is locked before, and can't understand the state of the machine.
#2: RunPowersaveCommand=false will stop upower from running powersave commands when plug in or out ac adapter, but won't stop that call to pm-powersave after suspend-hbernation.
The strangest and hardest thing to understand is why that call doesn't happen always, but only 15-20% of the times. (and in my latest debugging, described in the first post, when i killed upowerd, and everything works, my /var/log/pm-powersave neither was created (because nothing calls it).

Loading...