[SOLVED]Fix gnome-power

Hi guys,
i have a problem with the gnome-power. After last update with pacman -Syu (2 weeks ago).
I see in pacman cache folder that upower got a update from 0.15 -> 0.16
Later i got the problem. Tried to downgrade but nothing to do. Same problem. I use MATE as DE. It is based on gnome2 if i don't wrong.
Now sometimes work and sometimes not. Depend of it mood u.u
I don't have the menu to shutdown when doesn't work. And obviously don't work either the hibernate and the shutdown by acpi calling. Only work with shutdown -h now.
Someone can help me?
Thanks, Gabriele.
Last edited by Lilith (2012-05-21 20:12:20)

Fixed following this:
https://bbs.archlinux.org/viewtopic.php?id=141155
I achieve that is a problem of slim login manager and not of upower.
Edited xinitrc in home folder from: exec ck-launch-session dbus-launch mate-session
to: exec dbus-launch --exit-with-session mate-session
Bye

Similar Messages

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

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

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

[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

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

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)

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)

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.

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)

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)

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]Fix gnome-power

Similar Messages

Maybe you are looking for