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)

Similar Messages

Changing brightness in gnome-power-manager has no effect

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

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

Gnome-power-manager 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-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?

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

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

AUR eee-control/gnome-power-manager

I updated my system, and seem to have a minor issue between gnome-power-manager 2.30 and eee-control-tray 9.4 (from the AUR, this might be the wrong section). The tray tool functions normally, except for the automatic FSB scaling with the new gnome-power-manager applet: When I launch eee-control-tray from the command line, I get an output of "FSB scaling not available. Is gnome-power-manager running?" I was wondering if anybody else has encountered this so far, and if it can be fixed.
Last edited by arinlares (2010-04-22 23:38:07)

Hello combuster!
gpm 2.26.3 ?
Is it just a misstyping ?

[SOLVED] gnome-power-manager 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 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] 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 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 doesn't respond to disconnecting AC power supply

"acpi" command always shows correct information, but gnome-power-manager doesn't.
When computer is initially on AC power, and then I disconnect the adapter, gnome-power-manager still says hapilly that I'm on AC power, and the battery is fully charged. It only reacts when I plug adapter back. Then everything is correct. But If i disconnect it again - it shows "AC power, fully charged" again, even regarding the fact it was "80% charged" a second ago.
WTF?

After updating the BIOS, it's more correct, but still not always (I'm running Acer Aspire One 110).
And, another strange issue - when I disconnect the AC adapter, and the power-manager detects that, it automatically locks the screen. (I have a option enabled that when the laptop is closed then the blank screen screensaver is activated, which locks the screen, but this is not the case)

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

Similar Messages

Maybe you are looking for