Where has gnome-power-manager gone?

I'm using Xmonad (without Gnome) and installed gnome-power-manager to manage the battery on my laptop. I can't find the binary:
[me@laptop ~]$ pacman -Ss gnome-power-manager
extra/gnome-power-manager 3.2.0-1 (gnome-extra) [installed]
Power management tools.
[me@laptop ~]$ gnome-<tab>
gnome-autogen.sh gnome-power-statistics
gnome-doc-common
[me@laptop ~]$ which gnome-power-manager
which: no gnome-power-manager in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/core_perl)
Perhaps there were some wild and crazy changes due to Gnome 3? How do I find/use this thing?
EDIT: After looking at "Package Contents" list on the package page:
http://www.archlinux.org/packages/extra … r-manager/
it appears gnome-power-manager is not installed, just gnome-power-statistics. How can this be? They are not the same thing AFAICT.
Last edited by oops (2011-10-11 22:44:35)

pacman -Ql gnome-power-manager
will show you all the files within that package.
pacman -Ql gnome-power-manager | grep /bin/
should find some binaries.
https://wiki.archlinux.org/index.php/FA … tart_it.3F
Seems there's only /usr/bin/gnome-power-statistics.
Last edited by karol (2011-10-11 22:45:26)

Similar Messages

  • Changing brightness in gnome-power-manager has no effect

    Well it's mostly all in the title. When I change the brightness slider in gnome-power-manager it has no affect on brightness. However the fn key combo for changing the brightness does have change the brightness yet it brings up the volume like dialog for brightness yet no change is registered on the slider (despite brightness increasing). This erratic behavior is not seen in Fedora or Ubuntu so I know it can be made to work. I have a Dell Inspiron 640m.

    thunderogg wrote:Maybe a stupid question: Are you a member of the power group? I had a similar problem when I forgot to add my user to the power group.
    I am now. But it hasn't fixed anything. I restarted X after adding my user to the group.
    However when I started gnome-power-manager as root.  It wouldn't let me access the preference dialog BUT when I increased or decreased the brightness it showed me the proper progressbar indicator. I will restart and see what happens.
    edit:
    After a restart all is working well as far as I can tell. Thank you very much for all your help. It seems it was in fact an issue with the groups.
    Last edited by ihavenoname (2008-09-09 05:26:13)

  • 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] 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 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)

  • Gnome-power-manager with networkmanager_sleep option

    I have a wireless device using the ipw2200 module. I have always found it extremely annoying that gnome-power-manager asks NetworkManager to sleep before suspending, since, first of all, the ipw2200 module doesn't need to be unloaded and, secondly, because I always have to wait the extra few seconds it takes for NM to send the dhcp request after resuming. I made a patch that adds an option to turn the NM-sleep call on or off via a gconf entry (networkmanager_sleep). The patch has been accepted upstream and included in CVS. However, I've made a patch that applies cleanly to gnome-power-manager 2.16.1 as well. Here it is:
    diff -Naur gnome-power-manager-2.16.1/data/gnome-power-manager.schemas.in gnome-power-manager-2.16.1-new/data/gnome-power-manager.schemas.in
    --- gnome-power-manager-2.16.1/data/gnome-power-manager.schemas.in 2006-07-30 14:51:52.000000000 +0200
    +++ gnome-power-manager-2.16.1-new/data/gnome-power-manager.schemas.in 2006-10-05 11:56:10.000000000 +0200
    @@ -571,6 +571,17 @@
    <long>This is the laptop panel screen brightness used when the session is idle. Only valid when use_time_for_policy is true.</long>
    </locale>
    </schema>
    + <schema>
    + <key>/schemas/apps/gnome-power-manager/networkmanager_sleep</key>
    + <applyto>/apps/gnome-power-manager/networkmanager_sleep</applyto>
    + <owner>gnome-power-manager</owner>
    + <type>bool</type>
    + <default>true</default>
    + <locale>
    + <short>If Networkmanager should disconnect.</short>
    + <long>Chooses whether Networkmanager should disconnect from the network before suspending.</long>
    + </locale>
    + </schema>
    </schemalist>
    </gconfschemafile>
    diff -Naur gnome-power-manager-2.16.1/src/gpm-manager.c gnome-power-manager-2.16.1-new/src/gpm-manager.c
    --- gnome-power-manager-2.16.1/src/gpm-manager.c 2006-09-17 22:33:51.000000000 +0200
    +++ gnome-power-manager-2.16.1-new/src/gpm-manager.c 2006-10-05 12:03:22.000000000 +0200
    @@ -1172,6 +1172,7 @@
    gboolean allowed;
    gboolean ret;
    gboolean do_lock;
    + gboolean nm_sleep;
    gpm_manager_allowed_hibernate (manager, &allowed, NULL);
    @@ -1190,7 +1191,12 @@
    gpm_screensaver_lock (manager->priv->screensaver);
    - gpm_networkmanager_sleep ();
    + nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
    + GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
    + if (nm_sleep) {
    + gpm_networkmanager_sleep ();
    + }
    +
    ret = gpm_hal_hibernate (manager->priv->hal);
    manager_explain_reason (manager, GPM_GRAPH_EVENT_RESUME,
    @@ -1230,7 +1236,12 @@
    if (do_lock) {
    gpm_screensaver_poke (manager->priv->screensaver);
    - gpm_networkmanager_wake ();
    + nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
    + GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
    + if (nm_sleep) {
    + gpm_networkmanager_wake ();
    + }
    +
    sync_dpms_policy (manager);
    @@ -1257,6 +1268,7 @@
    gboolean allowed;
    gboolean ret;
    gboolean do_lock;
    + gboolean nm_sleep;
    GpmPowerStatus status;
    char *message;
    int charge_before_suspend;
    @@ -1279,7 +1291,12 @@
    gpm_screensaver_lock (manager->priv->screensaver);
    - gpm_networkmanager_sleep ();
    + nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
    + GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
    + if (nm_sleep) {
    + gpm_networkmanager_sleep ();
    + }
    +
    /* We save the current charge in mWh so we can see how much power we
    lost or gained over the suspend cycle */
    @@ -1348,7 +1365,12 @@
    if (do_lock) {
    gpm_screensaver_poke (manager->priv->screensaver);
    - gpm_networkmanager_wake ();
    + nm_sleep = gconf_client_get_bool (manager->priv->gconf_client,
    + GPM_PREF_NETWORKMANAGER_SLEEP, NULL);
    + if (nm_sleep) {
    + gpm_networkmanager_wake ();
    + }
    +
    sync_dpms_policy (manager);
    diff -Naur gnome-power-manager-2.16.1/src/gpm-prefs.h gnome-power-manager-2.16.1-new/src/gpm-prefs.h
    --- gnome-power-manager-2.16.1/src/gpm-prefs.h 2006-07-30 14:51:54.000000000 +0200
    +++ gnome-power-manager-2.16.1-new/src/gpm-prefs.h 2006-10-05 12:05:15.000000000 +0200
    @@ -55,6 +55,9 @@
    #define GPM_PREF_CAN_HIBERNATE GPM_PREF_DIR "/can_hibernate"
    #define GPM_PREF_LOCK_USE_SCREENSAVER GPM_PREF_DIR "/lock_use_screensaver_settings"
    +
    +#define GPM_PREF_NETWORKMANAGER_SLEEP GPM_PREF_DIR "/networkmanager_sleep"
    +
    /* These are only effective if the system default is turned off. See bug #331164 */
    #define GPM_PREF_LOCK_ON_BLANK_SCREEN GPM_PREF_DIR "/lock_on_blank_screen"
    #define GPM_PREF_LOCK_ON_SUSPEND GPM_PREF_DIR "/lock_on_suspend"
    It would be great if this could be added to the official package, but I'm not expecting it

    Have a look in gconf-editor to see if there's a setting for that? (I can't check now, I'm using XFCE.) Also, check that you didn't keep the default "put computer to sleep when the lid is closed", but I suppose you've done it already...

  • APC UPS & gnome-power-manager

    Hi there,
    I am running gnome-power-manager on a system which is connected to an APC Back-UPS CS 500. It appears gnome-power-manager fails to recognize the UPS, however. In the preferences window, I only have an "On AC Power" and a "General" tab. AFAIK there ought to be an "On UPS Power" tab as well.
    The UPS is connected correctly, as I can query it via apcaccess.
    Any hints?
    Edit: Just found http://bbs.archlinux.org/viewtopic.php?id=75730
    Gonna see if this fixes it.
    Last edited by Edmond (2009-07-13 21:44:53)

    pyther wrote:Does this post resolve the issue? http://bbs.archlinux.org/viewtopic.php? … 86#p583386
    Nope. As I said before:
    Edmond wrote:I compiled devicekit-power 009 and then recompiled gnome-power-manager. No visible change.

  • 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 ignores dpms_method_ac

    There's no way (it seems ) to make gnome-power-manager 2.26.3-1 to work fine...
    i'd like to put my monitor in standby after a while instead of simply blank and so i set dpms_method_ac  in gconf accordingly... but with no success...
    i don't know where to find a solution...
    my laptop is a HP pavillion dv5 1210el and thisi is my actual xorg.conf:
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 1.0 (buildmeister@builder63) Wed May 27 03:15:36 PDT 2009
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Synaptics Touchpad" "SendCoreEvents"
    InputDevice "USB Mouse" "CorePointer"
    EndSection
    Section "InputDevice"
    Option "Device" "/dev/input/mice"
    Option "Protocol" "Auto"
    Option "ZAxisMapping" "4 5"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Emulate3Buttons" "true"
    EndSection
    Section "InputDevice"
    Identifier "Synaptics Touchpad"
    Driver "synaptics"
    Option "SendCoreEvents" "true"
    Option "Device" "/dev/psaux"
    Option "Protocol" "auto-dev"
    Option "SHMconfig" "on"
    Option "LeftEdge" "1700" # x coord left
    Option "RightEdge" "5300" # x coord right
    Option "TopEdge" "1700" # y coord top
    Option "BottomEdge" "4200" # y coord bottom
    Option "FingerLow" "25" # pressure below this level triggers release
    Option "FingerHigh" "30" # pressure above this level triggers touch
    Option "MaxTapTime" "180" # max time in ms for detecting tap
    Option "VertEdgeScroll" "true" # enable vertical scroll zone
    Option "HorizEdgeScroll" "true" # enable horizontal scroll zone
    Option "CornerCoasting" "true" # enable continuous scroll with finger in corner
    Option "CoastingSpeed" "0.30" # corner coasting speed
    Option "VertScrollDelta" "100" # edge-to-edge scroll distance of the vertical scroll
    Option "HorizScrollDelta" "100" # edge-to-edge scroll distance of the horizontal scroll
    Option "AccelFactor" "0.0020" # acceleration factor for normal pointer movements
    Option "VertTwoFingerScroll" "true" # vertical scroll anywhere with two fingers
    Option "HorizTwoFingerScroll" "true" # horizontal scroll anywhere with two fingers
    Option "EmulateTwoFingerMinZ" "120" # this may vary between different machines
    Option "TapButton1" "1"
    Option "TapButton2" "2"
    Option "TapButton3" "3"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbModel" "hpdv5"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    Option "RenderAccel" "true"
    Option "DamageEvents" "True"
    Option "NoLogo" "true"
    Option "AddARGBGLXVisuals" "True"
    Option "DisableGLXRootClipping" "True"
    Option "OnDemandVBlankInterrupts" "True"
    Option "RegistryDwords""PowerMizerEnable=0x1; PerfLevelSrc=0x2233; PowerMizerDefault=0x3"
    Option "BackingStore" "True"
    Option "TripleBuffer" "True"
    Option "DPMS" "true"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Module"
    Load "glx"
    Load "synaptics"
    EndSection
    thanx!
    Last edited by euLinux (2009-07-29 07:02:14)

    hi miau!
    i changed my xorg.conf to match your suggestions... Option "DPMS" "true" moved in Monitor section and blanking and dpms settings in ServerLayout:
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Synaptics Touchpad" "SendCoreEvents"
    InputDevice "USB Mouse" "CorePointer"
    Option "BlankTime" "0"
    Option "StandbyTime" "10"
    Option "SuspendTime" "15"
    Option "OffTime" "20"
    EndSection
    i guess you suggested me to do this way, isn't it?
    unfortunately it still doesn't work!
    it seems that after login gnome-power-manager resets all the settings about dpms in xorg.conf... every section i put them in...
    this is part of the output of xset q just after login:
    Screen Saver:
    prefer blanking: yes allow exposures: yes
    timeout: 0 cycle: 600
    Colors:
    default colormap: 0x20 BlackPixel: 0 WhitePixel: 16777215
    Font Path:
    /usr/share/fonts/misc,/usr/share/fonts/100dpi:unscaled,/usr/share/fonts/75dpi:unscaled,/usr/share/fonts/TTF,/usr/share/fonts/Type1,built-ins
    DPMS (Energy Star):
    Standby: 0 Suspend: 0 Off: 0
    DPMS is Enabled
    Monitor is On
    any other idea?
    thanx

  • [Gnome] Gnome-power-manager is interfering the LCD luminosity level

    Hi there
    I'm on a Dell 1525 laptop, I use "Fn"+"down arrow" and "Fn"+"up arrow" to select the LCD luminosity level.
    When gnome-power-manager is running, there are only 4 levels of luminosity, so sometimes I can't adjust it as I want.
    But when gnome-power-manager is not running, there are 8 levels of luminosity.
    How can I configure gnome-power-manager (or perhaps another app?) in order to have the more levels of luminosity?
    Thank you

    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 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 woes

    Hi all.  I've been having a few problems with gnome-power-manager on my Dell Vostro since upgrading to Gnome 2.26.  I was just wondering if anyone else has been experiencing the same issues:
    - When unplugging my laptop, I no longer get any notifications.  Gconf is correctly configured.
    - When plugging my laptop into the mains, I (usually) get a notification which says words to the effect of: you have unplugged your laptop and it is now discharging.  The icon is is correct.
    - Closing the lid won't suspend the laptop, unless the laptop has been suspended at least once since coming up using the suspend options from the g-p-m menu or the system->shutdown menu.
    I've tried a new gconf setup (removing ~/.gconf* and ~/.gnome*).
    Any ideas?

    Here is my semi solution:
    lid_open.sh
    #!/bin/sh
    if cat < /proc/acpi/button/lid/LID0/state | grep -q closed
    then
    sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool false
    #lid has been opened
    else
    sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool true
    #lid has been closed
    fi
    lid_closed.sh
    #!/bin/sh
    sleep 3
    if cat < /proc/acpi/button/lid/LID0/state | grep -q open
    then
    sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool false
    #lid has been opened
    else
    sudo hal-set-property --udi /org/freedesktop/Hal/devices/computer_logicaldev_input_3 --key button.state.value --bool true
    #lid has been closed
    fi
    Does the job... but still
    I would be very thankful if anyone would be able to post a better solution, or, at least, how to make this work automaticaly.
    Last edited by Void_Walker (2009-06-29 23:27:36)

  • Gnome-Power-Manager don't save history and statistics

    I notice that g-p-m doesn't save history and statistics during a session:
    when I reboot the pc I loose every information and the graphs start by 0.
    I checked every configuration on gconf-editor, but nothing helped me.
    There is the section /apps/gnome-power-manager/info/ but there isn't a schema for any configuration, I don't know what test I could make.
    And I don't find the folder ~/.gnome2/gnome-power-manager on my Arch installations.
    I found this bug with Ubuntu:
    https://bugs.launchpad.net/ubuntu/+sour … bug/302570
    So I run lshal | grep battery to have information about my asus eeepc battery.
    This is the result:
    [root@e3pc luca]# lshal | grep battery
    udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'
      battery.charge_level.current = 20871  (0x5187)  (int)
      battery.charge_level.design = 51034  (0xc75a)  (int)
      battery.charge_level.last_full = 50638  (0xc5ce)  (int)
      battery.charge_level.percentage = 41  (0x29)  (int)
      battery.charge_level.rate = 16993  (0x4261)  (int)
      battery.is_rechargeable = true  (bool)
      battery.model = '901'  (string)
      battery.present = true  (bool)
      battery.rechargeable.is_charging = true  (bool)
      battery.rechargeable.is_discharging = false  (bool)
      battery.remaining_time = 6306  (0x18a2)  (int)
      battery.reporting.current = 2691  (0xa83)  (int)
      battery.reporting.design = 6580  (0x19b4)  (int)
      battery.reporting.last_full = 6529  (0x1981)  (int)
      battery.reporting.rate = 2191  (0x88f)  (int)
      battery.reporting.technology = 'Li-ion'  (string)
      battery.reporting.unit = 'mAh'  (string)
      battery.serial = ''  (string)
      battery.technology = 'lithium-ion'  (string)
      battery.type = 'primary'  (string)
      battery.vendor = 'ASUS'  (string)
      battery.voltage.current = 7756  (0x1e4c)  (int)
      battery.voltage.design = 8400  (0x20d0)  (int)
      battery.voltage.unit = 'mV'  (string)
      info.capabilities = {'battery'} (string list)
      info.category = 'battery'  (string)
      info.udi = '/org/freedesktop/Hal/devices/computer_power_supply_battery_BAT0'  (string)
    Eeepc hasn't the serial. Ok...
    But on my hp 6735s there is the serial of the battery while I run "lshal | grep battery".
    And it has the same problem.
    The version of g-p-m is 2.26.2-1 on both of them.
    I had many difficulties to find documentation about this gnome daemon!!
    Somebody found a solution?
    Thank you all!

    up

  • Gnome-power-manager 2.26 does not suspend on idle

    I got a problem with gnome-power-manager 2.26 (several Versions 2.26.0 2.26.1 2.26.2 (original PKGBUILD)). I can suspend from the applet menu. It does hibernate on critical bat level, but i does not suspend on idle, regardless what timeout values I set in screensaver and gnome-power-manager. Display sleep seems to work though. First I thought, this might be only an issue on my particular notebook, as I could not find anything on google about this, but it is the same behavior on my freshly installed desktop system.
    gnome-power-manager --verbose outputs nothing about going to standby.
    I built gnome-power-manager and gnome-screensaver from 2.24 and they do work porperly, except the notebook will not hibernating on crit bat level.
    Hardware:
    Notebook: HP Pavilion dv3550eg (centrino2 - Nvidia 9300M GS)
    Desktop: GB AMD 790XT, Phenom 720, Nvidia GTX 260
    Software:
    Arch64
    Might this be an Policy issue? Nevertheless if anyone out there has has this problem, let me know and i am goning to file a bug report.

    uwinkelvos wrote:I filed a bugrepoert about this: http://bugs.archlinux.org/task/15038
    anyone willing and able to have a look at the sources is welcome... i just do not have the skills and tools to get to the right conclusion.
    is a well know upstream problem. you should have been fill/comment on bugzilla bugtracker because is not archlinux fault.
    http://bugzilla.gnome.org/buglist.cgi?q … r-manager+
    http://blogs.gnome.org/hughsie/2009/05/ … tableness/

  • Gnome-power-management: /etc/group question

    gnome-power-management suspending works great for me as root , but not as unprivileged user:
    # groups
    root bin daemon sys adm disk wheel log
    # su print
    $ groups
    wheel video audio power noah thinkpad
    Wondering why this is?  (pm-suspend works as unprivileged user)
    TIA,
    print

    well, have a look at error messages (users.log, errors.log, messages.log, pm-suspend.log, ecc...). Did you log out after adding the "power" group to your user?

Maybe you are looking for

  • Invalid Serial Number when it's authentic and tied to my account (Adobe Acrobat XI Pro)

    I have an authentic version of Adobe Acrobat XI Pro. Everything was working fine and then out of the blue the program starts asking me for a serial number. When I enter the serial number that came with the purchase, the error message says "The serial

  • Keynote file i updated yesterday won't open

    I'm feeling nauseous.  I updated a very large file that i've been working on for years yesterday.  Upgraded it to new keynote.  Now....it won't open.  At all.  Just says "can't be opened".  I tried keynote 09, new keynote.  Tried dragging into new ke

  • Set-Up - HELP

    Hi, I've just literally received my AppleTV five minutes ago. It connected to my Wireles Network and is syncing as i type this. The AppleTV is connected to my TV via component. However, there is an annoying buzzing sound coming from the tv speakers n

  • Does an AP reboot if you change the WLANs in an AP Group?

    When you create an AP Group and then assign an access point to that AP Group, you have to reboot the AP. What if you edit an AP Group?  Do the APs automatically reboot, or do you need to do it manually or even better, not at all? I can't see to find

  • IGS Graphics Rendering Problem

    Hi experts, I have the following problem with the igs: I have 2 applications with business graphics technicaly the same. Both worked fine with the same igsURL, but lately one of them is showing "Graphics Rendering Problem" Can You tell me please wher