This has been reproducible on both my EEE PC 900 and 1005 all the way until
10.10. To recap, with the default screen settings, I get the following behavior:
1. Adjust the backlight to the lowest setting.
2. Read on the screen for a bit (maybe a minute) without moving the pointer or
typing.
3. Not
** Changed in: gnome-power
Status: Invalid => Expired
** Changed in: gnome-power
Importance: Unknown => Medium
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue that you reported is one that should be
reproducible with the live environment of the Desktop CD of the
development release - Karmic Koala. It would help us greatly if you
could test with it so we can wo
Well, a workaround is to kill gnome-power-manager (or somehow make it
not to load). Then you have full manual control of the backlight. The
only problem I have seen is the batteriy indicator disappears, but can
be replaced by a gnome battery applet instead.
--
Backlight no longer under my control
** Changed in: gnome-power
Status: Confirmed => Invalid
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
d
When I has Hardy I can't control backlight for AC even battery. Now I upgrade
on Intrepid and I can control backlight on AC. But only in gnome-power-manager
with slider. For battery I can select Dim diplay when idle or Reduce backlight
brightness. Hotkey on my Fujitsu Siemens work very strange.
Can anyone duplicate this in hardy or intrepid?
(My AC adaptor died and the new one is still in shipping)
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscr
** Changed in: gnome-power
Status: New => Confirmed
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
deskt
** Changed in: ubuntu
Status: New => Invalid
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu.
--
desktop-bugs
David, I have sometimes experienced what you mention (in a train), but I
think this is an issue we can live with.
In that case the problem is not g-p-m but the power source. I think that
there is no easy way to deal with it, and we should not have something
too complex for such some extreme and ra
Keenan Pepper napsal(a):
> So, let me get this straight.
>
> When the state changes from AC → battery → AC, or from battery → AC →
> battery, g-p-m should forget the temporary setting and use the permanent
> one from GConf.
>
> However, when the state changes from busy → idle → busy, g-p-m should
On Fri, 2008-03-14 at 16:00 +, Keenan Pepper wrote:
> Ted Gould, I tried out your package, and when I move the brightness
> slider in gnome-power-preferences, nothing happens.
Yes. The intention here is to respond to events instead of having
absolute values like the previous design. So that
So, let me get this straight.
When the state changes from AC → battery → AC, or from battery → AC →
battery, g-p-m should forget the temporary setting and use the permanent
one from GConf.
However, when the state changes from busy → idle → busy, g-p-m should
remember the temporary setting.
Is th
Keenan, that's exactly what I thought.
I don't have an ambient light sensor, so I have no experience using it.
However, I tend to believe that the sensor should deal with the
temporary setting only...
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You r
I guess what I think is joining what Kyle says, but to be sure I clarify
what I meant :
There are 2 different settings :
- the defaults values that g-p-m applies when the power state changes
- the current value in each power state, which is temporary for the current
state
The scenario :
g-p-m
I think that it should be separate, otherwise every time I'm on battery
and happen to change the brightness, the next time I switch from AC to
battery it's going to now go to this new value that I didn't explicitly
set. What's worse, when I go into g-p-m's config, I'll see that the
slider has chang
OK, so here's what I'm thinking of doing (I want to get a nod from
someone before I actually write the code):
* Remove the "Reduce backlight brightness" checkbox in the battery tab of
g-p-prefs.
* Replace it with a slider just like the one in the AC tab.
* Hook the new slider up to the
/apps/gno
Kyle Rankin, do you really think there's a need for separate permanent
and temporary settings?
I was thinking that hitting the brightness keys should change the value
in /apps/gnome-power-manager/backlight/brightness_{ac,battery}, and then
in order to get back to the setting you had before, you wo
It seems like what should happen when a user increases (or reduces) his
brightness level beyond what is stored in /apps/gnome-power-
manager/backlight/brightness_battery is that gnome-power-manager should
store this new brightness value separately. When the computer becomes
idle and g-p-m kicks in
Jean-Christophe Baptiste, I see why you want things to be synchronized,
but consider the following situation:
The configured AC brightness level is 100%.
The configuration option to reduce the brightness level on battery is
selected, so the default brightness on battery is 100% multiplied by
some
Ted Gould, I tried out your package, and when I move the brightness
slider in gnome-power-preferences, nothing happens.
It seems like this is the problem:
- /* get the 'main' brightness */
- gpm_conf_get_uint (backlight->priv->conf,
GPM_CONF_BACKLIGHT_BRIGHTNESS_AC, &value);
+
Thank you for this patch, quite an improvement.
However I disagree with the point of view of Keenan, I think the big
issue is that the gnome brightness setting is still not synchronized
with the hardware setting (set with the keyboard).
This is pretty confusing for the user to set brightness to
Could you please try out the GPM for Hardy that is in my PPA:
http://launchpad.net/~ted-gould/+archive
I believe that it has patches that fix this problem.
Thank you. Ted.
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notificat
This is one way to prevent counterintuitive things from happening. The
alternative would be to have the hardware brightness adjustment controls
actually change some GConf key in order to permanently change the default
setting. The big problem with that approach is that if you're calculating the
bri
Confirmed with my brand new Thinkpad T61.
This is a rather important issue, and it does not seem to evoluate at all !
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
26 matches
Mail list logo
