I've been experiencing this bug as well on my HP Pavilion dv6000 ever
since Karmic. I think the problem is related to the 'rate' that is
reported through lshal and devicekit. The former reports the rate as
-1:
$ lshal | grep battery | grep rate
battery.charge_level.rate = 0 (0x0) (int)
This is likely the same bug as
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/370999. Burning
progress over 2 gigabytes fails. That bug references upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=582261, which indicates it is
fixed in 2.26.3. IIRC, Karmic will have 2.28, so this
This is likely the same bug as
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/370999. Burning
progress over 2 gigabytes fails. That bug references upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=582261, which indicates it is
fixed in 2.26.3. IIRC, Karmic will have 2.28, so this
This is likely the same bug as
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/370999. Burning
progress over 2 gigabytes fails. That bug references upstream bug
https://bugzilla.gnome.org/show_bug.cgi?id=582261, which indicates it is
fixed in 2.26.3. IIRC, Karmic will have 2.28, so this
Replacing XSMP for a better way is a noble goal. However, it is
ridiculous that Gnome released 2.24 with a half done version of the new
protocol and no trace of the XSMP support. That simply speaks to bad
management at the Gnome project.
This bug is not something Ubuntu can fix at this point,
I have a similar problem on my HP Pavilion dv6700 laptop.
'battery.reporting.design' is constant, but
'battery.charge_level.design' changes. Is there any way to configure
g-p-m to use the former value, or is this something set in the code?
--
g-p-m doesn't save charge and discharge profiles
I've seen the same problem with Rhythmbox since upgrading to Intrepid.
Searching the bug reports, I found this one:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/276603, which
references this Gnome bug:
http://bugzilla.gnome.org/show_bug.cgi?id=554556. The description isn't
exactly the
I can confirm that this is happening on my Hardy laptop. It didn't used
to happen on Hardy, but now does. The screen saver looks like it's
going to kick in, but then at the last moment it stops and the screen
appears as before. This also prevents power saving (like turning off
the screen). If
