[Bug 439783] Re: Regression: devicekit-power does not display remaining battery time
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) battery.reporting.rate = -1 (0x) (int) Devicekit reports the rate as way too little: $ devkit-power --dump | grep energy energy: 47.8336 Wh energy-empty:0 Wh energy-full: 69.1456 Wh energy-full-design: 88.8 Wh energy-rate: 0.0148 W When I divide the full value by the rate, I get 4672 hours, which is much more than I can get out of my battery. Just playing with numbers, it looks like the rate may be off by a factor of 1500. If it were 22.2 watts, then the energy-full/energy-rate would be about 3.1, which is much closer to what I can actually get from this battery. Of course, this is assuming that GPM even uses the devicekit numbers at all. If I get motivated later, maybe I'll look through the GPM source to see if I can find where and how the time remaining is calculated. -- Regression: devicekit-power does not display remaining battery time https://bugs.launchpad.net/bugs/439783 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 346489] Re: Progress bar stays on 0% even after the burning begins
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 fix should be there. ** Bug watch added: GNOME Bug Tracker #582261 http://bugzilla.gnome.org/show_bug.cgi?id=582261 -- Progress bar stays on 0% even after the burning begins https://bugs.launchpad.net/bugs/346489 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 399958] Re: brasero progress bar resets itself several times
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 fix should be there. ** Bug watch added: GNOME Bug Tracker #582261 http://bugzilla.gnome.org/show_bug.cgi?id=582261 -- brasero progress bar resets itself several times https://bugs.launchpad.net/bugs/399958 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 442091] Re: Brasero's status bar disspapears when recording disc
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 fix should be there. ** Bug watch added: GNOME Bug Tracker #582261 http://bugzilla.gnome.org/show_bug.cgi?id=582261 -- Brasero's status bar disspapears when recording disc https://bugs.launchpad.net/bugs/442091 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 249373] Re: gnome session does not restore the previous session
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, but I hope that those in charge of Ubuntu learn from this problem. It appears that Gnome cannot be trusted to release a new version without major regressions, and Ubuntu needs to rigorously test new versions before committing to them. This regression was noticed in mid July, 3 months before 8.10 was released. If this had been evaluated then, Ubuntu could have avoided releasing a version with this problem (either fixed somehow, not releasing 2.24, or going the Gentoo route and holding the session manager at 2.22). -- gnome session does not restore the previous session https://bugs.launchpad.net/bugs/249373 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 302570] Re: g-p-m doesn't save charge and discharge profiles
It looks like this value is used in the code and not configurable. I
downloaded the source and found were 'battery.charge_level.design' was
used in src/gpm-cell.c. Instead of changing that, however, I just
commented out its usage in gpm_cell_get_id() to not use that value in
constructing the ID. See the attached patch for information.
I think this might have been how it used to be, because I had older
~/.gnome2/gnome-power-manager/profile-Primary-{dis,}charging.csv files
that didn't have the "design" ID.
Obviously, this patch is just a quick hack. I don't know enough about
g-p-m to know what is the correct solution. Whether that is just
removing the charge_level code I commented out, or making it an option,
or something entirely different.
Does anyone know if there is an upstream gnome bug for this issue?
** Attachment added: "Hack fix to remove charge_level.design from id"
http://launchpadlibrarian.net/20600417/gpm-cell.patch
--
g-p-m doesn't save charge and discharge profiles
https://bugs.launchpad.net/bugs/302570
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 302570] Re: g-p-m doesn't save charge and discharge profiles
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 https://bugs.launchpad.net/bugs/302570 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 297086] Re: Rhythmbox crashes after downloading a podcast
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 same, but the stack trace is very similar. The report indicates that the bug was fixed upstream. The Ubuntu bug has instructions for building your own patched version. Maybe Ubuntu could apply this patch into an update for the Intrepid version? -- Rhythmbox crashes after downloading a podcast https://bugs.launchpad.net/bugs/297086 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 241206] Re: On Hardy screen saver never displays
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 I lock the screen, the screen saver seems to work normally, including turning off the screen. It almost seems like as the screen saver is engaging, it thinks detects a keypress or mouse movement and thinks it should not screen save. When I lock the screen, it immediately brings up the password box to unlock it, as if I had pressed a key or moved the mouse. -- On Hardy screen saver never displays https://bugs.launchpad.net/bugs/241206 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
