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!

Similar Messages

How do I get gnome-power-manager working with standalone Openbox?

I'm brand new to Arch, so sorry if this is a dumb question that's already been answered. I'm installing on a Thinkpad T410, and I want a battery icon in my system tray. I've installed Openbox as a standalone window manager, and I'm using tint2 for a panel and system tray. I need something in my system tray to show my battery status.
I've looked around, and I don't really see any alternative to gnome-power-manager (I looked at trayfreq and batterymon), so I'm attempting to use that. I've installed it, but if I try to run it from a terminal I get this:
GLib-GIO-ERROR **: Settings schema 'org.gnome.settings-daemon.plugins.power' is not installed
aborting...
Aborted
After I get that, it quits and I really don't know what's going on there. Searching for "settings schema not installed" gets me nothing useful, so does anyone have an idea as to how to solve this problem?

n1md4 wrote:This solution worked for me too. I run a vanilla openbox install. Although I now have the battery icon in the panel, when selecting preferences, nothing loads. Any ideas?
From this thread https://bbs.archlinux.org/viewtopic.php?id=118420 the user said it solved it installing gnome-control-center.

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 and screen brightness

gnome-power-manager appears to be screwing with my ability to adjust the screen brightness. Now there are only two brightness settings that work - the ones defined in gnome-power-manager settings. Using the keyboard shortcuts "works" in that I can increase the brightness one level but then the change gets overridden. Decreasing the brightness sets it at the minimum level then I can get it back without entering gpm settings. This definitely work before the last update and I think for a while after.
Is there anyway I can get it to listen to manual adjustments?
Edit: I think this was due to the latest hal update.
> lshal | grep bright
laptop_panel.brightness_in_hardware = false (bool)
Edit 2:
Found http://ubuntuforums.org/archive/index.php/t-290994.html
Adding "video" to MOD_BLACKLIST in /etc/rc.conf fixed this. This is just a kernel module right? Nothing else will be screwed...?
Last edited by Allan (2007-10-31 11:30:37)

I have Sony Vaio VGN-FZ38M with Nvidia 8400M GT. I used package 'nvclock' (it is in repo) to control lcd brightness, here site with more info: NVClock. Some time ago I also configured Fn keys to work with it (on Ubuntu), but on Arch I didn't manged but I didn't try hard (in general i don't need, my laptop is stationary all the time). Solution I've found somwehere in Ubuntu forums.
edit: typo in address
edit2:
here's the solution from Ubuntu: http://newyork.ubuntuforums.org/showthr … ?t=1004568
Last edited by folletto (2009-06-14 20:58:56)

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

VLC keeps automatically starting gnome-power-manager, why?

Ive been running fluxbox as my main WM for a long time now. Recently I installed VLC, and every time I watch a movie it automatically starts gnome-power-manager. I have double checked my .fluxbox/startup and my xinitrc and even my rc.conf but there is no mention of gnome-power-manager or gnome-settings-dameon or anything gnome anywhere. It seems to only happen with VLC. Why does this keep happening?
I don't want to use gnome-power-manager in fluxbox, but I have another user that uses gnome as the default wm so I don't want to remove gnome either. How can I stop this behavior?
Last edited by tjwoosta (2009-09-13 19:00:19)

The only thing I can think of is the screen saver option in vlc.
Go to Tools / Preferences and click the All radio button select Video and see if Disable screensaver is selected. If not disable it and see if it fixes the problem.
edit: typos
Last edited by loafer (2009-09-13 19:13:12)

[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-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)

[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)

Pm-suspend quirks works - not gnome power manager

I installed Arch on my Thinkpad R61 once before, but the suspend 2 ram stuff didn't work. Well, I installed again with the goal of figuring it out, and I did. If I add the line
DISPLAY_QUIRK_S3_BIOS="true"
to /etc/pm/config.d/config
Then type sudo pm-suspend in the console and my computer gracefully goes to sleep and wakes up exactly how it should. However if I try to make my computer sleep through any other method, such as closing the lid or pressing the sleep button (Fn+F4) or using the gnome power icon, I just get the screen saver login window and when I return to the main desktop I see "Sleep Problem' popup from the gnome power icon. I'm wondering if there is another file I need to configure to make it all work. I'm really close and this is the last issue I have to solve to have a perfectly working arch install on my laptop, which would make me happy!

same problem here..
Acer 5920G T7300, Nvidia 8600GT, Intel 3945abg wifi card..running standard 2.6.25-ARCH from testing
if I call "sudo pm-suspend" from the console, it works without problems
if I try to suspend from the gnome-power-manager icon, it get me to the screen saver, and the "Sleep Problem" message popups.
I have only installed pm-utils, and made the "resume=/path/to/swap" modify in grub's menu.lst .. no other configs or modifications made by me..
edit I've just tried hibernate (sudo pm-hibernate) and it works fine too.. obviously it doesn't work by the gnome-power-manager icon.
Last edited by Berseker (2008-05-13 11:30:52)

Hal gnome-power-manager hibernate scripts

Hi All,
I'm having issues hibernating to disk using gnome-power-manager. My user is in the "power" group and I can suspend from a terminal using "sudo hibernate". However, when I attempt to hibernate with gnome-power-manager, i recive an error "Hal failed to hibernate - please see FAQ". When I run g-p-m with no-daemon, it gives an "unspecified error: failed to hibernate". I have the necessary hibernate scripts in /usr/share/hal/scripts (is this the default dir?) and the hal-system-power-hibernate looks as follows:
#!/bin/bash
POWERSAVED_SUSPEND2DISK="dbus-send --system --dest=com.novell.powersave \
--print-reply /com/novell/powersave \
com.novell.powersave.action.SuspendToDisk"
unsupported() {
echo org.freedesktop.Hal.Device.SystemPowerManagement.NotSupported >&2
echo No hibernate script found >&2
exit 1
if [ -x "/usr/sbin/hibernate" ] ; then
echo "wtf"
hibernate
RET=$?
else
unsupported
fi
#Refresh devices as a resume can do funny things
for type in button battery ac_adapter
do
devices=`hal-find-by-capability --capability $type`
for device in $devices
do
dbus-send --system --print-reply --dest=org.freedesktop.Hal \
$device org.freedesktop.Hal.Device.Rescan
done
done
exit $RET
Please let me know what I'm missing or what necessary config files need to be tweaked.

Does suspend to RAM work with gnome-power-manager? On my system I installed powersave from unstable, which is the daemon used by SuSE to do suspend to RAM and suspend to disk.

[Gnome 3] gnome-power-manager suspend timeout

When I set "System Settings > Power > Put the computer to sleep when inactive" to 5 min. Nothing ever happens.
I have searched and looked in dconf-editor but been unable to discover anything useful.
edit; just changed the title think it is better in this case (:
edit
Just changed the titel again it was more sane the first time around...
Still broked as of gnome-power-manager 3.0.2-1, patch still good...
Last edited by cell (2011-05-31 21:18:13)

I found this https://bugzilla.redhat.com/show_bug.cgi?id=675005 nonbug so...but any chance this is a matter of privileges when it comes to power settings?
I am running gnome 3 on my desktop never had any problems with suspend before. I did create a new user and deleted the old user before installing gnome 3, so maybe I missed something in that process.
Taking a look at the power settings on my netbook with gnome 2.32.1 they sure did slim down them settings.
This is the output if I run gnome-control-center -
libnm-glib.so.4: cannot open shared object file: No such file or directory
Failed to load module: /usr/lib/control-center-1/panels/libnetwork.so
Error getting primary device: GDBus.Error:org.gnome.PowerManager.Failed: There is no primary device to reflect system state (don't show any UI)
If I press the suspend button from the user menu I suspend just fine btw so thats a bit weird.

[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 don't save history and statistics

Similar Messages

Maybe you are looking for