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

Similar Messages

[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 wont run

when i try and run gnome-power-manager i get the following error, how do i fix this?
thanks markp1989
[mark@blackeee ~]$ gnome-power-manager --verbose
TI:14:10:40 TH:0x920a960 FI:egg-debug.c FN:egg_debug_init,306
- Verbose debugging 1 (on console 1)GPM_VERBOSE
TI:14:10:40 TH:0x920a960 FI:gpm-main.c FN:main,210
- GNOME Power Manager 2.26.1
TI:14:10:40 TH:0x920a960 FI:gpm-session.c FN:gpm_session_init,392
- DBUS error: Could not get owner of name 'org.gnome.SessionManager': no such name
** (gnome-power-manager:4874): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Segmentation fault
[mark@blackeee ~]$

Also posted here: http://bbs.archlinux.org/viewtopic.php?id=70812
Should be fixed in gnome-power-manager-2.26.1-2 (only built for x86_64 at the moment).

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

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?

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)

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

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)

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.

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

Similar Messages

Maybe you are looking for