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

Similar Messages

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

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 ?

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.

[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 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-power-manager no icon is being displayed

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

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

Gnome-power-manager not recognizing battery

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

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

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 after Last Upgrade

Hi There,
I just did a pacman -Syu and upgraded lots of packages which also include dbus etc.. I just restarted and puzzled that GNOME Power Manager is a lot different now then it's used to be before the upgrade. First of all, it's systray logo is different. Then it's menu, it's options, everything about it are different. I can't see an upgrade in the pacman.log for gnome-power-manager but it's completely changed..
When I pull the AC power and work on the batteries, it doesn't change the status of the applet. So the applet is very useless right now.. Although it doesn't seem to be an applet while it can't be moved around or I can't change anything about it..
Before the upgrade, I was able to get information by simply right clicking on it selection Information.. But now, even that option is completely changed.. Is there something wrong ?

Hello.
Is the bug fixed already? I have some problems with gnome-power-manager, dbus and hal. After installing Gnome everything was just fine, after I reboot I cannot start HAL:
[root@ichi ~]# /etc/rc.d/hal start
:: Starting Hardware Abstraction Layer [FAIL]
[root@ichi ~]# lshal
error: dbus_bus_get: org.freedesktop.DBus.Error.FileNotFound: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
gnome-power-manager gives msgbox with error about connecting to DBUS.
What is the issue?

Gnome-power-manager wont run

Similar Messages

Maybe you are looking for