Nabble - Gnome - Power Manager

Re: How discharging time is evaluated

2009-11-17T05:44:22Z

2009/9/13 Patrice Vetsel <ubuntu@...>:
> How the discharging time is evaluate for a netbook ? Here I always start
> with a 4H of time under battery but in fact it's near 7H.

From acpi (the hardware). You probably want to look at
gnome-power-statistics and see if any of the values the hardware is
giving us look wrong.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

how to leave screen brightness handling to the BIOS

2009-10-26T11:53:20Z

Hello,

how can g-p-m be told to leave screen brightness to the BIOS when xrandr
is used instead of HAL, i.e. what is the equivalent of setting
laptop_panel.brightness_in_hardware to true with HAL?
There seems to be a problem with Ubuntu 9.10 on MSI Wind Netbooks which
appear to handle the brightness-related keyboard events in BIOS but
still emit keypresses
(https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/415023/).

--
Guido Berhoerster
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

GNOME Power Manager 2.28.1 released

2009-10-19T03:19:32Z

Version 2.28.1
~~~~~~~~~~~~~~
Released: 2009-10-19

* Translations
- Updated Catalan translation (David Planella)
- Updated Greek translation (Kostas Papadimas)
- Updated Russian translation (Dmitriy Kodanev)
- Updated Romanian translation (Lucian Adrian Grijincu)
- Updated Danish translation (Mads Lundby)
- Upadated Oriya translation (Manoj Kumar Giri)
- Update Czech translation (Marek Černocký)
- Updated Slovenian translation (Matej Urbančič)

* Bugfix:
- Add missing indirection to return value of
DriveSetAllSpindownTimeouts call (Chris Coulson)
- Fix failure error messages and comments (Martin Pitt)
- Help the kernel through its sleep key confusion (Matthias Clasen)
- Improve configure summary wrt HAL (Michael Biebl)
- Use separate variables for dbus and dbus-glib (Michael Biebl)
- Remove devkit-power tool configure check (Michael Biebl)
- Correctly set the focus on the last used device in
gnome-power-statistics (Richard Hughes)
- Do not hide some radio buttons depending on the current machine
state (Richard Hughes)
- Fix up all the issues reported by clang (Richard Hughes)
- Don't try to match and refresh some devices, to stop g-p-s crashing
on virual devices (Richard Hughes)
- DeviceKit-disks is expecting an int as a value, not a uint (Scott Howard)
- Throttle screensaver before suspend/hibernate (Tormod Volden)

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Internetdefensegroup.com, Gnome Power Management

2009-10-19T01:40:02Z

2009/10/19 <rob@...>:
> Binary for X86 (v2.24.4) – Gnome Power Manager for Solaris Nevada X86
> platform
> Binary for SPARC (v2.24.2) – Gnome Power Manager for Solaris Nevada SPARC
> platform

Do you have a link to patches of the modifications you made please?

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Internetdefensegroup.com, Gnome Power Management

2009-10-18T17:45:09Z

Internetdefensegroup.com uses Gnome Power Management Utilities(gpm)

This is GNOME power manager utilities that work with the enhanced acpi (battery, lid, brightness, power button) and CPUfreq scaling.

The GPM GUI was integrated in nevada build 92.

GNOME Power Manager (GPM) is a set of utilities for the desktop user to manage everything about power in his laptop or desktop system. GPM stems from GNOME community. Now we port it to Solaris.

It supports following features:

o Monitor battery status, which shows whether battery is present or not and alerts when battery power is critically low.

o Trigger an action when lid is closed.

o Set CPU frequency policy.

o Set power button response action

o Adjust laptop screen brightness.

o suspend/hibernate system.

o Visualize power consumption statistics.

Downloads

Binary for X86 (v2.24.4) Gnome Power Manager for Solaris Nevada X86 platform

Binary for SPARC (v2.24.2) Gnome Power Manager for Solaris Nevada SPARC platform

Demostration

Flash Demo

NOTE: Suspend on laptop is an experimental feature so far.

Others

Features

In summary, GPM provides features as follows:

1 Battery Monitor

- power status (AC, battery charging, battery discharging and

battery power volume)

- Emit notification message and beep when battery power is

critically low

- perform the specified action when battery is below the critical

level



2 Suspend&Hibernate

- suspend manually

- hibernate manually (only on sparc for now)



3 Brightness support

- brightness hot-key

- brightness applet, show and adjust brightness level by mouse

- Set the specified brightness level in different power modes.



4 CPU scaling policy

- ondemand

- performance



5 Hot-key support

- power button

- brightness hot-key



6 Lid support

- perform the specified action including blank, suspend and hibernate when lid is closed.

- beep when lid is closed/opened.



7 Configuration switching between AC power and Battery Power

- change the action configuration when lid is closed (the action is

one of nothing, blank screen, suspend and hibernate)

- change the action configuration when battery is below the critical

level. (Only in battery mode)

- change the CPU scaling policy

- change the brightness level



8 Preferences

- action when lid is closed (in ac and battery power mode)

- action when battery is critically low (only in battery power mode)

- brightness level (in ac and battery power mode)

- cpu scaling policy (in ac and battery power mode)

- action when power button is pressed (general)

- action when suspend button is pressed (general)

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: The suspend and hibernate menu items Click to flag this post

2009-10-10T15:09:34Z

on 2009/9/14 Richard Hughes wrote:
[...] The user can still
click system -> shutdown -> suspend, or setup a icon on the panel to
do this, or if a laptop just shut the lid. What do you think?

I think those menu entries didn't do any harm at all and I was really missing them. At least now i know there's supposed to be some g-conf key somewhere, which I'll be looking for now.

Anyway - thanks for writing gnome-power-manager in the first place, Richard. I think it's a nice application all in all.

Would be glad if i could get those menu entries back though. I know there are other ways to hibernate, but it happend to be my method of choice to click on these entries as it's only 2 clicks - compared to three through the system menu. ... :-)

cheers

patrick
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Problem forcing monitor to standby

2009-09-29T14:48:39Z

> Date: Mon, 28 Sep 2009 09:54:24 +0100
> Subject: Re: [gpm] Problem forcing monitor to standby
> From: hughsient@...
> To: alweiner7@...
> CC: gnome-power-manager-list@...
>
> On 30/07/2009, Allen Weiner <alweiner7@...> wrote:
> > My multiboot desktop PC runs Fedora 11 and Ubuntu 9.04. The PC has an LCD
> > monitor and a GeForce 6200 graphics card. On both Fedora and Ubuntu I use
> > the proprietary nvidia driver provided by the distro.
>
> The proprietary drivers are not provided by Fedora, and really, they
> are unsupported.

What I meant by this is I use the nvidia driver from the rpmfusion repository, the standard (unofficial) Fedora repo for proprietary items, as opposed to obtaining the nvidia driver from the nvidia web site.

>
> > I just started using Fedora-Gnome. When I run this script under
> > Fedora-Gnome, the monitor goes into standby for about two minutes and then
> > turns back on. Why is the monitor coming back on under Fedora-Gnome? The
> > monitor does the same thing if I issue the xset dpms force standby from a
> > terminal.
>
> I'm not sure. You could try running:
>
> killall gnome-power-manager
> gnome-power-manager --verbose
>
> and see if gnome-power-manager causes events when the monitor wakes
> up. It could also be an X bug, or even a nvidia bug.
>
> > Also, if I use the menu option to exit Fedora-Gnome, and I select "suspend",
> > the system ignores my request.
>
> Sounds like your system doesn't support suspend. Arguably, it's also a
> bug where the suspend menu item is displayed in this case.
>
> > [aweiner@localhost Documents]$ lshal | grep can_suspend
> > power_management.can_suspend = false (bool)
> > power_management.can_suspend_hybrid = false (bool)
> > power_management.can_suspend_to_disk = true (bool)
> > power_management.can_suspend_to_ram = false (bool)
>
> According to HAL your system doesn't support suspending. What's the
> output of "cat /sys/power/state" ?

[aweiner@localhost Documents]$ cat /sys/power/state
standby disk

>
> Richard.

Microsoft brings you a new way to search the web. Try Bing™ now
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

dpms problems

2009-09-28T03:13:17Z

Hi all,

I have some DPMS problems. I am not running a full gnome desktop, just
gnome-settings-daemon and gnome-power-manager with fluxbox

I can set the dpms parameters using xset:
xset dpms 300 600 1200

and the screen blanks after 5 minutes. However, after resuming from
suspend they are reset as shown by xset q:
DPMS (Energy Star):
Standby: 0 Suspend: 0 Off: 0
DPMS is Enabled
Monitor is On
and the screen never blanks

I must say that apart from this glitch I everything worked out of the
box - thanks for this great piece of software.
Shai

My system:
debian sid on a dell d630 with a nvidia quadro graphics card. all
software installed by apt. debian package versions:
gnome-power-manager 2.24.4-3
dbus 1.2.16-2
hal 0.5.13-3
linux-image-2.6.30-1-686 2.6.30-6

output of gconftool-2 -R /apps/gnome-power-manager:
/apps/gnome-power-manager/buttons:
lid_battery = suspend
hibernate = hibernate
suspend = suspend
lid_ac = suspend
power = interactive
/apps/gnome-power-manager/keyboard:
brightness_battery = 50
brightness_ac = 100
/apps/gnome-power-manager/actions:
low_ups = nothing
sleep_type_ac = suspend
event_when_closed_battery = true
critical_ups = shutdown
critical_battery = shutdown
sleep_type_battery = hibernate
/apps/gnome-power-manager/ambient:
dim_policy = none
correction_factor = 50
correction_scale = 200
poll_timeout = 60
enable = true
/apps/gnome-power-manager/thresholds:
time_low = 1200
time_critical = 300
percentage_low = 10
time_action = 120
percentage_critical = 3
percentage_action = 2
/apps/gnome-power-manager/ui:
show_context_menu = true
show_actions_in_menu = true
icon_policy = always
enable_sound = true
/apps/gnome-power-manager/lowpower:
on_battery = true
on_ups = true
on_ac = false
/apps/gnome-power-manager/lock:
hibernate = true
suspend = true
gnome_keyring_hibernate = true
blank_screen = true
use_screensaver_settings = true
gnome_keyring_suspend = false
/apps/gnome-power-manager/timeout:
sleep_display_ac = 60
sleep_computer_battery = 0
sleep_computer_ac = 0
sleep_display_battery = 300
/apps/gnome-power-manager/general:
invalid_timeout = 500
use_profile_time = true
ignore_inhibit_requests = false
check_type_cpu = false
debug = false
can_suspend = true
can_hibernate = true
use_time_for_policy = true
network_sleep = false
installed_schema = 3
policy_suppression_timeout = 5
/apps/gnome-power-manager/backlight:
dpms_method_battery = default
idle_dim_time = 30
battery_reduce = true
brightness_ac = 88
idle_brightness = 30
enable = true
idle_dim_ac = true
dpms_method_ac = default
idle_dim_battery = true
brightness_dim_battery = 50
/apps/gnome-power-manager/statistics:
graph_type = profile-charge-accuracy
show_events = true
show_axis_labels = true
smooth_data = true
data_max_time = 21600
/apps/gnome-power-manager/notify:
discharging = true
inhibit_lid = false
sleep_failed = true
low_power = true
perhaps_recall = true
low_capacity = true
estimated_data = true
fully_charged = true
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: ACPI -correct without AC- measures a power of ~720 Watts when AC is plugged in

2009-09-28T01:58:56Z

On 26/09/2009, Peter Waller <peter.waller@...> wrote:
> This is making gnome-power-manager incorrectly report time-to-empty and
> time-to-full by a significant margin, enough to make the estimates useless
> (2 minutes to completely fill an empty battery?).

Smeels like a kernel bug...

> I guess I need to talk to the kernel ACPI guys to get it fixed there, but I
> was wondering if it would be possible to have an option in GPM to ignore
> these obviously ridiculous values.

Well, it would be a DeviceKit-power feature request. Arguably, we
should just finish the time estimation work in DeviceKit-power and
turn it on by default. Then this sort of bug wouldn't happen.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Problem forcing monitor to standby

2009-09-28T01:54:24Z

On 30/07/2009, Allen Weiner <alweiner7@...> wrote:
> My multiboot desktop PC runs Fedora 11 and Ubuntu 9.04. The PC has an LCD
> monitor and a GeForce 6200 graphics card. On both Fedora and Ubuntu I use
> the proprietary nvidia driver provided by the distro.

The proprietary drivers are not provided by Fedora, and really, they
are unsupported.

> I just started using Fedora-Gnome. When I run this script under
> Fedora-Gnome, the monitor goes into standby for about two minutes and then
> turns back on. Why is the monitor coming back on under Fedora-Gnome? The
> monitor does the same thing if I issue the xset dpms force standby from a
> terminal.

I'm not sure. You could try running:

killall gnome-power-manager
gnome-power-manager --verbose

and see if gnome-power-manager causes events when the monitor wakes
up. It could also be an X bug, or even a nvidia bug.

> Also, if I use the menu option to exit Fedora-Gnome, and I select "suspend",
> the system ignores my request.

Sounds like your system doesn't support suspend. Arguably, it's also a
bug where the suspend menu item is displayed in this case.

> [aweiner@localhost Documents]$ lshal | grep can_suspend
> power_management.can_suspend = false (bool)
> power_management.can_suspend_hybrid = false (bool)
> power_management.can_suspend_to_disk = true (bool)
> power_management.can_suspend_to_ram = false (bool)

According to HAL your system doesn't support suspending. What's the
output of "cat /sys/power/state" ?

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: odd behaviour

2009-09-28T01:50:43Z

On 31/08/2009, Brian Russ <bjrus@...> wrote:

> I noticed a few days ago that my desktop machine (which I use most days)
> had switched itself on in the middle of the night. This was mystifying
> because the only change I had made recently was to accept some security
> updates in the usual way. Now I notice the new Notification icon in the
> top panel and the power management facility includes the battery stuff
> that is irrelevant. The worst thing is that Shutdown no longer means
> that - the machine switches itself on again immediately. This is bad
> because my Dell Vostro has a power button that only ever switches ON. I
> shouldn't have to pull the plug ! can I get back to the previous, easy
> set-up ?

Sorry for the delay, your mail got stuck in the moderation queue.
Could you please explain exactly what the problem is? It would also be
helpful to know the output from gnome-power-bugreport.sh

Thanks,

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

ACPI -correct without AC- measures a power of ~720 Watts when AC is plugged in

2009-09-26T06:22:30Z

I'm on gentoo, and I'm using gnome-extra/gnome-power-manager-2.27.92.

When plugged in, /proc/acpi/battery/BAT0/state reports:
charging state:          charging
present rate:            64645 mA

After unplugging AC:
charging state:          discharging
present rate:            4168 mA

And for a good minute after unplugging, the rate is still ridiculously high. This is making gnome-power-manager incorrectly report time-to-empty and time-to-full by a significant margin, enough to make the estimates useless (2 minutes to completely fill an empty battery?).

I guess I need to talk to the kernel ACPI guys to get it fixed there, but I was wondering if it would be possible to have an option in GPM to ignore these obviously ridiculous values.

Thoughts?

Thanks,

- Peter

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: The suspend and hibernate menu items

2009-09-14T12:54:10Z

Hey Richard and the list,

2009/9/14 Richard Hughes

I'm thinking the suspend and hibernate menu items (when you left click
the battery icon) don't really work. The icon isn't shown if there are
no battery devices, and in some cases it's only shown when the
batteries are discharging or critical, so it's not always there. I'm
thinking of setting the GConf keys to default false for 2.27.x and
removing the functionality completely for 2.29. The user can still
click system -> shutdown -> suspend, or setup a icon on the panel to
do this, or if a laptop just shut the lid. What do you think?

I, as most it seems, have never used these.
whenever I do call shutdown / hibernate (...) from the menu (ie not from hw keys), I use the Gnome menu.

moreover, I also found these inapropriate and redundant with the system menu.
so, removing these is very welcome.

cheers,

Arnaud
--
Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: The suspend and hibernate menu items

2009-09-14T07:03:57Z

I've never used the battery icon menu for those actions, I don't see why others would, since it is in the system shutdown menu.

Odysseus

2009/9/14 Richard Hughes <hughsient@...>

I'm thinking the suspend and hibernate menu items (when you left click
the battery icon) don't really work. The icon isn't shown if there are
no battery devices, and in some cases it's only shown when the
batteries are discharging or critical, so it's not always there. I'm
thinking of setting the GConf keys to default false for 2.27.x and
removing the functionality completely for 2.29. The user can still
click system -> shutdown -> suspend, or setup a icon on the panel to
do this, or if a laptop just shut the lid. What do you think?

Thanks.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: The suspend and hibernate menu items

2009-09-14T06:52:44Z

On Mon, 2009-09-14 at 12:30 +0100, Richard Hughes wrote:
> I'm thinking the suspend and hibernate menu items (when you left click
> the battery icon) don't really work. The icon isn't shown if there are
> no battery devices, and in some cases it's only shown when the
> batteries are discharging or critical, so it's not always there. I'm
> thinking of setting the GConf keys to default false for 2.27.x and
> removing the functionality completely for 2.29. The user can still
> click system -> shutdown -> suspend, or setup a icon on the panel to
> do this, or if a laptop just shut the lid. What do you think?

That sounds good to me.

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

The suspend and hibernate menu items

2009-09-14T04:30:26Z

I'm thinking the suspend and hibernate menu items (when you left click
the battery icon) don't really work. The icon isn't shown if there are
no battery devices, and in some cases it's only shown when the
batteries are discharging or critical, so it's not always there. I'm
thinking of setting the GConf keys to default false for 2.27.x and
removing the functionality completely for 2.29. The user can still
click system -> shutdown -> suspend, or setup a icon on the panel to
do this, or if a laptop just shut the lid. What do you think?

Thanks.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

How discharging time is evaluated

2009-09-13T12:56:53Z

Hi,

How the discharging time is evaluate for a netbook ? Here I always start
with a 4H of time under battery but in fact it's near 7H.

Regards
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Storing energy data in a database for future polling , to find cumulative energy cost of a computing session

2009-09-13T03:24:37Z

2009/9/13 Chris Adams <chris@...>:
> I'm trying to work out if there's a way to easily store energy consumption
> data of a computer, so I can add these readings up over a set period to work
> out how much energy in watts has been used for a particular computing
> session.
> However Gnome power manager already offers some graphing of power usage when
> turned on - so before reinventing the wheel, and creating an sqllite
> database to store data that's already being stored, I wanted to check - is
> this already being done internally somewhere?

Checkout the statistics interface on DeviceKit-power -- but you'll
need a proper power meter plugged in like a a Watts Up Pro if you want
to get accurate data, or data when you're not discharging or charging.

> If so, how can I poll it?

You don't want to poll, polling is bad for battery life.

> My current approach was going to be as follows:
> 1) setting up a daemon to grep the output of the
> `/usr/share/gnome-power-manager/gnome-power-bugreport` command, every n
> seconds.

No, just use DeviceKit-power.

> 2) store current charge in a database

DeviceKit-power already stores this.

> To give some context, I'm hoping to do this so I can eventually take this
> figure and pipe it through the AMEE carbon calculator, to work out the
> carbon footprint of using a machine for a set period. I then want to pipe
> THAT through http://carbon.to, to see what else could have been done with
> the energy I just spent using my computer...
> Thanks,

You'll need to use a watts up pro device then, using a laptop battery
only works when you're discharging or charging, and at the limits of
the range it's not accurate at all.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Storing energy data in a database for future polling , to find cumulative energy cost of a computing session

2009-09-13T03:15:35Z

Hi there,

First post to the list, and if this qn has been asked already,and I missed when I first skimmed the docs please forgive me.

I'm trying to work out if there's a way to easily store energy consumption data of a computer, so I can add these readings up over a set period to work out how much energy in watts has been used for a particular computing session.

However Gnome power manager already offers some graphing of power usage when turned on - so before reinventing the wheel, and creating an sqllite database to store data that's already being stored, I wanted to check - is this already being done internally somewhere?

If so, how can I poll it?

My current approach was going to be as follows:

1) setting up a daemon to grep the output of the `/usr/share/gnome-power-manager/gnome-power-bugreport` command, every n seconds.

2) store current charge in a database

3) at the end of a computing session (say, on sleep, or log off, or shutdown) measure the difference in charge inside the battery (taking into account whether it's plugged in or not to external power etc).

To give some context, I'm hoping to do this so I can eventually take this figure and pipe it through the AMEE carbon calculator, to work out the carbon footprint of using a machine for a set period. I then want to pipe THAT through http://carbon.to, to see what else could have been done with the energy I just spent using my computer...

Thanks,

---
I'm currently only checking my email at 9am, midday and at 4pm.
If you need a response from me urgently, please call or text my mobile, or contact me via Skype (chris.d.adams).
---
Chris Adams
Stemcel Studios
The Hub
5 Torrens Street
London
EC1V 1NQ

email: chris@...
web: www.stemcel.co.uk
twitter:chris_d_adams
skype: chris.d.adams
mob: 07974 368 229
tel: 0207 558 8971

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Disabling backlight control entirely

2009-09-11T09:33:55Z

2009/9/11 Jacob Rau <jacob.rau@...>:
> Richard Hughes wrote:
>>
>> Set /apps/gnome-power-manager/backlight/enable to false in gconf-editor.
>
> Hmm...not to come across as a twat, but that seems to have had no effect.

Did you try restarting gnome-power-manager? Does the brightness still
do funny things when you've killed g-p-m (i.e. is the event in
hardware or the BIOS?)

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Disabling backlight control entirely

2009-09-11T03:45:55Z

Forgot to send this to the list.

-------- Original Message --------
Subject: Re: [gpm] Disabling backlight control entirely
Date: Fri, 11 Sep 2009 06:43:54 -0400
From: Jacob Rau <jacob.rau@...>
To: Richard Hughes <hughsient@...>
References:
<86010bc80909091017k68340f3dpfc61b8172350a129@...>
<15e53e180909110035h6ae5b132vda75fb23038aafb9@...>

Richard Hughes wrote:
> Set /apps/gnome-power-manager/backlight/enable to false in gconf-editor.

Hmm...not to come across as a twat, but that seems to have had no effect.

Since I'm running 2.24.2, which as I understand is very old, I figure
this probably won't be useful, but here it is anyway. I'm actually
trying to quantify it a bit better than "it's broken"; from what I can
tell there's two problems: at boot time, regardless of prior backlight
levels, the brightness is forced to 100%; I can turn it down, but then
after a few seconds, it is forced to 100% again. This has happened
intermittently, but in one session it was repeatedly doing this.
Sometimes it seems related to me pressing keys on the keyboard, but not
all the time.

Is there a .deb package available for Ubuntu Jaunty with 2.26? That
would require replacing HAL as well, right? It might start making sense
for me to get my feet wet here, at least.

Jacob
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Disabling backlight control entirely

2009-09-11T00:35:35Z

2009/9/9 Jacob Rau <jacob.rau@...>:
> However, I really would like to know how to forbid gpm from making any
> changes to my backlight level. The hardware is completely competent at
> remembering and handling this setting, whereas gpm is setting the
> brightness to arbitrary levels every minute or so. I can file a more
> thorough bug report in the proper channel at a later date.

Set /apps/gnome-power-manager/backlight/enable to false in gconf-editor.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Disabling backlight control entirely

2009-09-09T10:17:57Z

Hello,

Gnome-power-manager's method of controlling backlight settings, as of
Ubuntu 9.04, is completely broken. I don't have time to mess with this
right now, so I am not going to test the current development version,
toy with alpha versions of Ubuntu, patch things...etc. Next summer I
will put in the time and effort to fix it for real.

However, I really would like to know how to forbid gpm from making any
changes to my backlight level. The hardware is completely competent at
remembering and handling this setting, whereas gpm is setting the
brightness to arbitrary levels every minute or so. I can file a more
thorough bug report in the proper channel at a later date.

I just want to turn it off right now, and my bit of searching didn't
turn anything up.

Please help.
Jacob
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Merge inhibit applet with GPM?

2009-09-08T03:30:04Z

Hello Richard,

Since you were taking the time to reply, I decided to try and implement
my idea myself, and I have completed it. I have attached the patches for
your review. :)

Cheers,
Pramod

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

user-inhibit-patches.tar.bz2 (7K) Download Attachment

Re: Merge inhibit applet with GPM?

2009-09-06T03:06:39Z

Hello Richard,

I still haven't received your thoughts on this idea, apart from a
question about what it's logic would be, which I tried answering in my
previous email. :)

Also I can try and implement this myself, I already have done a part of
this by:-

1) Implementing two new signals emitted by the GpmTrayIcon object when
the user presses the entry in the popup menu.

2) Having callbacks that successfully manage to give some output once
they receive the signals, albeit I still need to send the method call to
gnome-session to tell it that I want to inhibit the session, but I have
an idea as to how I can achieve this.

So, what do you think?

Cheers,
Pramod

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: [Patch] Make notifications more reliable at session startup

2009-09-06T02:39:23Z

2009/9/6 Pramod Dematagoda <pmd.lotr.gandalf@...>:
> This is a patch that addresses an earlier problem that seems to have
> cropped up again, it does not do much except for replacing
> gtk_status_icon_get_visible with gtk_status_icon_is_embedded as a way of
> finding out if the status icon is visible to the user during session
> startup. Also I removed the timeout relating to the old fix since it's
> no longer necessary. :)

Applied, thanks.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

[Patch] Make notifications more reliable at session startup

2009-09-06T02:25:42Z

Hello Richard,

This is a patch that addresses an earlier problem that seems to have
cropped up again, it does not do much except for replacing
gtk_status_icon_get_visible with gtk_status_icon_is_embedded as a way of
finding out if the status icon is visible to the user during session
startup. Also I removed the timeout relating to the old fix since it's
no longer necessary. :)

Cheers,
Pramod

[0001-Make-notifications-more-reliable-at-session-startup.patch]

From a0168c74ce9c0ad65311fa592be13fec4fd3bef6 Mon Sep 17 00:00:00 2001 From: Pramod Dematagoda <pramod@...> Date: Sun, 6 Sep 2009 14:41:52 +0530 Subject: [PATCH] Make notifications more reliable at session startup --- src/gpm-manager.c | 2 +- src/gpm-tray-icon.c | 1 - 2 files changed, 1 insertions(+), 2 deletions(-) diff --git a/src/gpm-manager.c b/src/gpm-manager.c index 69bc713..27fc98e 100644 --- a/src/gpm-manager.c +++ b/src/gpm-manager.c @@ -379,7 +379,7 @@ gpm_manager_notify (GpmManager *manager, NotifyNotification **notification_class gpm_manager_notify_close (manager, *notification_class); /* if the status icon is hidden, don't point at it */ - if (gtk_status_icon_get_visible (manager->priv->status_icon)) + if (gtk_status_icon_is_embedded (manager->priv->status_icon)) notification = notify_notification_new_with_status_icon (title, message, icon, manager->priv->status_icon); else notification = notify_notification_new (title, message, icon, NULL); diff --git a/src/gpm-tray-icon.c b/src/gpm-tray-icon.c index 11e5981..cf272b0 100644 --- a/src/gpm-tray-icon.c +++ b/src/gpm-tray-icon.c @@ -53,7 +53,6 @@ static void gpm_tray_icon_finalize (GObject *object); #define GPM_TRAY_ICON_GET_PRIVATE(o) (G_TYPE_INSTANCE_GET_PRIVATE ((o), GPM_TYPE_TRAY_ICON, GpmTrayIconPrivate)) -#define GPM_TRAY_ICON_CONNECT_TIMEOUT 10 /* s */ struct GpmTrayIconPrivate { -- 1.6.4.2

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

odd behaviour

2009-08-31T10:34:14Z

I noticed a few days ago that my desktop machine (which I use most days)
had switched itself on in the middle of the night. This was mystifying
because the only change I had made recently was to accept some security
updates in the usual way. Now I notice the new Notification icon in the
top panel and the power management facility includes the battery stuff
that is irrelevant. The worst thing is that Shutdown no longer means
that - the machine switches itself on again immediately. This is bad
because my Dell Vostro has a power button that only ever switches ON. I
shouldn't have to pull the plug ! can I get back to the previous, easy
set-up ?
thanks in anticipation, B J Russ

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Merge inhibit applet with GPM?

2009-08-22T03:49:09Z

My apologies, I forgot to send a CC of my reply to the mailing list.

Pramod

On Fri, 2009-08-21 at 13:40 +0100, Richard Hughes wrote:
> 2009/8/21 Pramod Dematagoda <pmd.lotr.gandalf@...>:
> > I am thinking of trying to integrate the inhibit applet with GPM, the
> > reason being is for simplicity.
>
> What's the logic with integrating it? I would say not many users use
> the inhibit functionality, as it's designed to be value-add, not core
> functionality.
>
> Richard.

Well, first of all, it would not be on the menu at all times since the
user would have the option of having it or not, so those users who do
not need it do not have to be bothered with it at all. For users who do
need this, they can quickly enable inhibition when they need to without
having to have the inhibition applet sitting in the panel all the time.

The users who would benefit from something like this, would be users
watching videos from websites like You Tube, etc. where inhibition is
not automatically enabled, also it would be useful for users of
applications via WINE where some power saving modes like suspending
would probably cause problems.

>From personal experience, I always hated having the inhibition applet
just sitting in the panel because it was not useful(until I actually
needed it) and it took space on a panel that was already crammed with
other applets, but when I did need it, I had to go through the whole
task of adding it to the panel and then activating the inhibition. By
integrating the applet with GPM, the applet does not get in the user's
way until he/she actually needs it and then it is just a simple matter
of clicking on the tray icon and pressing the inhibition entry.

Cheers,
Pramod

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: Merge inhibit applet with GPM?

2009-08-21T05:40:34Z

2009/8/21 Pramod Dematagoda <pmd.lotr.gandalf@...>:
> I am thinking of trying to integrate the inhibit applet with GPM, the
> reason being is for simplicity.

What's the logic with integrating it? I would say not many users use
the inhibit functionality, as it's designed to be value-add, not core
functionality.

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Merge inhibit applet with GPM?

2009-08-20T23:19:23Z

Hello,

I am thinking of trying to integrate the inhibit applet with GPM, the
reason being is for simplicity. For example, me as a laptop user needs
that feature at times, however, I also only have a limited amount of
space on the panel, and I also only require that feature occasionally
where at other times I am more than happy to let the power management go
on as it's supposed to. So basically what I would like to know is, would
my patch be accepted if I was to make it?

About how it would look like, it would be on the main drop down menu of
the GPM tray icon below the Hibernate and Suspend options and separated
by a separator, the icon would change appearance in the way that the
inhibit applet does. I am also thinking of having an option in the GPM
preferences that allows the user to specify if he wants to control the
inhibition of power savings or not, so depending on that option, the
inhibition menu item would or would not be shown.

I already have the GUI part working(except for the option to show the
menu item or not), however I am still trying to figure out how to do it
for real, now dependencies would be the proxy in the GpmSession object
and the inhibited_old boolean variable.

So, what do you think? :)

Cheers,
Pramod

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

GNOME Power Manager 2.26.4 released

2009-08-03T09:20:20Z

GNOME Power Manager is a session daemon that makes it easy to manage the
power on your laptop or desktop system.

This stable release contains important fixes since 2.26.3 was
released. Distributions should consider upgrading gnome-power-manager
via errata packages if possible.

==============
Version 2.26.4
==============

Fixed:
- Make hotkeys work with modifiers (Martin Pitt)
- gnome-power-bugreport.sh: add missing hasbang (Martin Pitt)
- Fix pointer alignment, to build on sparc (Martin Pitt)
- Only use libpanel-applet flags to build applets (Vincent Untz)
- Remove the depricated Encoding= lines from the desktop files. Fixes
#590612 (Richard Hughes)
- Make the orange icons yellower. Fixes rh#512962 (Richard Hughes)
- Add a bodge to reset the idletime XAlarm when we are no longer
inhibited. (Richard Hughes)
- Only show gnome-power-statistics in the context menu if it is
installed. Fixes rh#514249 (Richard Hughes)
- Save the caches value before we emit the inhibit and idle signals
(Richard Hughes)
- Use the correct DBus signal types when watching gnome-session
(Richard Hughes)
- Inhibit gnome-session in the applet, not gnome-power-manager (Richard Hughes)
- Add DeviceKit data to the bugreport script (Richard Hughes)
- Backport a fix from master to fix notification on AC power (Richard Hughes)

Richard.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

GNOME Power Manager 2.27.5

2009-08-03T05:17:30Z

GNOME Power Manager is a session daemon that makes it easy to manage the
power on your laptop or desktop system.

Version 2.27.5
~~~~~~~~~~~~~~
Released: 2009-08-03

* Translations
- Updated Traditional Chinese translation (Chao-Hsiung Liao)
- Updated Swedish translation (Daniel Nylander)
- Updated Finnish translation (Ilkka Tuohela)
- Updated Estonian translation (Ivar Smolin)
- Updated Spanish translation (Jorge González)
- Updated Ukrainian translation (Maxim V. Dziumanenko)
- Updated Irish translation (Seán de Búrca)
- Updated Dutch translation (Tino Meinen)
- Updated Tamil translation (drtvasudevan)

* New Features:
- Claim org.freedesktop.Policy.Power on D-BUS (Martin Pitt)
- Remove PolkitGnome code completely as PolicyKit 1.0 doesn't need
this (Matthias Clasen)
- Add a bodge to reset the idletime XAlarm when we are no longer
inhibited (Richard Hughes)
- Add functionality to debug the idle code by setting GPMIDLEDEBUG on
the command line (Richard Hughes)
- Use the same composited OSD for brightness notification. Fixes
rh#512968 (Richard Hughes)
- Add DeviceKit data to the bugreport script (Richard Hughes)

* Bugfix:
- Fix pointer alignment to build on sparc (Martin Pitt)
- gnome-power-bugreport.sh: add missing hasbang (Martin Pitt)
- Show .desktop files in XFCE (Martin Pitt)
- Make hotkeys work with modifiers (Martin Pitt)
- Remove an unused include to fix compile (Matthias Clasen)
- Be more paranoid about setting idle in a race (Richard Hughes)
- Remove some UI elements after UI review (Richard Hughes)
- Correct the type of the fully-charged signal. Fixes #588259 (Richard Hughes)
- Don't ever fallback to the warning icon in the tray when batteries
are invalid (Richard Hughes)
- Don't show a discharging battery notification on each battery, just
the global battery (Richard Hughes)
- The composite battery is only fully charged if all batteries are
fully charged (Richard Hughes)
- Remove GpmNotify, and do the notifications in a more sane way.
Fixes #423186 (Richard Hughes)
- Constrain the user to a dropdown selection of times, as freeform
sliders are bad UI (Richard Hughes)
- Add policy to show icon when low, rather than critically low. Fixes
#589125 (Richard Hughes)
- Inhibit gnome-session in the applet, not gnome-power-manager (Richard Hughes)
- Change the default to hibernate when critically low on battery
power (Richard Hughes)
- When libnotify fails, fall back to modal dialogs (Richard Hughes)
- Use enumerated values for the policy actions, and hide 'Do nothing'
unless specified in GConf (Richard Hughes)
- Finally remove the CanSuspend and CanHibernate options, now that
gnome-session is ported (Richard Hughes)
- Switch back to org.gnome.PowerManager as we don't adhere to the
shared spec anymore (Richard Hughes)
- Compile common code with a noinst library to make compile quicker,
and reduce the compressed package size by 100kB (Richard Hughes)
- Add a GConf key to show or hide the sleep quirk site (Richard Hughes)
- Make the orange icons yellower. Fixes rh#512962 (Richard Hughes)
- Use the correct DBus signal types when watching gnome-session
(Richard Hughes)
- Save the caches value before we emit the inhibit and idle signals
(Richard Hughes)
- Only show gnome-power-statistics in the context menu if it is
installed. Fixes rh#514249 (Richard Hughes)
- Only use libpanel-applet flags to build applets (Vincent Untz)

Richard
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Problem forcing monitor to standby

2009-07-30T12:48:07Z

My multiboot desktop PC runs Fedora 11 and Ubuntu 9.04. The PC has an LCD monitor and a GeForce 6200 graphics card. On both Fedora and Ubuntu I use the proprietary nvidia driver provided by the distro.

On my desktop (both Fedora & Ubuntu) I have a script I use to force my monitor into standby. I run this when I'm going to be away from the PC for an extended time such as for a meal. The script is:

sleep 5
xset dpms force standby

This script works fine with Fedora-KDE and Ubuntu-Gnome.

I just started using Fedora-Gnome. When I run this script under Fedora-Gnome, the monitor goes into standby for about two minutes and then turns back on. Why is the monitor coming back on under Fedora-Gnome? The monitor does the same thing if I issue the xset dpms force standby from a terminal.

Also, if I use the menu option to exit Fedora-Gnome, and I select "suspend", the system ignores my request.

My Fedora-Gnome AC power management display preference is set for suspend after 20 minutes. The screensaver preference is set for 20 minutes.

Following is some info about my Fedora install:

[aweiner@localhost Documents]$ lshal | grep can_suspend
power_management.can_suspend = false (bool)
power_management.can_suspend_hybrid = false (bool)
power_management.can_suspend_to_disk = true (bool)
power_management.can_suspend_to_ram = false (bool)

Kernel: 2.6.29.6-213.fc11.i686.PAE

gnome-power-manager-2.26.3-1.fc11.i586

hal-0.5.12-26.20090226git.fc11.i586

dbus-1.2.12-2.fc11.i586

My PC is a Dell Dimension 4100 (nine years old).

Windows Live™ Hotmail®: Search, add, and share the web’s latest sports videos. Check it out.
_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list

Re: gnome-session blinken IDLETIME problem

2009-07-29T11:06:06Z

2009/7/29 Richard Hughes <hughsient@...>:
> Okay, after having F11 g-p-m blank the screen on me (not using
> nouveau, that's a separate issue) whilst watching some short videos in
> totem yesterday, I got really angry.

Attached is 130 line demo code illustrating the problem. Notice the
lack of "DEBUG: Reset" lines when there is a session inhibit. Do it
without gnome-power-manager running and observe the brokenness.

Richard.

//gcc -o idlecounter-demo idlecounter-demo.c `pkg-config --cflags --libs gtk+-2.0` -Wall

#include <gdk/gdkx.h>
#include <gdk/gdk.h>
#include <gtk/gtk.h>

#include <stdio.h>
#include <string.h>

#include <X11/Xlib.h>
#include <X11/extensions/sync.h>

#include <stdio.h>
#include <string.h>

static XSyncCounter idle_counter = None;
static XSyncAlarm timeout_alarm = None;
static XSyncAlarm reset_alarm = None;
static Display *dpy;
static int sync_event;

#define TIMEOUT 2000 /* ms */

static void
test_set_alarm (Display *dpy, XSyncAlarm *alarm, XSyncCounter counter, XSyncTestType test, XSyncValue value)
{
XSyncAlarmAttributes attr;
XSyncValue delta;
unsigned int flags;

XSyncIntToValue (&delta, 0);

attr.trigger.counter = counter;
attr.trigger.value_type = XSyncAbsolute;
attr.trigger.test_type = test;
attr.trigger.wait_value = value;
attr.delta = delta;

flags = XSyncCACounter | XSyncCAValueType | XSyncCATestType | XSyncCAValue | XSyncCADelta;

if (*alarm)
XSyncChangeAlarm (dpy, *alarm, flags, &attr);
else
*alarm = XSyncCreateAlarm (dpy, flags, &attr);
}

/**
* test_filter_cb:
*/
static GdkFilterReturn
test_filter_cb (GdkXEvent *gdkxevent, GdkEvent *gdkevent, gpointer data)
{
static gint count = 0;
XEvent *xevent = (XEvent *) gdkxevent;
XSyncAlarmNotifyEvent *alarm_event;
XSyncValue timeout;

/* no point continuing */
if (xevent->type != sync_event + XSyncAlarmNotify)
return GDK_FILTER_CONTINUE;

alarm_event = (XSyncAlarmNotifyEvent *) xevent;

if (alarm_event->alarm == timeout_alarm) {
g_debug ("Timeout %i", count++);

/* Don't match on the current value because
* XSyncNegativeComparison means less or equal. */
int overflow;
XSyncValue add;
XSyncValue plusone;
XSyncIntToValue (&add, -1);
XSyncValueAdd (&plusone, alarm_event->counter_value, add, &overflow);

/* Set the reset alarm to fire the next time
* idle_counter < the current counter value */
test_set_alarm (dpy, &reset_alarm, idle_counter, XSyncNegativeTransition, plusone);

} else if (alarm_event->alarm == reset_alarm) {

g_debug ("Reset");
XSyncIntToValue (&timeout, TIMEOUT);
test_set_alarm (dpy, &timeout_alarm, idle_counter, XSyncPositiveTransition, timeout);
}

return GDK_FILTER_CONTINUE;
}

int
main (int argc, char **argv)
{
int sync_error;
int sync_major, sync_minor;
int ncounters;
XSyncSystemCounter *counters;
XSyncValue timeout;
gint i;

gtk_init (&argc, &argv);
dpy = GDK_DISPLAY ();

if (!XSyncQueryExtension (dpy, &sync_event, &sync_error)) {
g_debug ("No Sync extension");
return 1;
}

XSyncInitialize (dpy, &sync_major, &sync_minor);
counters = XSyncListSystemCounters (dpy, &ncounters);

for (i = 0; i < ncounters && !idle_counter; i++) {
if (!strcmp(counters[i].name, "IDLETIME"))
idle_counter = counters[i].counter;
}

if (!idle_counter) {
g_debug ("No idle counter");
return 1;
}

/* setup timeout */
XSyncIntToValue (&timeout, TIMEOUT);
test_set_alarm (dpy, &timeout_alarm, idle_counter, XSyncPositiveTransition, timeout);

/* catch the timer alarm */
g_debug ("Adding filter");
gdk_window_add_filter (NULL, test_filter_cb, NULL);

g_debug ("Waiting for timeout");
gtk_main ();
return 0;
}

_______________________________________________
gnome-power-manager-list mailing list
gnome-power-manager-list@...
http://mail.gnome.org/mailman/listinfo/gnome-power-manager-list