FS#29719 - [upower] Backup upower.conf

Attached to Project: Arch Linux
Opened by Leonid Isaev (lisaev) - Wednesday, 02 May 2012, 23:17 GMT
Last edited by Jan de Groot (JGC) - Monday, 14 October 2013, 07:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Currently upower calls pm-powersave on startup/power state change. AFAIU this behavior is controlled by the recently-added [1] option "RunPowersaveCommand" in /etc/Upower/Upower.conf which defaults to true. The call executes "pm-powersave false" from pm-utils thus disabling powersavings on various subsystems according to scripts in /usr/lib/pm-utils/power.d. As discussed in [2] some of those are broken and this behavior is not always wanted and definitely undocumented (I just spent two days blaming kmod for not applying power settings in modprobe.conf).

A workaround is to block the above scripts by putting dummies in /etc/pm/power.d, but the real problem is upower _silently_ doing its magic. So, is it possible to either (a) change the default RunPowersaveCommand to false, and/or (b) add Upower.conf to "backup" array in PKGBUILD so that users' settings are not forgotten on update?

Thank you.

[1] http://cgit.freedesktop.org/upower/commit/?id=19790b99a2b8b0f1a784bfc8b10e7677020efdb8
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625606
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 14 October 2013, 07:07 GMT
Reason for closing:  Fixed
Comment by Matthias Dienstbier (fs4000) - Friday, 06 July 2012, 12:44 GMT
This has not been fixed in upower 0.9.17-1 which is in testing ATM.
Comment by Doug Newgard (Scimmia) - Sunday, 29 September 2013, 22:53 GMT
upower in testing doesn't use pmutils anymore, but it's still a valid concern that a conf file in /etc isn't in the backup array.

Loading...