Hi, could you please try the version of GPM from this PPA:
https://launchpad.net/~showard314/+archive/ppa
and try to recreate this bug?
--
gnome-power-manager when removing or inserting power cable
https://bugs.launchpad.net/bugs/447304
You received this bug notification because you are a
** Branch linked: lp:~showard314/gnome-power/LPbug_447304
--
gnome-power-manager when removing or inserting power cable
https://bugs.launchpad.net/bugs/447304
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
:
dbus_g_proxy_call()...
Returns : FALSE if an error is set, TRUE otherwise.
So it's returning FALSE without setting ERROR non-NULL.
[Scott Howard]: Thanks for looking at this, Richard. I found this, and think
we're on to
something:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541632
By passing
Upstream applied the patch, could someone with the bug confirm that it is fixed
in this PPA so we can get this into Karmic before release? Thanks.
https://launchpad.net/~showard314/+archive/ppa
** Bug watch added: GNOME Bug Tracker #598221
https://bugzilla.gnome.org/show_bug.cgi?id=598221
**
*** This bug is a duplicate of bug 447304 ***
https://bugs.launchpad.net/bugs/447304
Upstream applied the patch, could someone with the bug confirm that it is fixed
in this PPA so we can get this into Karmic before release? Thanks.
https://launchpad.net/~showard314/+archive/ppa
** This bug
** Also affects: devicekit-power (Ubuntu)
Importance: Undecided
Status: New
--
[Karmic] power management icon says laptop is connected to power when it isn't
https://bugs.launchpad.net/bugs/393008
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Pointing out two similar bugs:
Bug #381242
Bug #384304
For further debugging try:
'devkit-power --dump'
And see if those values correspond to the real state.
--
[Karmic] power management icon says laptop is connected to power when it isn't
https://bugs.launchpad.net/bugs/393008
You received
Fixed in 2.28.1
gnome-power-manager (2.28.1-0ubuntu1) karmic; urgency=low
* New upstream bug fix release:
- Add missing indirection to return value of DriveSetAllSpindownTimeouts
call.
- Fix failure error messages and comments.
- Help the kernel through its sleep key
- DeviceKit-disks is expecting an int as a value, not a uint.
--
gnome-power-manager when removing or inserting power cable
https://bugs.launchpad.net/bugs/447304
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
The upload of GPM 2.27.91 included the patch. I no longer have screen
blanking problems, can anyone else confirm this? Thank you.
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Fix Released
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You
From comment #22, we needed 3 patches: 2 for xorg and 1 for GPM. GPM's
patch was applied with 2.7.91-0ubuntu1 (that's why I put GPM to fixed
released). One of xorg's was applied with 2:1.6.3-1ubuntu2.
xorg-server still needs this patch:
Thanks for testing this so much. This bug has been a moving target
since gnome-session, xorg (which keeps track of IDLE), and GPM have
been changing how they keep track of IDLE sessions quite a bit (see
bug #397839).
I have a new version at
https://launchpad.net/~showard314/+archive/ppa, which
Thanks for your report. Here is some information as to where inhibit went:
http://blogs.gnome.org/hughsie/2009/01/28/inhibits-and-the-new-world-order/
Basically all inhibiting is done with gnome-session-manager. The dbus
interface is described in the gnome-session documentation in /usr/share
!
** Changed in: gnome-power-manager (Ubuntu)
Status: In Progress = Triaged
** Changed in: gnome-power-manager (Ubuntu)
Assignee: Scott Howard (showard314) = (unassigned)
** Bug watch added: GNOME Bug Tracker #593800
http://bugzilla.gnome.org/show_bug.cgi?id=593800
** Changed in: gnome
http://git.gnome.org/cgit/gnome-power-manager/commit/?id=a472d25191ec3202ecc4c0d1a652bd32e87fef8f
Thanks for the report, the fix has been committed upstream and will arrive with
version 2.27.92.
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Low
** Changed in:
@Noel: The intention of the applet is to inhibit auto-standby.
However, the new version in the above linked ppa has a patch which
might also inhibit the screen saver as well since it will inhibit the
gnome session from going idle. I'm not 100% sure though. Does either
version (karmic official repo
** Description changed:
- With the inhibit applet enabled:
+ With the inhibit applet enabled (using patched version):
1) does the screen blank when power preferences is set to blank it? (no)
2) does it suspend at the time set in power preferences? (no)
3) can you manually shutdown? (no)
** Description changed:
- With the inhibit applet enabled (using patched version):
+ With the inhibit applet enabled (using the patched version from upstream, see
linked ppa below):
1) does the screen blank when power preferences is set to blank it? (no)
2) does it suspend at the time set in
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Triaged
--
gnome-power-manager needs several minutes to load at startup
https://bugs.launchpad.net/bugs/296451
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Moving this bug to xscreensaver since it exists when you are using a
different power manager and does not exist when using gnome-screensaver.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Triaged
** Also affects: xscreensaver (Ubuntu)
Importance: Undecided
Status:
Thanks for the pointing it that out, sorry I misread it. I'm resetting
this bug to the previous state.
** Changed in: gnome-power-manager (Ubuntu)
Status: Invalid = Confirmed
** Changed in: xscreensaver (Ubuntu)
Status: New = Invalid
--
Screen not locked on resume from
Thanks for confirming in Karmic! Do get GPM's debugging messages go to:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager
Can you follow the steps for:
Getting DBUS info
Getting info from GPM
And post the output here for recreating the bug?
Also, could you type the following into the terminal:
...@gmail.com wrote:
On 09/10/2009 10:02 AM, mac_v wrote:
The thing is that the patches described in Richard's blog have been applied
but none of them seem to have fixed this issue... :(
Seems like no one really knows where the problem really is !
Scott Howard , you might wanna consider re
I submitted a new bug report at:
https://bugzilla.gnome.org/show_bug.cgi?id=594739. You can add yourself to the
cc: list there and add any additional information if it is missing it. Thanks
for your help!
** Bug watch added: GNOME Bug Tracker #594739
@mac: that warning was placed in to see if the conditions causing the
idle were still occuring in x. The author of GPM believes that the three
patches should have fixed it (and ubuntu has the three patches), but if
you are seeing the warnings, that means the bugs still remains in x
somewhere.
I
Thanks for checking, I'm setting this back to confirmed.
status confirmed
2009/9/18 Սահակ petros...@gmail.com:
I am still seeing this bug in 2.27.92, but now it gives a different
error message.
** Attachment added: gpp.png
http://launchpadlibrarian.net/32000351/gpp.png
--
Help does
I think multiple bugs are getting mixed together.
See bug 397839.
According to Bryce at that bug report, xorg has been properly patched
with both patches that Richard Hughes requests.
gnome-power-manager is at a version where its fix is included.
So xorg says the bug is invalid since they have
** Changed in: xorg-server (Ubuntu)
Status: Fix Released = Triaged
--
Screen randomly goes off in karmic
https://bugs.launchpad.net/bugs/397839
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
Thanks for commenting on this bug.
1) It is marked for expiration because no one has replied with more
information after it was marked incomplete.
(https://wiki.ubuntu.com/Bugs/Status). It was marked incomplete
because there was not enough information for a developer to work on
the bug and it was
Thanks for the testing. From your comment: Now my computer suspends
normally when I close the lid and resumes when I open the lid. Is the
bug fixed or is it still a problem? If it is fixed, feel free to mark
this bug as Fix Released
As for the suspend/hibernate issue: is an unrelated to this bug
Thanks. What video card do you have?
You can get it by pasting the output of: 'lspci -nn | grep VGA'
The original reporter had an Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller
** Changed in: gnome-power-manager (Ubuntu)
Status: Fix Released = Incomplete
--
Monitor
Thanks. I'm adding the xorg intel drivers to this bug since both
reporters have Intel chipsets.
** Also affects: xserver-xorg-video-intel (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Monitor does not turn back on and computer hangs when laptop lid is closed
+
This is an important bug, are we sure it is fix released? So far all comments
have been from people testing the PPA. From Loic's comments:
Closing the GPM task as things work for me with the patched xorg-server which
I just uploaded; needs to be reviewed by release team still
I don't think it
Thanks for your report.
Attached is the patch for the first fix.
The newest version of the GPM manual does not discuss IBM laptop sliders
or contain the phrase the bug describes in 8.6.
I'll send them upstream later today.
** Changed in: gnome-power-manager (Ubuntu)
Status: New =
** Attachment added: low_or_critical_help.patch
http://launchpadlibrarian.net/29619792/low_or_critical_help.patch
** Attachment removed: gnome-power-manager.orig.xml
http://launchpadlibrarian.net/29619775/gnome-power-manager.orig.xml
--
gpm manual errors: 8.2 8.6
Just a comment as to what I was doing above:
the 100 papercuts project would like to keep track of their successes
and fixes, and since this bug was rejected from their project we should
keep it as invalid
Once the fix is in Karmic, we can say it is fix released. If it is in
an unreleased bzr
** Bug watch added: GNOME Bug Tracker #590023
http://bugzilla.gnome.org/show_bug.cgi?id=590023
** Changed in: gnome-power
Importance: Undecided = Unknown
** Changed in: gnome-power
Status: New = Unknown
** Changed in: gnome-power
Remote watch: None = GNOME Bug Tracker #590023
--
running on a virtual machine would be good, but it may be easier to
just try using the liveCD. The daily live cd is found here:
http://cdimage.ubuntu.com/daily-live/current/
and information on the Karmic Alphas is here:
http://www.ubuntu.com/testing/
On Tue, Jul 28, 2009 at 2:09 PM, Matt
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.
If you need a fix for the bug in previous versions of Ubuntu, please
follow the instructions for
Thanks for the report and working to make Ubuntu better. Have you had this
problem recently in Karmic? If so, could you run the following command in the
terminal:
apport-collect 382176
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
computer randomly shuts down
Thanks for the report. Does this bug exist in the most recent version of GPM in
Karmic (2.27.2-0ubuntu2)? If so, can you run the follow command from the
terminal:
apport-collect 386996
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
suspend timeout ignored
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Does this bug exist in Karmic Alpha 3? If so, could you
please attach your X server configuration file (/etc/X11/xorg.conf) and
X server log file (/var/log/Xorg.0.log) to the bug report as individual
uncompressed
Thanks for your report and helping make Ubuntu better.
This does seem somewhat inconsistent. This is an Ubuntu specific change, and I
don't think it is necessary. Commit 13 of ubuntu packaging:
http://bazaar.launchpad.net/~gnome-power-manager-team/gnome-power/trunk/revision/13
added
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = In Progress
** Changed in: gnome-power-manager (Ubuntu)
Assignee: (unassigned) = Scott Howard (showard314)
--
Feature request : Possible improvements for notifications
https://bugs.launchpad.net/bugs/399492
You received
More information from the author of GPM (Richard Hughes), this was sent
to the gnome-power-manager developer mailing list:
Okay, after having F11 g-p-m blank the screen on me (not using
nouveau, that's a separate issue) whilst watching some short videos in
totem yesterday, I got really angry.
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
Great! Thanks for the report and for following up.
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Fix Released
--
Screen corruption on resume (Karmic-testing)
https://bugs.launchpad.net/bugs/377299
You received this bug notification because you are a member of Ubuntu
Thanks for checking in Karmic. This 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 advance.
Hello, when you do do it, please see bug #390669. There was a pending
bug to update how notify-osd was working in GPM to properly use
int32-hints.
--
notify-osd patch needs to be rewritten
https://bugs.launchpad.net/bugs/406396
You received this bug notification because you are a member of
Has anyone tested this bug with Karmic yet? There has been significant
changes to GPM from Jaunty to Karmic, and if this is not fixed in Karmic
we should work on it. While it is a security issue, Ubuntu tends to be
extra careful in allowing SRUs. The best course of action would be to
get it fixed
I marked as incomplete until it is checked in Karmic, then it can go
back to confirmed.
--
Screen not locked on resume from hibernate/suspend
https://bugs.launchpad.net/bugs/42052
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Thanks for the report. I can't reproduce this bug either (after
suspending the settings are still the same). We can try some things to
figure out what is causing this.
First, you can follow the instructions at:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Getting%20info%20from%20GPM
to run
Thanks for the input Martin. I sent this upstream:
http://bugzilla.gnome.org/show_bug.cgi?id=590259 . Steve, could you add
yourself to the cc: list for that one?
** Bug watch added: GNOME Bug Tracker #590259
http://bugzilla.gnome.org/show_bug.cgi?id=590259
** Also affects: gnome-power via
From Richard Hughes, author of GPM, in response to our bug request:
For example, right now GPM gives the following notification:
title = Power Information
message = Laptop battery fully charged (100%). Provides 2 hours 5 minutes
battery runtime.
Can be made:
title = Battery full
message =
Thanks for the debugging info. We have some more commits coming
through over the next week (I believe 2.27.3-0ubuntu1 will be
officially released Monday on Ubuntu). Let's try to test again once it
is released. I'll leave it incomplete for now until we try against the
newest release.
--
Power
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
Thanks for helping with this bug. Fix released indicates that the bug
has been fixed in the latest development release of Ubuntu [1]. To
target for an SRU, you can target for release (as lunch did above).
However, this bug is not eligible for SRU since it is not a security
flaw nor a potential for
thanks for bringing this up - could you try a liveCD of Karmic and see
if those icons are better?
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
Laptop power status notification icon is uninformative
https://bugs.launchpad.net/bugs/404525
You received this bug
Thank you taking the time to report this bug and helping to make Ubuntu better.
However, processing the crash report to get detailed information for the
developers failed as the retracer did not generate a useful symbolic stack
trace.
Please try to obtain a backtrace manually following the
** Also affects: gnome-power via
http://bugzilla.gnome.org/show_bug.cgi?id=590279
Importance: Unknown
Status: Unknown
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
user-defined notification of battery status
https://bugs.launchpad.net/bugs/406803
Sorry, I wasn't clear. I was checking to make sure that it had not
changed behavior in Karmic (I'm away from my laptop for a bit).
I believe Ubuntu is currently blocking the exact bubble you are requesting
since they think it is redundant (the icon should change in gnome-panel).
(the patch removes the acbattery notification which is part of
upstream's GPM code. I don't think upstream GPM has a batteryAC
notification, so we might have to add it)
--
Laptop power status notification icon is uninformative
https://bugs.launchpad.net/bugs/404525
You received this bug
A fix for this has been committed upstream.
http://git.gnome.org/cgit/gnome-power-
manager/commit/?id=f669bea7168ef5fecbb11993e4ab35cead26b5a4
I believe 2.27.3 will be released on Monday, we should test the new
release (2.27.3-0ubuntu1) when it is available to confirm it is fixed.
** Changed
Great! If it comes back, please reopen this bug by setting it to new.
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Invalid
** Changed in: devicekit-power (Ubuntu)
Status: New = Fix Released
--
Laptop battery indicator indicates 0% charge when fully charged
The first package is ready for testing.
This is my first time packaging, patching, using ppas, and bzr - so please bear
with the extra commits and ppa versions while I figured out how to actually
upload the files!
The ppa is here:
https://launchpad.net/~showard314/+archive/ppa
Could you please
@Mac Steve
thanks for working out the icons. I saw the icons in the source code
and am not familiar with notify-osd, so your help on this is great.
Let me know if there is anything you need in the code to make it work
(I'm working on the upstream project).
@ Steve
The percentages are more
Thanks for your report and helping make Ubuntu better. Since you have
attached all the relevant logs, I'm marking as confirmed. Since this
will affect a large population of users, the status is high (especially
since there is potential data loss from unwanted shutdowns, suspends,
etc.)
There is
** Tags added: ping-2.27.3
--
Power Management Settings Are Not Applied / Retained
https://bugs.launchpad.net/bugs/406599
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
** Tags added: ping-2.27.3
--
Incorrect battery recall warning for Lenovo T61
https://bugs.launchpad.net/bugs/403564
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
** Tags added: ping-2.27.3
--
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 gnome-power-manager in ubuntu.
--
desktop-bugs mailing list
** Tags added: ping-2.27.3
--
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 ubuntu.
--
desktop-bugs mailing list
** Tags added: ping-2.27.3
--
brightness applet shows red cross if doubled click
https://bugs.launchpad.net/bugs/326826
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
Hello, we haven't heard about this bug in some time, and policy-kit in
now standard in Debian/Ubuntu. Has this bug been fixed or resolved?
Thanks. (setting to incomplete so I know to check up on this, if it
still exists, set back to triaged)
** Changed in: gnome-power-manager (Ubuntu)
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue for you. Can you try
with the latest Ubuntu release? Thanks in advance.
(setting
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Can you try with the latest Ubuntu release? Thanks in advance.
(setting to
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently, and GNOME has marked this bug as fixed
released. We were wondering if this is still an issue for you. Can you
try with the latest
Thanks for replying. Since the primary bug here, that screen brightness
dims after screensaver initializes in xubuntu is fixed, I'll mark this
as fix released. However, since the fn hotkeys are still buggy, could
you check if they are still buggy in Karmic (this can be tested with a
liveCD)? If
Some how we get un-synced from launchpad.
Scott Howard asked if it could be tested with the daily liveCD since
there were commits this week trying to address this issue. Here is the
reporter's response:
-- Forwarded message --
From: Gilly Creamy gillycre...@gmail.com
Date: Sat
This may just be that your gconf got buggy some how.
You can try resetting the gconf settings by following the instructions here:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Getting%20GConf%20values
I'll close this since it seems to be a configuration problem. If you'd
like additional help
new ppa is up: https://launchpad.net/~showard314/+archive/ppa
Pretty much finalized low and critical battery notifications:
from the todo
- [DONE] write a check to see if any other battery device peripherals(PDA,
phone, wireless mouse/kb, UPS) exist on the system, if they do the title should
I'm just working on the strings and not touching the icons yet. This
is because the strings patch will go upstream and the icons/notify-osd
patch should be done within Ubuntu. I'm getting close to finishing it
and sending it upstream.
Ubuntu used to have it's own notify-osd patch, but Martin Pitt
setting back to confirmed in GPM. DKP is misreporting the battery level
so GPM is reporting what it is told. Until someone starts working on
this, keep checking the newestversions
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
--
Laptop battery indicator indicates 0%
Thanks for your report and helping make Ubuntu better. After rebooting,
has this crash reappeared? It appears that HAL crashed after the
upgrade, which caused GPM to crash.
(From dmesg):
hal segfaulted first:
[362742.276805] hald[2737]: segfault at b7a16008 ip b7d3e078 sp bfb89ecc error
4 in
*** This bug is a duplicate of bug 407491 ***
https://bugs.launchpad.net/bugs/407491
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 407491, so it is being marked as such. Please look
*** This bug is a duplicate of bug 407491 ***
https://bugs.launchpad.net/bugs/407491
The bug still exists, I'm condensing similar bug reports to: bug 407491.
Please follow that bug and add any additional information.
** This bug has been marked a duplicate of bug 407491
[karmic]
*** This bug is a duplicate of bug 354269 ***
https://bugs.launchpad.net/bugs/354269
** This bug has been marked a duplicate of bug 354269
[Acer Aspire one] suspend/resume failure
--
system won't suspend on lid close
https://bugs.launchpad.net/bugs/400097
You received this bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering if this is still an issue
for you. Were you able to install the package after a reboot? Thanks in
advance.
**
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 379599 ***
https://bugs.launchpad.net/bugs/379599
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 379599, so it is being marked as such. Please look
Could someone test this with the most recent Karmic GPM
(2.27.5-0ubuntu1)? Upstream has put some bug fixes in that should have
fixed this in their latest versions.
--
System shutdown on 0% for 1 of 2 batteries.
https://bugs.launchpad.net/bugs/379599
You received this bug notification because you
I'm sorry that this bug has been ping-ponged around, but everyone's
trying to find the right location for this bug. Duplicate does not mean
take a hike, it means that we are trying to bring together all the
information from different reporters in order to process the 300+ open
bugs in
Max, could you try resetting the gconf settings by following the instructions
here:
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager#Getting%20GConf%20values
Although Arnaud's diff didn't show much (besides a different history
section), it could be worth updating to the new defaults. Max, just
Great, thanks for checking.
On Tue, Aug 4, 2009 at 12:42 AM, Phil Sungps...@mit.edu wrote:
Scott, I can confirm that this still happens on g-p-m 2.27.5-0ubuntu1,
and with a completely fresh gconf and profile (new user account).
--
[karmic] gnome-power-preferences not storing settings
Richard Hughes, the author of gnome-power-manager, has written a bodge
in the most recent version of Karmic gnome-power-manager (2.27.5) [1] to
prevent screen blanking when using inhibit in gnome-session or xsync.
Could you test it to see if it is now working properly (a daily liveCD
of karmic
*** This bug is a duplicate of bug 381116 ***
https://bugs.launchpad.net/bugs/381116
This is now a known bug in gnome-session [1], and Robert Hughes (the
author of gnome-power-manager) wrote a bodge [2] to fix it. This fix
is included in the most recent version Karmic version of gnome-power-
Thanks for following up. It appears that the install modified a file HAL
needed to continue to run, and a reboot was necessary. Closing since
Ubuntu now uses devicekit-power instead of HAL, and a reboot was
necessary to properly boot with the new kernel.
** Changed in: gnome-power-manager
Thanks for your report and helping make Ubuntu better. Could you attach the
output of:
devkit-power --dump
with the battery charging and with the battery full (to compare). GPM now gets
info from devicekit-power instead of HAL, so we should just make sure that
those two interfaces are on the
Hello, this bug was supposedly fixed in version 2.27.5. Could you please
test the latest release in Karmic and confirm that it is working? I was
able to get it working.
The inhibit call was moved from gnome-power-manager to gnome-session-
manager over the past few weeks and should be working now.
Great! Thanks for reporting this bug.
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Fix Released
--
[karmic] inhibit applet not working
https://bugs.launchpad.net/bugs/389857
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
ppa updated, the string patch should be complete now. I'll test it for a
couple more days before sending upstream. Here are the overall changes:
Battery charged:
title = Battery Charged
message = NONE
(message used to be: Your laptop battery is now fully charged)
todo: change title from battery
401 - 500 of 586 matches
Mail list logo
