GNOME Bugzilla – Bug 509211
On battery, dim accourse even though activly using the computer
Last modified: 2009-03-04 14:49:41 UTC
Please describe the problem: The program does not seem to listen to changes of inactivity when on battry. Even though I select not to dim or dim to 100% it always goes down to zero after a few seconds. Steps to reproduce: 1. Remove power adapter 2. Change settings 3. Watch the miracles happen Actual results: It falls into inactivity and ignores the settings, ie. resets the light to about 0. Expected results: The desktop to stay light up. Does this happen every time? Yes. Other information:
Do you have gnome-screensaver installed and working?
Yes I have.
I find that the screen dims the backlight while I am using it (the screensaver works fine) but I can't isolate the issues enough to report it in a bug.
Hello, 1) I hate all these brightness related bugs, especially since they represent a regression. 2) There are several bugs that overlap(#478128, #483134, #483143, #509211) ; IMHO, there should be ONLY ONE I have reported this in Debian bug #467264 and I explained why the current (and former) behaviour is(was) wrong and how they should actually behave. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467264 To summarize: - AC and battery settings MUST not interact with each other - the battery *brightness*slider* should be *brought*back* (one should be able to set the default battery brightness level, no matter what automatic dimming effect is added) - dimming on idle should *really*dim*or*do*nothing*, if dimming is not possible; is should NEVER bright up the display - using the *brightness* *keys* should be a clear adjustment of the default brightness level and it should *always* have precedence over anything automatically computed or commanded - DO NOT DIM WHILE ACTIVE If anyone cares, here is the summary I made in the debian bug report: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467264#33
Sorry, the entire list of bug was: bug #478128, bug #483134, bug #483143, bug #509211, bug #530346, bug #335673 and bug #483144
Tim, does this still happen when using gnome-power-manager from svn? Thanks.
Tried to build the latest SVN first with prevu on Ubuntu Hardy 8.04: [ if [ -e ./configure.ac ] || [ -e ./configure.in ]; then cd . && `which autoconf"yes" || which autoconf`; fi configure.ac:5: error: possibly undefined macro: AM_INIT_AUTOMAKE If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:6: error: possibly undefined macro: AM_CONFIG_HEADER configure.ac:10: error: possibly undefined macro: AM_PROG_LIBTOOL configure.ac:45: error: possibly undefined macro: AM_GLIB_GNU_GETTEXT configure.ac:134: error: possibly undefined macro: AM_GCONF_SOURCE_2 configure.ac:206: error: possibly undefined macro: AM_CONDITIONAL make: *** [debian/stamp-autotools-files] Error 1 ] After that I tried to build according to: http://www.gnome.org/projects/gnome-power-manager/packages.html And I got: [ $ ./autogen.sh --prefix=/home/hughsie/root --enable-applets --with-gconf-source=xml::/home/hughsie/.gconf /usr/bin/gnome-autogen.sh checking for autoconf >= 2.53... testing autoconf2.50... not found. testing autoconf... found 2.61 checking for automake >= 1.7... testing automake-1.10... found 1.10.1 checking for libtool >= 1.5... testing libtoolize... found 1.5.26 checking for glib-gettext >= 2.2.0... testing glib-gettextize... found 2.16.3 checking for intltool >= 0.30... testing intltoolize... found 0.37.1 checking for pkg-config >= 0.14.0... testing pkg-config... found 0.22 checking for gnome-doc-utils >= 0.4.2... testing gnome-doc-prepare... found 0.12.2 checking for gnome-common >= 2.3.0... testing gnome-doc-common... found 2.20.0 Checking for required M4 macros... Checking for forbidden M4 macros... Processing ./configure.ac Running libtoolize... You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. Running glib-gettextize... Ignore non-fatal messages. Copying file mkinstalldirs Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running intltoolize... Running gnome-doc-common... Running gnome-doc-prepare... You should add the contents of '/usr/share/aclocal/gnome-doc-utils.m4' to 'aclocal.m4'. Running aclocal-1.10... configure.ac:333: warning: underquoted definition of AC_CHECK_X_HEADER configure.ac:333: run info '(automake)Extending aclocal' configure.ac:333: or see http://sources.redhat.com/automake/automake.html#Extending-aclocal configure.ac:134: warning: macro `AM_GCONF_SOURCE_2' not found in library Running autoconf... configure.ac:134: error: possibly undefined macro: AM_GCONF_SOURCE_2 If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. ] Is the fix included in the package 2.23.1 which was built on the 16th (I think)?
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.