After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 348234 - Label at y-axis are truncated
Label at y-axis are truncated
Status: RESOLVED FIXED
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-preferences
2.15.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
: 353636 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-07-21 11:13 UTC by Tobias Wolf
Modified: 2006-08-31 07:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot of truncated labels (50.99 KB, image/png)
2006-07-21 11:15 UTC, Tobias Wolf
  Details
hal fix (2.66 KB, patch)
2006-07-21 15:23 UTC, Richard Hughes
none Details | Review
Screenshot of more battery spec figures (39.12 KB, image/png)
2006-07-21 17:24 UTC, Tobias Wolf
  Details
Screenshot of capacity info screen after patching (39.98 KB, image/png)
2006-07-30 08:42 UTC, Tobias Wolf
  Details

Description Tobias Wolf 2006-07-21 11:13:16 UTC
It’s likely due to my font settings but on this screen the units at the y-axis on the power charting screens are truncated.
Comment 1 Tobias Wolf 2006-07-21 11:15:33 UTC
Created attachment 69320 [details]
Screenshot of truncated labels
Comment 2 Richard Hughes 2006-07-21 15:22:58 UTC
Ahh, believe it or not you are actually hitting a hal problem... Really!

The charge being reported by your system if measured in mAh, and HAL converts this to uWh and reports it as mWh. Hence the numbers are 3 orders of magnitude what they should be. Relax, you're not using 4.6KW of power!

You need to apply the attached patch to get good readings, although I agree, we should be doing dynamic resizing of the text on the left.

I'll see what I can do.

Thanks for the bug,

Rchard.
Comment 3 Richard Hughes 2006-07-21 15:23:36 UTC
Created attachment 69335 [details] [review]
hal fix
Comment 4 Tobias Wolf 2006-07-21 16:30:03 UTC
Ah, I belive you. Was kind of wondering about the scales, too, when I saw the screenshots in the doc folder.*scratches head ...*
So it’s 10^-3, right?
Comment 5 Tobias Wolf 2006-07-21 16:32:19 UTC
And you’re right. This is what apci thinks I have:

present:                 yes
design capacity:         4800 mAh
last full capacity:      2300 mAh
battery technology:      rechargeable
design voltage:          11100 mV
design capacity warning: 0 mAh
design capacity low:     69 mAh
capacity granularity 1:  1 mAh
capacity granularity 2:  1 mAh
model number:            
serial number:           
battery type:            LION
OEM info:                SAMSUNG Electronics

Yes, the capacity _is_ low :-(
Comment 6 Richard Hughes 2006-07-21 16:59:36 UTC
Yes, that confims my initial assesment. You need the hal patch. I'll try to get the patch upstream asap.
Comment 7 Tobias Wolf 2006-07-21 17:24:03 UTC
Created attachment 69343 [details]
Screenshot of more battery spec figures

Ok, I will give it a shot and compile hal on the next occasion.

Here’s another thing I encountered on the first page. At least the values are not human-readable, and I don’t know whether they convert from the mAh figures.

Does the patch attack this problem as well?
Comment 8 Tobias Wolf 2006-07-30 01:25:10 UTC
Hi,

I built the Ubuntu Edgy hal with the patch and all battery-related figures make sense (e.g., 24W consumption).

One minor cosmetic issue is that the capacity is given as 53280 mWh even though it would the prettier as 53 Wh.
Comment 9 Richard Hughes 2006-07-30 08:03:02 UTC
Nice one thanks. Can you attach a screenshot of how the capcacity is show as mWh on your system please. Thanks.
Comment 10 Tobias Wolf 2006-07-30 08:42:53 UTC
Created attachment 69900 [details]
Screenshot of capacity info screen after patching

Here it is. (Note that the displayed icon is small because I moved the scalable icons out of the icon theme folder. I sent another reply via mail regarding this bug ( Bug 348994 ) but it is being held for moderator approval with the reason "Message has implicit destination".)
Comment 11 Tobias Wolf 2006-07-30 08:45:40 UTC
Note the remaining time (1 min) and the charge (100%).
Comment 12 Richard Hughes 2006-07-30 08:53:10 UTC
The rate in mWh has a lot of precision (25420) and converting it to plain Wh would loose lots of info, altho I agree we are showing too much info. What about a reading like "25.4 Wh" rather than 25420mWh or "25Wh"

And for the reading of 1 min and charge 100%, that looks odd, but it's quite normal when the battery is nearing the end of it's life. We should probably supress it from the more screen tho.
Comment 13 Tobias Wolf 2006-07-30 09:09:00 UTC
> What about a reading like "25.4 Wh" rather than
> 25420mWh or "25Wh"
 
That sounds reasonable to me.
 
 
> And for the reading of 1 min and charge 100%, that looks odd,
> but it's quite normal when the battery is nearing the end of
> it's life. We should probably supress it from the more screen
> tho.
 
I hope it isn´t exactly dead; it still gives me 1.2 h under normal load. After I realized the discrepancy I looked at the tooltip, which said 1h20min. Then I removed the mains and suspend was immediately activated because of the critical battery level. After waking up the figure on the info screen was back to normal. A new bug?
Comment 14 Richard Hughes 2006-07-30 09:33:19 UTC
(In reply to comment #13)
> > What about a reading like "25.4 Wh" rather than
> > 25420mWh or "25Wh"
> 
> That sounds reasonable to me.

2006-07-30  Richard Hughes  <richard@hughsie.com>

	* src/gpm-power.c:
	Reduce the precision to 100mW as the big numbers are too clumsy.
	The new format is '24.5 W' rather than '24520mWh'

> I hope it isn´t exactly dead; it still gives me 1.2 h under normal load. After
> I realized the discrepancy I looked at the tooltip, which said 1h20min. Then I
> removed the mains and suspend was immediately activated because of the critical
> battery level. After waking up the figure on the info screen was back to
> normal. A new bug?

Yes, please open a new bug and we can discuss it there.

Richard.
Comment 15 Richard Hughes 2006-08-31 07:39:58 UTC
My patch has been applied to HAL. The soon-to-be-released version 0.5.8 will contain this fix and should fix the issues with values being too large.
Comment 16 Richard Hughes 2006-08-31 07:41:45 UTC
*** Bug 353636 has been marked as a duplicate of this bug. ***