Bug 153103

Summary: KPowersave Information Dialog shows ambiguous info
Product: [openSUSE] SUSE Linux 10.1 Reporter: Forgotten User 55iwwMllzz <forgotten_55iwwMllzz>
Component: OtherAssignee: Danny Kukawka <dkukawka>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P5 - None    
Version: Beta 4   
Target Milestone: ---   
Hardware: i686   
OS: Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: KPowersave Information Dialog snapshot

Description Forgotten User 55iwwMllzz 2006-02-23 15:31:53 UTC 
The Information Dialog is a nice feature of KPowersave, but it shows some ambiguous information:

1. I don't know what the "Battery state" field is supposed to mean, but its value is always "ok"... Even when I remove the battery (as you can see on the attached screenshot)!

2. My processor doesn't support frequency scaling. So the label on the CPUs section of the dialog shows "deactivated" (see attached screenshot). This is not precise. Here is my suggestion:
   1) The processor supports frequency scaling. In this case, Kpowersave shows the current MHz (it already does this).
   2) The processor does not support frequency scaling. In this case, KPowersave could show the static MHz value as reported by /proc/cpuinfo and between parentheses "(no scaling)".
   3) The processor supports frequency scaling but it is deactivated.  KPowersave could show the static MHz value as reported by /proc/cpuinfo and between parentheses "(scaling deactivated)".
Comment 1 Forgotten User 55iwwMllzz 2006-02-23 15:32:40 UTC 
Created attachment 69989 [details]
KPowersave Information Dialog snapshot
Comment 2 Michael Gross 2006-02-23 15:46:24 UTC 
Joao, please report this upstream to the developers of kpowersave, not to us. However, if you encounter problems (bugs) or want to suggest minor changes that raises the usability of a program, feel free to report it here.
Comment 3 Forgotten User 55iwwMllzz 2006-02-23 15:53:19 UTC 
Since KPowersave developers are SuSE people, I thought I could report the bug here... But, no problem, I will report upstream.
Comment 4 Michael Gross 2006-02-23 16:00:46 UTC 
Sorry, I was wrong here. KPowersave is developed by us, I'll reassign it to the maintainer as enhancement.
Comment 5 Danny Al-Gaaf 2006-02-23 16:24:24 UTC 
Battery state has the following states which came from powersave: "NORMAL=ok,WARNING,LOW,CRITICAL"

All under 3 is already implemented for next beta.