After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 571807 - backlight on screen oscillates
backlight on screen oscillates
Status: RESOLVED DUPLICATE of bug 566095
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.24.x
Other All
: Normal major
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-02-15 07:28 UTC by James Strother
Modified: 2009-02-16 05:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Attachments
Output of gnome-power-bugreport.sh (2.51 KB, text/plain)
2009-02-15 07:29 UTC, James Strother
Details
Output from gconftool-2 --recursive-list /apps/gnome-power-manager (2.21 KB, text/plain)
2009-02-15 07:30 UTC, James Strother
Details
Log from running gnome-power-manager --verbose --nodaemon (49.19 KB, text/plain)
2009-02-15 07:31 UTC, James Strother
Details
Output from xbacklight (8.15 KB, text/plain)
2009-02-15 07:33 UTC, James Strother
Details

Description James Strother 2009-02-15 07:28:49 UTC
Please describe the problem:
When the system is running off of battery power the screen brightness oscillates randomly over a period of a couple of minutes.  It seems as though gpm detects that the system is idle and then turns down the screen backlight, very very very slowly. After it brings the screen brightness down, it then detects that the system is not so idle and then brings the brightness back up, very very very slowly.  There are two problems with this.  The first is that the system is not idle, this happens even when I am actively typing or using the mouse.  The second is, of course, the speed at which the backlight is adjusted.  Related bugs appear to be bug 566095 and bug 555526.  Though I've filed a new report as the symptoms are not identicaly (this does not happen when I set the backlight and my system never becomes unresponsive).

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?
Yes.

Other information:
Comment 1 James Strother 2009-02-15 07:29:44 UTC
Created attachment 128758 [details]
Output of gnome-power-bugreport.sh
Comment 2 James Strother 2009-02-15 07:30:53 UTC
Created attachment 128759 [details]
Output from gconftool-2 --recursive-list /apps/gnome-power-manager
Comment 3 James Strother 2009-02-15 07:31:54 UTC
Created attachment 128761 [details]
Log from running gnome-power-manager --verbose --nodaemon

The laptop is unplugged around 9:03 and the backlight begins to oscillate around 9:05.
Comment 4 James Strother 2009-02-15 07:33:58 UTC
Created attachment 128762 [details]
Output from xbacklight

This is the output from xbacklight just to demonstrate that change in the backlight brightness is real and to show the duration over which the transition occurs.  This was recorded at the same time as the gpm log was recorded so the timestamps should match up.
Comment 5 James Strother 2009-02-15 07:38:06 UTC
Finally, I just looked at the output from the bugreport too and it does not seem to be able to locate information on the hardware so I thought I would provide that as well.  It is an IBM ThinkPad X40.  Here is the output from uname -a

Linux elysium 2.6.28-ARCH #1 SMP PREEMPT Sun Feb 8 10:13:45 UTC 2009 i686 Intel(R) Pentium(R) M processor 1200MHz GenuineIntel GNU/Linux

It is running Arch linux, and was fully patched as of yesterday.
Comment 6 Richard Hughes 2009-02-15 09:24:23 UTC
Your version is very old. gnome-power-manager-2.24.4 should fix things for you.
Comment 7 James Strother 2009-02-16 05:08:39 UTC
Well, my version isn't that old, it looks like it was released just a couple of months ago.  At any rate, I downloaded and built 2.24.4 and can verify that this fixes the problem.  I'm marking this bug as a duplicate of bug 566095 (Richard, thanks for getting that fixed).

*** This bug has been marked as a duplicate of 566095 ***