** Summary changed:
- update to ubuntu 9.04 all media files broken!
+ update jaunty update: totem crashes when opening video audio
--
update jaunty update: totem crashes when opening video audio
https://bugs.launchpad.net/bugs/371045
You received this bug notification because you are a member
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 you tried it with
compiz installed on Jaunty (9.04). Can you try with the latest Ubuntu
release (maybe live
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.
** Changed
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.
** Changed
Gnome closed the bug since it is refers to an old version of Gnome. Does
this bug exist in Jaunty (9.04)?
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Incomplete
--
gnome-power-preferences crashed with signal 5 in g_return_if_fail_warning()
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
Looking at the attachments in this bug report, I noticed that an
attachment was not flagged as a patch. A patch contains changes to an
Ubuntu package that will resolve a bug and this attachment is one!
Subsequently, I've checked the patch flag for it. In the future when
submitting patches please
** Package changed: ubuntu = gnome-desktop (Ubuntu)
** Changed in: gnome-desktop (Ubuntu)
Status: New = Confirmed
--
window decorations disappear on login
https://bugs.launchpad.net/bugs/371585
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Package changed: gnome-control-center (Ubuntu) = xkeyboard-config
(Ubuntu)
--
Keyboard layout switching does not work
https://bugs.launchpad.net/bugs/372611
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
@onyxrev: This bug report is being closed due to your last comment
regarding this being fixed by removing an old madwifi script. For future
reference you can manage the status of your own bugs by clicking on the
current status in the yellow line and then choosing a new status in the
revealed drop
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Does this problem exist on Jaunty (9.04)?
If so, could you please attach the resulting log file of:
/usr/share/gnome-power-manager/gnome-power-bugreport gpm.log
to the report? You might also want to take a look
*** This bug is a duplicate of bug 375260 ***
https://bugs.launchpad.net/bugs/375260
Thank you for taking the time to report this bug and helping to make
Ubuntu better. I'm combining this bug with duplicate bug #375260 so you
will be subscribed to follow the bug there. Please feel free to
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please attach the following to the report?
The output of:
dbus-monitor --session
type='signal',interface='org.freedesktop.PowerManagement'
Can you attach the file gpm.gconf.values.txt and gpm.log to this
Thank you for taking the time to make Ubuntu better by reporting this
bug. For illustrative purposes, could you attach a screen shot to this
bug report?
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
[ubuntu karmic]Power History windows too big for netbook screen
Thank you for your bug report. This bug has been reported to the developers of
the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=582984
** Bug watch added: GNOME Bug Tracker #582984
http://bugzilla.gnome.org/show_bug.cgi?id=582984
** Changed in:
Marking as confirmed since Mandriva is experiencing the same bug.
https://qa.mandriva.com/show_bug.cgi?id=50087
@Nick:
Can you do
1) run: dbus-monitor --session
type='signal',interface='org.freedesktop.PowerManagement'
2) unplug your AC adapter
3) plug in your AC adapter
4) post the output from
@Nick: Thanks for the response, it is really helpful. Please try the
following:
$ lshal -m lshal.log.txt
and attach lshal.log.txt to the bug report. This may be a problem with
HAL/pm-utils.
Since dbus-monitor could not determine that the AC power was
unplugged/plugged in, I added pm-utils to
I'm sorry, I should be more specific:
Please try the following steps:
1) the following command into terminal: lshal -m lshal.log.txt
2) unplug then plug in the AC adapter
3) attach lshal.log.txt to the bug report. This may be a problem with
HAL/pm-utils.
--
gnome-power-manager doesn't
** Package changed: pm-utils (Ubuntu) = hal (Ubuntu)
--
gnome-power-manager doesn't properly detect power state
https://bugs.launchpad.net/bugs/375260
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
*** This bug is a duplicate of bug 213128 ***
https://bugs.launchpad.net/bugs/213128
** This bug is no longer a duplicate of bug 375260
gnome-power-manager doesn't properly detect power state
** This bug has been marked a duplicate of bug 213128
[Hardy] Guidance-power-manager doesn't
*** This bug is a duplicate of bug 213128 ***
https://bugs.launchpad.net/bugs/213128
Nick, thank you for taking the time to report this bug and helping to
make Ubuntu better. I've found that this problem is in hal, and that
there are many other bugs describing this issue. I'm consolidating
Thanks for the report and the detective work. Does this bug still exist
in Jaunty?
The report demonstrates the power button event and this bug is described
in the description of bug #44058, so I'm marking it confirmed.
The description of bug #44058: When manually choosing for suspend
(through
Thanks for the update.
For troubleshooting hotkeys, see:
https://wiki.ubuntu.com/Hotkeys/Troubleshooting
As a first step, do the following steps:
1) From a terminal, enter:
xev | sed -n 's/^.*state \([0-9].*\), keycode *\([0-9]\+\) *\(.*\), .*$/keycode
\2 = \3, state = \1/p'
2) press the
@Toby: Bug 44058 is about an incorrect reporting of the state of the
lid. This report is about the correct state, it is just not turning on
the standby. Bug 223192 may be a duplicate of this one, however.
@Jeremy: Could you please attach the resulting log files of:
Thanks for checking with 9.04. To investigate further, could you please
attach the resulting log files of:
/usr/share/gnome-power-manager/gnome-power-bugreport gpm.log
gconftool --recursive-list /apps/gnome-power-manager
gpm.gconf.values.txt
and:
1) run: dbus-monitor --session
Thanks for your testing and finding this bug. I can confirm that this
bug exists in Karmic.
Steps to reproduce:
Karmic Live CD (Power Manager Inhibit Applet version 2.27.1)
Add Power Manager Inhibit Applet to the top panel
click on the icon
what happens:
nothing
what should happen:
the icon
Thanks again.
Let's check the bot logs and see if any messages are coming up. To enable boot
logging, follow the instructions at the first post here:
http://ubuntuforums.org/showthread.php?t=49925
Then attach one log after you shutdown with 'shutdown -h now' and one
log with 'shutdown -r now'
** Summary changed:
- inhibit applet not working after upgrade to karmic
+ [karmic] inhibit applet not working
** Description changed:
Binary package hint: gnome-power-manager
- On a Thinkpad T61, after upgrading to Karmic the inhibit applet stopped
- working. The applet icon appears
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we can't fix it because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
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
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
Thanks for your report and helping to make Ubuntu better! Is this
reproducible? If so, how frequently does it happen? Can you describe in
detail the conditions where it does crash and when it doesn't?
** Description changed:
Binary package hint: gnome-power-manager
Gnome-power-manager
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Could you please attach the resulting log file of:
/usr/share/gnome-power-manager/gnome-power-bugreport gpm.log
to the report? You might also want to take a look to the Debugging
instructions located at
Thank you for your bug report. This bug has been reported to the developers of
the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=586908
** Bug watch added: GNOME Bug Tracker #586908
http://bugzilla.gnome.org/show_bug.cgi?id=586908
** Changed in:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we can't fix it because your description
didn't include enough information. You may find it helpful to read How
to report bugs effectively
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd
Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=586943
** Bug watch added: GNOME Bug Tracker #586943
http://bugzilla.gnome.org/show_bug.cgi?id=586943
** Changed in:
The developers at GPM pointed us to this bug report:
http://bugzilla.gnome.org/show_bug.cgi?id=484516
and asked us to try the newest version of GPM and either confirm that
the bug still exists in GPM or if their fix has corrected it. If it
hasn't, we should discuss development of the fix on
Thanks for all the help - I'm sure there are many GNOME and Ubuntu users
who are grateful!
You're right, Ubuntu 9.04 uses GPM 2.24, which included Revision #2551.
http://svn.gnome.org/viewvc/gnome-power-manager/branches/gnome-2-24/src
/gpm-cell-array.c?view=log
Therefore, Ubuntu 2.24 should
Thank you for your bug report. This bug (comments and patch) has been
reported to the developers of the software. You can track it and make
comments at: http://bugzilla.gnome.org/show_bug.cgi?id=568162
It would be best to continue discussions on the patch in GPM over int he
gnome bugzilla.
**
** Changed in: gnome-power-manager (Ubuntu)
Importance: Undecided = Medium
--
gnome-power-manager dies on startup with BadRequest error
https://bugs.launchpad.net/bugs/372468
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Summary changed:
- gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID()
+ gnome-power-manager crashes when gnome-phone-manager is connected to a phone
--
gnome-power-manager crashes when gnome-phone-manager is connected to a phone
https://bugs.launchpad.net/bugs/333910
You
*** This bug is a duplicate of bug 333910 ***
https://bugs.launchpad.net/bugs/333910
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 333910, so it is being marked as such. Please look
Thanks a lot Victor, I sent Fabio an email over at the gnome bug tracker
to revisit the bug and re-open it. I posted your most recent comments as
well. I think we should use their tracker for discussions on the fix
then report back here once done. You can subscribe to the bug at gnome
by adding
Thanks for the comments. We'll need some more information before sending
this upstream. Please try the following:
GNOME Power Manager Verbose Trace (This will turn on verbose debugging
for GNOME Power Manager.)
1) Enter the following into the terminal:
killall gnome-power-manager
Thanks for your report and helping make Ubuntu better! Karmic shifts
away from HAL towards devicekit, so I'm adding that package as a package
it affects.
From DevkitPower.txt:
Device: /org/freedesktop/DeviceKit/Power/devices/battery_BAT0
native-path:
Thanks for your report and help making Ubuntu better.
From the pm-suspend.log, we can see:
/usr/lib/pm-utils/sleep.d/99video resume suspend: Returned exit code 1.
during the resume.
I'm reassigning to pm-utils as GPM was working properly and it appears
that the problem lies in pm-utils 99video
Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=587146
** Bug watch added: GNOME Bug Tracker #587146
http://bugzilla.gnome.org/show_bug.cgi?id=587146
** Changed in:
Thank you for your bug report. This bug has been reported to the
developers of the software. You can track it and make comments at:
http://bugzilla.gnome.org/show_bug.cgi?id=587147
** Bug watch added: GNOME Bug Tracker #587147
http://bugzilla.gnome.org/show_bug.cgi?id=587147
** Changed in:
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
*** This bug is a duplicate of bug 389857 ***
https://bugs.launchpad.net/bugs/389857
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 389857, so it is being marked as such. Please look
From duplicate bug #383637 by Nicolò Chieffo (yelo3).
Binary package hint: gnome-power-manager
ye...@yelo3-laptop:~/bin$ /usr/bin/gnome-power-manager-inhibit test
Traceback (most recent call last):
File /usr/bin/gnome-power-manager-inhibit, line 34, in module
cookie = gpm.Inhibit(Command
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
closing the lid should suspend if and only if no external video is connected
https://bugs.launchpad.net/bugs/243751
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
Idle timeout does not deal with simultanious logins
https://bugs.launchpad.net/bugs/73321
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
display sleep time - why 11 minutes (gnome-power-preferences confusing to the
users)
https://bugs.launchpad.net/bugs/59589
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
missing support for wireless powersave
https://bugs.launchpad.net/bugs/118431
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Triaged
--
Shut Down dialog doesn't open in the foreground
https://bugs.launchpad.net/bugs/279406
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager
Thanks for your report and helping make Ubuntu better. Confirming
because of duplicate.
Possible regression: bug #250649
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Confirmed
** Summary changed:
- power management icon says laptop is connected to power when it isn't
+
*** This bug is a duplicate of bug 393008 ***
https://bugs.launchpad.net/bugs/393008
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 393008, so it is being marked as such. Please look
*** This bug is a duplicate of bug 250649 ***
https://bugs.launchpad.net/bugs/250649
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 250649, so it is being marked as such. Please look
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Confirmed
--
power status mouse-over does not change when power plugged in
https://bugs.launchpad.net/bugs/250649
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
From Bug #386778 reported by Patrick (patrick-voegeli):
Using Karmic, gnome-power-manager doesn't work fine. It won't detect
that the battery is discharging or even running on battery. Also, when
pluging in the AC to charged, it acts flacky.
When running on battery:
atr...@patrick-laptop:~$ acpi
*** This bug is a duplicate of bug 393008 ***
https://bugs.launchpad.net/bugs/393008
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 393008, so it is being marked as such. Please look
** Changed in: gnome-power-manager (Ubuntu)
Status: Confirmed = Invalid
** Changed in: acpi (Ubuntu)
Status: Confirmed = Triaged
--
Random reaction to brightness hotkeys
https://bugs.launchpad.net/bugs/376924
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
This bug report is being closed due to your last comment regarding this
being fixed with an update. Everyone really appreciates your help
testing out Karmic and finding bugs like this one. Please submit any
future bugs you may find.
For future reference you can manage the status of your own bugs
*** This bug is a duplicate of bug 389930 ***
https://bugs.launchpad.net/bugs/389930
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 389930, so it is being marked as such. Please look
Thanks for your detective work, finding the dup and the work around.
I'm not closing this bug and marking as confirmed to point others towards
testing if grub2 fixes their problem:
https://wiki.ubuntu.com/KernelTeam/Grub2Testing
** Summary changed:
- grub menu does not display after cold boot
Sorry for confusion:
I'm not closing this bug BUT instead am marking as confirmed to
encourage others to test if grub2 fixes their bug.
--
grub menu does not display after cold boot on Toshiba laptops
https://bugs.launchpad.net/bugs/389930
You received this bug notification because you are a
*** This bug is a duplicate of bug 389857 ***
https://bugs.launchpad.net/bugs/389857
** This bug has been marked a duplicate of bug 389857
[karmic] inhibit applet not working
** Visibility changed to: Public
--
gnome-power-manager-inhibit crashed with DBusException in call_blocking()
@DervishD: discharge-time-profile tells you the amount of time your
laptop spends with a specific battery percentage during a single
discharge. For example, in your image, your laptop would quickly
discharge from 100 to 90 percent, then slow down from 90-10, then
quickly accelerate from 10-0.
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
Thank you for taking the time to make Ubuntu better. Since what you
submitted is not really a bug, or a problem, but rather an idea to
improve Ubuntu, you are invited to post your idea in Ubuntu Brainstorm
at http://brainstorm.ubuntu.com/ where it can be discussed, voted by the
community and
This bug report is being closed due to your last comment regarding this
being fixed with a configuration change. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line and then choosing a new status in the revealed drop down
box. You
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
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. Gnome-power-manager has many bug
fixes for two-battery systems
Hey bugabundo - just checking up to see if this is still an issue. Have
you tried in Karmic yet?
--
laptop sleep_computer_battery is reached even if using the PC and not on idle
https://bugs.launchpad.net/bugs/284808
You received this bug notification because you are a member of Ubuntu
Desktop
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 - Jaunty Jackalope. It would help us greatly if you
could test with it so we
GPM does give a power history in watts (see attached). You may need to
cycle your battery several times (run it down low off when not plugged
in) before it will show up.
** Changed in: gnome-power-manager (Ubuntu)
Status: Triaged = Invalid
--
request for a power history graph (in watts
** Attachment added: power_history_W.png
http://launchpadlibrarian.net/28564075/power_history_W.png
--
request for a power history graph (in watts versus time)
https://bugs.launchpad.net/bugs/391579
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more
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 - Jaunty Jackalope. It would help us greatly if you
could test with it so we
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
Thanks for trying.
Sorry, the full command is:
/usr/share/gnome-power-manager/gnome-power-bugreport gpm.log
Also check the wiki to attach any other relevant messages come across
the DBus and gnome-power-manager in verbose mode.
--
Can not disable the laptop Lid
Thanks for checking. I'm marking this closed as per your last comment.
Also, see: https://wiki.ubuntu.com/StableReleaseUpdates for
information as to why we debug alpha and beta releases to get bugs
fixed in future versions. The upstream developers of
gnome-power-manager are currently working on
Yes, sorry about that! The autoresponse is still set to Jaunty. Since
the upstream developers are working on version 2.27+ (karmic), and
Ubuntu generally would only fix security flaws in stable releases
(https://wiki.ubuntu.com/StableReleaseUpdates), the best way to get
this fixed would be to
Thank you for taking the time to make Ubuntu better. Since what you submitted
is not really a bug, or a problem, but rather an idea to improve Ubuntu, you
are invited to post your idea in Ubuntu Brainstorm at
http://brainstorm.ubuntu.com/ where it can be discussed, voted by the community
and
** Changed in: gnome-power-manager (Ubuntu)
Status: Incomplete = Invalid
--
a second gnome-power-manager gets launched as root, without reason
https://bugs.launchpad.net/bugs/267109
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
*** This bug is a duplicate of bug 389857 ***
https://bugs.launchpad.net/bugs/389857
testing LP email interface
status invalid
--
gnome-power-manager-inhibit crashed with DBusException in call_blocking()
https://bugs.launchpad.net/bugs/393707
You received this bug notification because you
*** This bug is a duplicate of bug 389857 ***
https://bugs.launchpad.net/bugs/389857
more testing
status invalid
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Invalid
--
gnome-power-manager-inhibit crashed with DBusException in call_blocking()
This bug report is being closed due to your last comment regarding this
being fixed. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug
Sorry about that, thanks for reopening this bug and testing this in
Karmic.
You probably have already seen:
http://projects.gnome.org/gnome-power-manager/bugs.html
and
https://wiki.ubuntu.com/DebuggingGNOMEPowerManager
Those links have some helpful tips for debugging GPM. In your case,
Discussion of a similar bug in Karmic is going on here: bug #385633
--
DPMS is broken
https://bugs.launchpad.net/bugs/193192
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
Discussion of a similar bug in Karmic is going on here: bug #385633
--
display doesn't go to DPMS sleep
https://bugs.launchpad.net/bugs/203513
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
some other bugs with similar symptoms:
bug #231397
bug #193192
in addition to the reporter's comment about bug #203513
from bug #231397 (this may or may not help):
Tony Houghton (h-realh: 0) wrote on 2008-10-14: (permalink)
I've discovered that this behaviour is deliberate and
Thanks for checking. I think we can list this as an unknown fix for now, but
if it comes back use:
ubuntu-bug gnome-power-manager
to have apport put together the report (since upstream would want to see bugs
with DeviceKit and GPM 2.27).
** Changed in: gnome-power-manager (Ubuntu)
Thanks for you report and helping make Ubuntu better. Has this crash
repeated since your original report? Thanks.
** Changed in: gnome-power-manager (Ubuntu)
Status: New = Incomplete
--
gnome-power-manager crashed on removing the battery
https://bugs.launchpad.net/bugs/394700
You
Thanks for the debugging work. We have a some more things to do to work
on your bug:
A) For all the following debugging use Karmic Koala only (liveCD or
development installation). The upstream developers are currently working
on that version of GPM, and it is the best way we can get the bug fixed
1 - 100 of 586 matches
Mail list logo
