FS#16970 - [gnome-power-manager] doesn't save battery charge/discharge profiles

Attached to Project: Arch Linux
Opened by Carl Reinke (Mindless) - Monday, 02 November 2009, 00:44 GMT
Last edited by Jan de Groot (JGC) - Monday, 02 November 2009, 19:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
gnome-power-manager does not save battery charge/discharge statistics between sessions as it should

see also: http://bbs.archlinux.org/viewtopic.php?id=75081 (however, my battery does have a serial entry in lshal)


Additional info:
gnome-power-manager 2.28.1-1


Steps to reproduce:
start gnome-power-manager
discharge or charge battery, noting charge/discharge statistics via gnome-power-statistics
restart gnome-power-manager
note that statistics have not been preserved
   lshal.txt (1.7 KiB)
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 02 November 2009, 19:45 GMT
Reason for closing:  Upstream
Additional comments about closing:  Upstream regression.
Comment by Jan de Groot (JGC) - Monday, 02 November 2009, 07:50 GMT
I might be wrong on this, but AFAIK these statistics are generated at runtime and aren't stored in a persistent database.
Comment by Carl Reinke (Mindless) - Monday, 02 November 2009, 17:17 GMT
When I asked in #gnome on irc.gnome.org, I was told that the statistics should persist between sessions, and the Ubuntu bug report (link is in the thread mentioned above) indicates that there should be statistics data stored in .cvs files in ~/.gnome2/gnome-power-manager/ which doesn't exist at all on my system.
Comment by Jan de Groot (JGC) - Monday, 02 November 2009, 19:06 GMT
The .csv files were stored in 2.24.x. When gnome-power-manager switched to devicekit-power with 2.26, persistent storage of profiling data was no longer done.
Comment by Carl Reinke (Mindless) - Monday, 02 November 2009, 19:13 GMT
Hrm, seems like a loss of a useful feature. :(

But if that's the case, there's nothing to be done for this bug report.
Thanks for your help.

Loading...