Gnome-power-manager update causes backlight to power off frequently

After the upgrade to gnome-power-manager 2.26.1-1 today, my laptop screen backlight is being powered off constantly, after only about 1 minute. It's not the screen blanking, but the backlight going off. It comes right back up if I do anything on the keyboard.
My power management preferences haven't changed though. They're all set (as before the upgrade) to never dim the display and never put the display to sleep. So why is the backlight going off anyway?
Also, this pretty distinctly seems to have to do with Gnome and not X. If I leave the laptop for an extended period at the GDM login screen, the backlight is never powered off. The problem only develops after I have logged into Gnome.
Thanks for any help.
Last edited by cb474 (2009-04-23 07:14:55)

Thanks, I looked for bugs on this, but didn't find that one on the backlight for some reason. I was about to issue my own bug report. Anyway, so I added my comments to the bug report, but it has been marked "fixed" already (because it was really addressing a slightly different issue with DPMS), so I don't know if I need to start a new bug report or not. I'll wait and see what kind of reply I get. (In fact, it seems like the fix to the problem in the backlight bug report may have caused the problem addressed in this thread.)
That said, I found a work around, if you want to completely disable the backlight ever going off. You can issue the command:
xset -dpms
This disables entirely the display power management system (which I'm guessing gnome-power-manager operates as a frontend for). Of course, if you want your screen to be put to sleep after some set point of time this won't work. But you may be able to configure this directly with other xset commands or in xorg.conf (see links below).
To disable dpms at startup. I found oddly that it didn't work to add it to my .xinitrc. So instead I went to System > Preferences > Startup Applications. Added an a program in the "Startup Programs" tab, named it "DPMS (disable)" and for the command put:
xset -dpms
This is working.
You can also configue DPMS in xorg.conf, but I'm not using xorg.conf so I didn't fiddle with it. See: http://wiki.archlinux.org/index.php/DPMS and http://www.shallowsky.com/linux/x-screen-blanking.html.
Hope that helps.
Last edited by cb474 (2009-04-24 08:26:23)

Similar Messages

  • GNOME 3.10 update caused GUI artifacts

    Ever since the Gnome 3.10 update I've been getting weird artifacts in the windows bar when accessing certain settings/apps. Such as going into network manager settings and opening up Evolution mail client. There are these random black bars and artifacts.
    Evolution Mail Client Screenshot:
    Network Manager Screenshot:
    Last edited by mrhpeng (2013-10-16 05:26:59)

    trunneml wrote:
    Hi,
    I reinstalled gnome3, gtk3, radeon and libtxc_dxtn and the worst issues are gone. May be you can try:
    pacman -S gnome
    pacman -S gtk3
    pacman -S libtxc_dxtn
    Thank you! Your solution improved the problem a bit. There is still minor artifacts, however it is much more bearable now! Lets hope Gnome fixes this bug soon.

  • Gnome Power Off menu not triggering any action

    After a couple of hibernation / restoration processes the Power Off menu suddenly starts to no longer work correctly.
    Regardless which of the options I choose, be it Suspend / Hibernate / Shutdown, no action is executed.
    Sometimes this problem occurs after 2 hibernation restores, sometimes after 3 etc. I cannot really trigger down the problem. The logs do not show any error.
    Does someone notice the same effect?

    gnome 3.8 can use gdm(screen saver is integrated into it) or xscreensaver. You will need either one of them.

  • Iphone slide to power off frequently

    Hi every one.
    my iphone keep prompting slide to power off automatically and the power off button also not working . is anyone facing same issues . is there anyway to get rid of this issues

    Strangely, I have the exact same problem, it started yesterday too. I've reinstalled the firmware and it was doing the same thing before I even restored from backup.
    No warranty and not even an Apple Service Centre here

  • [SOLVED] gnome-power-manager issues since update?

    Since maybe an update (I'm not sure), gnome-power-manager isn't launched anymore. No battery applet, suspend and hibernation buttons.
    acpid, pm-utils are on.
    By launching it in terminal, it gives:
    ~$ gnome-power-manager
    (gnome-power-manager:3238): libupower-glib-WARNING **: Couldn't enumerate devices: Launch helper exited with unknown return code 127
    TI:17:42:09 TH:0x10cf090 FI:gpm-engine.c FN:gpm_engine_coldplug_idle_cb,834
    - failed to get device list: Launch helper exited with unknown return code 127
    Traceback:
    gnome-power-manager() [0x419a64]
    gnome-power-manager() [0x41904e]
    /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1f3) [0x7f72b683abf3]
    /usr/lib/libglib-2.0.so.0(+0x423d0) [0x7f72b683b3d0]
    /usr/lib/libglib-2.0.so.0(g_main_loop_run+0x182) [0x7f72b683ba42]
    gnome-power-manager() [0x40f11b]
    /lib/libc.so.6(__libc_start_main+0xfd) [0x7f72b6239c3d]
    gnome-power-manager() [0x407a49]
    So would libupower-glib bug?
    Last edited by feNNec (2011-01-16 19:03:59)

    yes there is:
    $ ./upowerd start
    ./upowerd: error while loading shared libraries: libusb-1.0.so.0: cannot open shared object file: No such file or directory
    libusb-1.0.8-1 is installed
    What's this daemon for?

  • 4313CTO Power Manager update problem ** Ignore **

    T510, Win 7 32, all updates up to date.
    Just installed  BIOS 1.43-1.19 / Power Manager 3.48.  I am now unable to configure the Power Button.
    Sorry everyone ;-) I didn't check the Global Settings !!!!!
    Seems OK now.
    Thanks, Bob

    Thanks, I looked for bugs on this, but didn't find that one on the backlight for some reason. I was about to issue my own bug report. Anyway, so I added my comments to the bug report, but it has been marked "fixed" already (because it was really addressing a slightly different issue with DPMS), so I don't know if I need to start a new bug report or not. I'll wait and see what kind of reply I get. (In fact, it seems like the fix to the problem in the backlight bug report may have caused the problem addressed in this thread.)
    That said, I found a work around, if you want to completely disable the backlight ever going off. You can issue the command:
    xset -dpms
    This disables entirely the display power management system (which I'm guessing gnome-power-manager operates as a frontend for). Of course, if you want your screen to be put to sleep after some set point of time this won't work. But you may be able to configure this directly with other xset commands or in xorg.conf (see links below).
    To disable dpms at startup. I found oddly that it didn't work to add it to my .xinitrc. So instead I went to System > Preferences > Startup Applications. Added an a program in the "Startup Programs" tab, named it "DPMS (disable)" and for the command put:
    xset -dpms
    This is working.
    You can also configue DPMS in xorg.conf, but I'm not using xorg.conf so I didn't fiddle with it. See: http://wiki.archlinux.org/index.php/DPMS and http://www.shallowsky.com/linux/x-screen-blanking.html.
    Hope that helps.
    Last edited by cb474 (2009-04-24 08:26:23)

  • Udev and gnome-power-manager

    Hi,
    Recently I upgrade the udev from 141-5-i686 to 145-1-i686 in my MSI wind. Then the following problem begins:
    When the system boots this characters can be seen in the screen just before udev is finished: ^@^@
    I can add more characters during the whole boot process if I press Fn+F5 (the brightness hotkey).
    When gnome is running, in few minutes the screen change the brightness very fast, like blinking. This problem only happens if the gnome-power-manager is enabled.
    Downgrading udev fix the problem.
    Does anyone know if this is something related with this particular version of udev, or can I do something to fix it?
    I don't know if the following messages will help, because them can be seen with the current and with the old udev version. But they are the only ones that I think are related with hotkeys amb modules loading. So I post them just in case.
    messages.log:
    Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
    Aug 29 14:57:02 peremsi load-modules.sh: 'dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd06/26/2008:svnMICRO-STARINTERNATIONALCO.,LTD
    :pnU-100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU-100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvrVer.001:' is
    not a valid module or alias name
    Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d000027A6sv00001462sd00000110bc03sc80i00' is not a valid module or alias
    name
    Aug 29 14:57:02 peremsi load-modules.sh: 'platform:vesafb' is not a valid module or alias name
    Aug 29 14:57:02 peremsi load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias
    name
    Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
    Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
    Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
    Aug 29 14:57:02 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0103:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0303:PNP030B:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'acpi:PNP0F03:PNP0F13:' is not a valid module or alias name
    Aug 29 14:57:03 peremsi load-modules.sh: 'usb:v0C45p62C0d0100dcEFdsc02dp01ic0Eisc02ip00' is not a valid module or alias name
    Aug 29 14:57:08 peremsi ntfs-3g[2611]: Version 2009.4.4 integrated FUSE 27
    (so many times) This message is because the kernel do not map some hotkeys. Gnome do it.
    atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0).
    atkbd.c: Use 'setkeycodes e077 <keycode>' to make it known.
    atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0).
    atkbd.c: Use 'setkeycodes e078 <keycode>' to make it known.

    recently, I updated system, and now I have same problem like you had. I was not sure, what could cause this brightness fast changing. I thought about hal, dbus, udev. Never tried to downgrade udev. Now, I have udev 146. I am not sure what version I had before system upgrading.
    Now, I have kernel 2.6.31, and I am not sure if udev 141 will work with this kernel...
    I have MSI WIND, also...
    Last edited by kunalagon (2010-01-08 11:15:54)

  • SOLVE strange problem with suspend and resume with gnome-power-manager

    I have pm-utils and gnome installed.
    Suspending and hibernation works well from the command line ($ pm-hibernate and $ pm-suspend).  Resuming works without any problems.
    Suspending from gnome "Shutdown dialog" works perfectly as well.
    However, if suspending is initiated by gnome-power-manager something strange happens:  After pressing the power button resuming switches to hibernation and my laptop turns off.  Resuming from disk works fine again.
    Now, suspending works fine again if I change and save any config file in /etc/pm/.
    Here comes the strange thing:  It doesn't really matter what I change as long as I save it.
    However, as soon as I reboot resuming fails again the way I described above.
    Anyone have a clue what's going on?
    I get no error messages and I've tried all sorts of boot entries.
    Last edited by mehldutt (2007-12-26 19:42:31)

    After some try and error my guess is that "HAL" is responsible for this problem:
    I deinstalled ACPID and 'pm-utils' and switched to 'uswsusp'.
    I made the appropriate changes to the appropriate hal-scrips
    usr/lib/hal/scripts/hal-system-power-suspend:
    #!/bin/sh
    /sbin/s2ram --force
    usr/lib/hal/scripts/hal-system-power-hibernate:
    #!/bin/sh
    /sbin/s2disk
    After these changes I still have the same problem:  immidiatly after resuming form suspend (via power-button) my laptop hibernates (s2disk).
    However, if I delete all entries in "usr/lib/hal/scripts/hal-system-power-hibernate" resuming from suspend works fine again, but hibernate doesn't of course.  So, some script must be calling "usr/lib/hal/scripts/hal-system-power-hibernate" emmediatly after resuming from suspend.
    A couple of weeks ago everything worked fine.  My guess is that one of the recent hal-updates is causing this.
    How can I figure what script is calling "usr/lib/hal/scripts/hal-system-power-hibernate" after resuming from suspend?

  • Gnome power manager upgrade - nvidia sedmentation error

    I am trying to use the rolling update model properly and check the web page for issues before doing my pacman Syu.
    I updated gnome-power-manager (along with the other available updates) today amd immediately noticed different behaviour. 
    The laptop (Dell Inspiron 1720) no longer suspended when I shut the lid.  I still had the shutdown menu option but... when I used it it intermittently caused segmentation fault errors in nvidia settings and stuff like Google Earth no longer worked.  My graphics card is geForce 8600M GT. 
    Downgrading the gnome-power-manager package restored everything to working order.
    Maybe I did something daft, but I'd like to know if there is something else I should have checked or if there is a problem with this package.  In the meantime I've added it to IgnorePkg

    i just pointing out that you can try to fix it yourself(until is fixed in our repo) by compiling gnome-power-manager using abs and add that option to the ./configure within PKGBUILD.
    Last edited by wonder (2009-04-14 20:26:39)

  • Gnome Power Manager Applet

    Hi all,
    since the last update, the gnome power manager applet is gone. I can change the preferences with the gnome-power-preferences tool, but the applet in the system bar is gone... Any idea?
    Acker

    Master One wrote:
    So what's going on?
    I do not assume, that users of other distros have such problems, at least in Foresight Linux the applet is working as supposed to, which confirms that it's not an upstream problem. There is a bug open, but no info about any progress.
    Is anybody working on a fix?
    Jan de Groot has been assigned to this task a few days ago. Jan works on 580 open tasks, most of which have a higher priority then this bug.
    As seen from the screenshot threads, quite some Arch users are on Gnome, so that's surely not something just a minority is in need of.
    What's with the Gnome 2.18.1 updates (though the working version of the Gnome Power Manager in Foresight Linux is 2.18.2 as well)?
    Oh my, an icon is not shown, man the life boats. The gnome-power-manager works perfectly -- at least for me -- it just doesn't show an icon in the notification area. If you absolutely need the icon, deploy Iloeki's script. It should do the job.

  • [Solved] Systemd - Overrides settings of Gnome-Power-Manager?

    Hello!
    I've always used the following to lines to tell Gnome-Power-Manager not to suspend my laptop, when the lid is closed:
    org.gnome.settings-daemon.plugins.power lid-close-ac-action 'blank'
    org.gnome.settings-daemon.plugins.power lid-close-battery-action 'blank'
    I remember a huge (and regular...) discussion around Gnome 3, because the developers resisted to re-implemented a button for this in the UI of Gnome3. Well, the two lines above done their job all the time. Since the last update of Systemd this seems to be ignored:
    Oct 09 01:19:58 cupcake systemd-logind[273]: Lid closed.
    Oct 09 01:19:58 cupcake systemd-logind[273]: Suspending...
    Oct 09 01:19:58 cupcake systemd[1]: Starting Sleep.
    Oct 09 01:19:58 cupcake systemd[1]: Reached target Sleep.
    Oct 09 01:19:58 cupcake systemd[1]: Starting Suspend...
    Is anyone other affected? Looks like a real problem for me. If I close the lid I want to close my lid, nothing more an especially not suspend
    /var/log/pacman.log
    [2012-10-08 21:59] upgraded systemd (193-1 -> 194-1)
    [2012-10-08 21:59] upgraded systemd-sysvcompat (193-1 -> 194-1)
    Last edited by hoschi (2012-10-08 23:53:06)

    pablox wrote:
    hoschi wrote:
    Nope. Found it five minutes ago. My shame! Thank you
    https://wiki.archlinux.org/index.php/Sy … th_systemd
    This is driving me crazy. I've read the article, but I still don't understand what I'm supposed to do. I have tried changing values from logind.conf *IgnoreInhibited to yes to no, but the laptop still suspend when the lid is closed .
    All you need to do is set HandleLidSwitch=ignore in logind.conf, this will make systemd ignore the lid switch completely, and leave gnome to handle it. Its pretty self explanatory... You can also set the other similar options to ignore, like HandlePowerKey, HandleSuspendKey, HandleHibernateKey if you want only gnome to handle them.
    Last edited by bwat47 (2012-10-10 22:02:54)

  • AUR eee-control/gnome-power-manager

    I updated my system, and seem to have a minor issue between gnome-power-manager 2.30 and eee-control-tray 9.4 (from the AUR, this might be the wrong section).  The tray tool functions normally, except for the automatic FSB scaling with the new gnome-power-manager applet:  When I launch eee-control-tray from the command line, I get an output of "FSB scaling not available.  Is gnome-power-manager running?"  I was wondering if anybody else has encountered this so far, and if it can be fixed.
    Last edited by arinlares (2010-04-22 23:38:07)

    Hello combuster!
    gpm 2.26.3 ?
    Is it just a misstyping ?

  • [SOLVED] GNOME Power Manager Icon

    Hello,
    With the recent influx of GNOME 2.22 packages, gnome-power-manager has begun to behave strangely on my system.
    In gnome-power-preferences, I have specified that the notification area icon should only be displayed when my laptop battery is charging or discharging. Since I upgraded my GNOME packages, the icon has always appeared in my notication area upon login -- even if I am running on AC power. In that situation, the tooltip for the icon reads as follows:
    Computer is running on AC power
    Laptop batteries discharging (100%)
    Battery discharge time is currently unknown
    If I unplug the power cord from my computer,  the icon (strangely) disappears. If I then proceed to plug the cord back in, the icon will appear briefly (I assume to indicate that what little power was drained from the battery is being replenished) and then disappear once more.
    This problem is occurring on a Dell Inspiron 6400 (E1505). I feel that I might need to report this issue as a bug, but I'd first like to know if anyone else has noticed this oddity since the upgrade.
    Thanks!
    Edit:
    It seems as if gnome-power-manager thinks that I have two laptop batteries (though I have only one). Clicking on the notification icon lists two batteries: one with the usual "on AC power" icon and the other with the "discharging" (standard battery) icon.
    I do not think that there are any problems with ACPI: running acpi yields the following:
    Battery 1: charged, 100%
    I'm not quite sure where gnome-power-manager procures its information about the batteries)....
    Last edited by ssjlegendx (2008-04-20 18:34:53)

    I just updated to HAL 0.5.11rc2-2, and it seems that my problem has been solved!
    I didn't see the related bug report before starting this thread.... Thanks, JGC!
    Last edited by ssjlegendx (2008-08-02 20:44:41)

  • Gnome-power-manager no icon is being displayed

    Hi.
    I've recently upgraded to Gnome 2.18 from testing and noticed that gnome-power-manager does not display icon for my battery. I've chcecked options and everything seems to be fine. The process itself is also running. After couple of tests I've managed to show icon (killed process and re-run it with --no-daemon option) but after restart the icon was missing. Lshal shows my battery withouth any problem. Does anyone have similar problem??? My system is up-to-date, updated everyday.

    In this thread: http://bbs.archlinux.org/viewtopic.php?id=31193
    JGC wrote:The gnome-power-manager thing is something that appeared after switching to the GtkStatusIcon API. This bug appears because gnome-power-manager starts before the notification area is placed on the panel.
    This problem has been picked up already, so perhaps something's already being done before 2.18 goes to the extra repository.

  • Gnome-power-manager not recognizing battery

    Gnome-power-manager seems to act as if I have no battery whatsoever, and, when I am on battery power, keeps saying that I am running on AC power, despite the fact that both typing "acpi" into a terminal and the battery monitor applet give the correct state. I do have the dbus and acpid daemons running (they're in my rc.conf), and my laptop is an Acer Aspire 3618AWLCI.
    Does anyone know what I could do? I would much rather use gnome-power manager than the batter monitor applet.

    I realized that my problem since the update is that hald crashes after the session is launched. noamsml, did you check that hald is running on your laptop ?
    Last edited by vlaaad (2007-02-05 14:17:04)

Maybe you are looking for