Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Significant changes have occurred since
2.22.1-1ubuntu4.1 (we are on 2.27.2-0ubuntu2). Has there been any
additional upgrade failures? The issue that you reported is one that
should be reproducible with the live
Hello - I'm just checking in on this bug, has it been fixed in Karmic?
Also, has upstream been made aware of this bug/fix?
--
Power Management shows 1 hour 1 minute instead of Never
https://bugs.launchpad.net/bugs/344236
You received this bug notification because you are a member of Ubuntu
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make Ubuntu
better. There appears to be two issues here:
1) brightness control using Fn keys
2) blinking when using brightness control
We should focus one bug per report, and we should focus on 1 above
since 2 has been reported by
*** This bug is a duplicate of bug 328946 ***
https://bugs.launchpad.net/bugs/328946
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 328946, so it is being marked as such. Please look
Thanks for checking on this - someone else reported the same thing, so
I'll mark as confirmed.
Thanks for the report, the feature request should be send directly to
the upstream authors at bugzilla.gnome.org, for forwarding instructions
please have a look to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Good job debugging this, those logs are helpful.
The issue that you reported is one that should be reproducible with the
live environment of the Desktop CD of the development release - Karmic
Koala. It would help us greatly if you could test with it so we can
work on getting it fixed in the next
Nice detective work. We should use the liveCD for all debugging from now on.
Let's try the Ubuntu versions first.
The bug only appears with: linux-headers-generic - 2.6.28.11.15 (i386),
linux-restricted-modules-generic - 2.6.28.11.15 (i386), linux-generic -
2.6.28.11.15 (i386) and
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
*** This bug is a duplicate of bug 312440 ***
https://bugs.launchpad.net/bugs/312440
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 312440, so it is being marked as such. Please look
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Yes, that is correct! Thanks for your help!
On Mon, Jul 13, 2009 at 9:48 PM, Jeenu Vjee...@gmail.com wrote:
Thanks for the response.
Since I'm new the procedure you just mentioned, I'd appreciate if you
could help me a bit here: for the testing purpose, I'm supposed to
download the Alpha 2
Great, thanks for explaining it. I saw some gnome git commits talking
about hard drive spinning down too - it seems like they are actively
working on it. Great job finding the upstream report and for adding to
their conversation!
** Also affects: gnome-power via
Architecture: amd64
DistroRelease: Ubuntu 9.10
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
Uname: Linux 2.6.31-2-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
--
apport-hook in GPM no longer attaches gnome-power-bugreport.sh
Architecture: amd64
DistroRelease: Ubuntu 9.10
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
Uname: Linux 2.6.31-2-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
--
apport-hook in GPM no longer attaches gnome-power-bugreport.sh
i'll try to burn the daily build - deskptop. would this
do?
On Sun, 2009-07-12 at 14:02 +, Scott Howard wrote:
@mzc: Thank you for the GPM trace. The issue that you reported is one
that should be reproducible with the live environment of the Desktop CD
of the development release - Karmic
Great! I think that they would really appreciate that. Perhaps you can
drop them an email on their mailing list:
gnome-power-manager-l...@gnome.org
to get feedback.
On Tue, Jul 14, 2009 at 3:52 AM, Derek Whited-ma...@yahoo.com wrote:
Ok, I will do that. I am currently working on a redo of the
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu - Karmic Koala. It won't be
fixed in previous versions of Ubuntu because the package doesn't fit the
requirements
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Committed = Fix Released
--
gnome-power-manager uses all available CPU
https://bugs.launchpad.net/bugs/324903
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
I'm happy to answer your questions:
First, how can I reproduce it? Start working all day on the desktop cd?
Loading a liveCD and testing suspend through the GNOME logout/quit
sequence and a short timer would suffice. However, some bug reporters do
run a fully installed development version of
The reporter is interested in a workaround for a Jaunty problem, and not
interested in debugging in Karmic, so this bug was converted into a
question. Bug #380211.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
** Converted to question:
Great presentation and idea. I can see on the mailing list that there is
lots of support and feedback for this proposal. I'm marking as
triaged/wishlist. Steve, are you working on the patch? If not I'll try
to get a developer to look at this (or I'd take a crack at it).
** Changed in:
/usr/bin/gnome-power-manager-inhibit is an Ubuntu script.
It needs to be fixed or removed.
http://bazaar.launchpad.net/~gnome-power-manager-team/gnome-power/trunk/annotate/head%3A/debian/patches/14_inhibit_tool.patch
--
/usr/bin/gnome-power-manager-inhibit test doesn't work
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
No problem, I'll try to find someone or take care of it.
On Wed, Jul 15, 2009 at 11:14 AM, Steve Dodiersidnio...@gmail.com wrote:
I would really love someone to take care of it, i currently have a few
more important things to work on and i fear i won't be able to produce a
decent patch for it
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Since your report there has been significant changes and
improvements to power management in Ubuntu and gnome-power-manager. The
issue that you reported is one that should be reproducible with the live
environment
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
gpm manual is too vague and geared towards laptops
https://bugs.launchpad.net/bugs/390476
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for testing. So there was no difference between Karmic and
Jaunty's performance? It's still best to do debugging in Karmic since
the developers would be able to get fixes into the development release.
There are some additional debugging steps we can do to identify this problem.
First,
*** This bug is a duplicate of bug 380508 ***
https://bugs.launchpad.net/bugs/380508
I believe this was a typo duplicate since the reporter reported the same
bug consecutively. The bug was fixed in 2.27.1-0ubuntu1.
** This bug has been marked a duplicate of bug 380508
FTBFS fix on ARM for
Thanks for the report, the feature request should be send directly to
the upstream authors at bugzilla.gnome.org, for forwarding instructions
please have a look to http://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you
forward the bug, please post a link to the upstream bug report here.
Thanks in
The workaround mentioned in Divan's comment is:
A workaround is unloading/reloading the video kernel module, but
after this the brightness-changing-OSD doesn't appear anymore and I
guess there may be other issues, at least it's not the elegant way ;)
For developer reference, see bug #369777
--
*** This bug is a duplicate of bug 369777 ***
https://bugs.launchpad.net/bugs/369777
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 369777, so it is being marked as such. Please look
Since reloading the kernel video module fixed this bug, I've added
linux (Ubuntu) to this bug report. Which video card and driver are you
using? Your video card info can be found in /etc/X11/xorg.conf.
I'm unfamiliar with kernel level debugging/fixing, so if a member of the
kernel team can take a
*** This bug is a duplicate of bug 351586 ***
https://bugs.launchpad.net/bugs/351586
Thanks for testing and confirming.
Here's some stuff to try:
(from bug #399675)
A workaround is unloading/reloading the video kernel module, but
after this the brightness-changing-OSD doesn't appear anymore
*** This bug is a duplicate of bug 351586 ***
https://bugs.launchpad.net/bugs/351586
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 351586, so it is being marked as such. Please look
*** This bug is a duplicate of bug 351586 ***
https://bugs.launchpad.net/bugs/351586
** This bug is no longer a duplicate of bug 369777
Lenovo laptop brightness control problems (3000 100N and SL300)
** This bug has been marked a duplicate of bug 351586
please add lenovo-sl-laptop to
*** This bug is a duplicate of bug 224636 ***
https://bugs.launchpad.net/bugs/224636
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 224636, so it is being marked as such. Please look
Thanks for reporting this bug and verifying it was fixed.
You should probably open new bug reports for those two new issues, as this one
is now closed.
Also, those new bugs should be send directly to the upstream authors at
bugzilla.gnome.org, for forwarding instructions please have a look to
Hey Ken, are you still working on the patch or has it been tested and is
ready for merging?
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Triaged
--
notify-osd changes the way it supports int32-hints
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please attach the resulting log file of: gnome-power-
bugreport.sh gpm.log to the report? You might also want to take a
look at the debugging instructions located at
Thanks for reporting this bug and helping make Ubuntu better! Since this
appears to be a configuration error and not a programming bug, I'm
converting this to a question to better help the reporter fix his
problem. However, if it does turn out to be a programming bug, please
re-open the report.
Thanks for checking. Try with a live-cd
(http://cdimage.ubuntu.com/daily-live/current/) both with your sound
on and muted. We also have Ubuntu only patches which modify
notifications settings. If it doesn't work with Karmic, we should
build some PPAs without the notification patches to test this.
From the reporter:
Hi Scott
I finally managed to download Karmic alpha thanks to that helpful
little Firefox add-on DownThemAll!
I booted my Toshiba Satellite L300 from the CD and set the screen
saver to activate in 1 minute. Power management (AC and battery power)
was set to put computer to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
Thanks for your debugging work. I'm assigning this to the nvidia driver
package and confirming. Hopefully they will start including the 185
drivers soon in Karmic so this work around won't be needed.
** Also affects: nvidia-graphics-drivers-180 (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: GNOME Bug Tracker #472812
http://bugzilla.gnome.org/show_bug.cgi?id=472812
** Changed in: gnome-power
Status: New = Unknown
** Changed in: gnome-power
Remote watch: GNOME Bug Tracker #588124 = GNOME Bug Tracker #472812
--
[karmic] inhibit applet not working
** Bug watch added: GNOME Bug Tracker #472812
http://bugzilla.gnome.org/show_bug.cgi?id=472812
** Changed in: gnome-power
Status: New = Unknown
** Changed in: gnome-power
Remote watch: GNOME Bug Tracker #588124 = GNOME Bug Tracker #472812
--
/usr/bin/gnome-power-manager-inhibit test
.
** Affects: gnome-power-manager (Ubuntu)
Importance: Wishlist
Assignee: Scott Howard (showard314)
Status: Triaged
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Triaged
I'm assigning this to the linux package and removing GPM since the bug
exists in both KDE and GNOME, and only exists with a specific kernel
version.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Invalid
** Also affects: linux (Ubuntu)
Importance: Undecided
Thanks for the report. For completeness, can you attach a screen shot of
the warning?
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
Keeps showing recall warning
https://bugs.launchpad.net/bugs/402287
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
*** This bug is a duplicate of bug 381116 ***
https://bugs.launchpad.net/bugs/381116
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 381116, so it is being marked as such. Please look
I believe I can help this one a bit:
From Richard Hughes' blog:
http://blogs.gnome.org/hughsie/2009/01/28/inhibits-and-the-new-world-order/
inhibit is now a method of:
org.gnome.SessionManager
The API and documentation is now in gnome session manager, and the GPM inhibit
is no longer in GPM
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Invalid
--
When the laptop is inactive, screen dims but doesn't remember previous
brightness setting when reactivited
https://bugs.launchpad.net/bugs/216545
You received this bug notification because you are a member of
Thanks for the report. Is this a regression or did it behave like this
in Jaunty as well?
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
brightness value is reset when power properties is
added the bzr branch for this fix.
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Ken VanDine (ken-vandine) = (unassigned)
--
notify-osd changes the way it supports int32-hints
https://bugs.launchpad.net/bugs/390669
You received this bug notification because you are a member of
to the sponsors: the patch was written by Mirco Müller, can you see that
he gets the proper credit in the changelog? Thanks!
--
notify-osd changes the way it supports int32-hints
https://bugs.launchpad.net/bugs/390669
You received this bug notification because you are a member of Ubuntu
Desktop
wait a sec, there is a build error - i'll send an updated one
--
notify-osd changes the way it supports int32-hints
https://bugs.launchpad.net/bugs/390669
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
I'd like to remove ubuntu-main-sponsors, there are problems with the
patch. The patch is against 2.27.1, and the newest release is 2.27.2
I was able to update the patch for all except the 8th hunk
(gpm.manager.c, which is now the 7th hunk in this updated patch file). I
cannot find where the
(the above patch is with my updates for 2.27.2)
** Branch unlinked: lp:~showard314/gnome-power/karmic1_feedback-notify-
osd
--
notify-osd changes the way it supports int32-hints
https://bugs.launchpad.net/bugs/390669
You received this bug notification because you are a member of Ubuntu
Desktop
Great to hear! Thanks for testing. Unfortunately, we can't bring this
into previous versions of Ubuntu. The Stable Release Update [1] and
backporting policy [2] generally only allows security bugs or bugs that
could cause severe loss of data. Thanks again for helping make Ubuntu
better!
[1]
) = Scott Howard (showard314)
--
notify-osd changes the way it supports int32-hints
https://bugs.launchpad.net/bugs/390669
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
*** This bug is a duplicate of bug 378072 ***
https://bugs.launchpad.net/bugs/378072
** This bug is no longer a duplicate of bug 384416
[Gnome-Power-Manager] No Brightness-Control in Ubuntu Jaunty
** This bug has been marked a duplicate of bug 378072
no brightnesscontrol working
--
*** This bug is a duplicate of bug 378072 ***
https://bugs.launchpad.net/bugs/378072
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
--
Keeps showing recall warning
https://bugs.launchpad.net/bugs/402287
You received this bug notification because you are a member of Ubuntu
There has been a pretty significant change in how GPM and power
management in general works between Jaunty and Karmic, a patch won't
easily work (dependencies have changed significantly, HAL has been
deprecated in favor of devicekit-power). Fixing bugs in power
management has been a moving target
Thanks for your report and working to make Ubuntu better. Is this a
regression, did it work in Jaunty?
status incomplete
On Thu, Jul 23, 2009 at 7:09 AM, balduinbaldu...@gmx.com wrote:
** Visibility changed to: Private
--
gnome starts with minimal brightness
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
gnome starts with minimal brightness
https://bugs.launchpad.net/bugs/403075
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct subscriber.
--
desktop-bugs mailing
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
DIM will dim my screen even when not idle
https://bugs.launchpad.net/bugs/403248
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
Hey bug - this is upstream-able, but they have been doing a bunch of
work since 2.27.2. The new 2.27.3 should be out very soon (a few days),
maybe we should test it first and if it exists before sending it
upstream (unless you can build with git master and try it out before
2.27.3 comes out). I'm
*** This bug is a duplicate of bug 402287 ***
https://bugs.launchpad.net/bugs/402287
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 402287, so it is being marked as such. Please look
From a duplicate:
I've got a Lenovo battery with:
ASM P/N: 92P1142
FRU P/N: 92P1141
(top right corner of label)
So, I get a recall warning pointing me to the website[1]. I can't run
the automated checking system, so I called support. Turns out: there is
no recall. The problem is that I have a
*** This bug is a duplicate of bug 402287 ***
https://bugs.launchpad.net/bugs/402287
Yes, these are two separate bug symptoms most likely caused by the
same thing (incomplete battery recall functionality). Upstream
developers have been rolling out the recall warning recently and these
two
(Ubuntu)
Status: In Progress = Triaged
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Scott Howard (showard314) = (unassigned)
--
notify-osd changes the way it supports int32-hints
https://bugs.launchpad.net/bugs/390669
You received this bug notification because you are a member
** Summary changed:
- Can't hide incorrect battery recall warning
+ Keeps showing battery recall warning
--
Keeps showing battery recall warning
https://bugs.launchpad.net/bugs/402287
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
replaced. And I got the recall warning then, did the
recall and told the notice to leave me alone. I haven't gotten such a
notice until upgrading to Karmic, presumably because of the switch to
DeviceKit, and how it and g-p-m have regressed from HAL a bit.
On Thu, 2009-07-23 at 19:59 +, Scott
bneijt: Can you run the following from the terminal:
apport-collect 403564
Thank you.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Incomplete
--
Incorrect recall warning for Lenovo T61
https://bugs.launchpad.net/bugs/403564
You received this bug notification because
Thanks for helping with this bug. This is a regression that reappeared in
Karmic.
can you run the following from the terminal:
apport-collect 402287
Thank you.
--
Keeps showing battery recall warning
https://bugs.launchpad.net/bugs/402287
You received this bug notification because you are a
Inhibit has been moved to gnome session, away from gnome power manager.
gnome-power-manager-inhibit.py is no longer included in the gnome-power-
manager package [1], so this won't be fixed. Thanks for the report, it
actually helped point out that the inhibit applet was broken upstream as
well, and
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
--
Incorrect recall warning for Lenovo T61
https://bugs.launchpad.net/bugs/403564
You received this bug notification because you are a member of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can
DeviceKit-power is reporting the battery is recalled, assigning this bug
to DeviceKit-power as GPM is reporting what DKP is telling it.
from devkit-power --dump:
Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT0
native-path:
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = New
** Visibility changed to: Public
--
gnome starts with minimal brightness
https://bugs.launchpad.net/bugs/403075
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a direct
201 - 300 of 586 matches
Mail list logo
