To add extra data points, if I shift to VT1 (Ctrl-Alt-F1) then the
blinking works. It only stops the moment I change back to X. I tried
starting X by itself to see if that affected it and it didn't. In fact
the blinking only stopped once gdm started and continued through the
rest of the desktop
This bug is also affecting me. Blinkd functioned fine with Hardy and
stopped working after the Intrepid upgrade. I notice that when I resume
my laptop that the LEDs will blink for a moment up until I see the
locked screen login prompt. I haven't had a chance to test yet, but I'm
wondering whether
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
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
I also see this issue and I notice that
/sys/class/backlight/XXX/brightness is modified both by g-p-m and by the
Fn-keys on my laptop so it doesn't appear to be a situation where one is
out of sync with the other. A simple way to reproduce this bug:
1. Set battery mode in g-p-m so that backlight
