This still happens in current Hardy.
** Summary changed:
- [Gutsy] sonybright.sh doesn't use the correct value range
+ [Gutsy][Hardy] sonybright.sh doesn't use the correct value range
--
[Gutsy][Hardy] sonybright.sh doesn't use the correct value range
https://bugs.launchpad.net/bugs/136380
You
** Changed in: acpi-support (Ubuntu Hardy)
Importance: Undecided = Low
Status: New = Confirmed
--
[Gutsy] sonybright.sh doesn't use the correct value range
https://bugs.launchpad.net/bugs/136380
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
** Tags added: cherry-pick
--
[Gutsy] sonybright.sh doesn't use the correct value range
https://bugs.launchpad.net/bugs/136380
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Could this patch or at least the value changes make it into Gutsy?
Without that Sony laptops consume more energy and loose one brightness
value.
--
[Gutsy] sonybright.sh doesn't use the correct value range
https://bugs.launchpad.net/bugs/136380
You received this bug notification because you are
** Attachment added: acpi-support_0.102.debdiff
http://launchpadlibrarian.net/9300464/acpi-support_0.102.debdiff
--
[Gutsy] sonybright.sh doesn't use the correct value range
https://bugs.launchpad.net/bugs/136380
You received this bug notification because you are a member of Ubuntu
Bugs,
I have forgot something to fix.
The third line BRIGHTNESS=$(cat /sys/class/backlight/sony/actual_brightness)
is wrong since it returns on some circumstances 32 instead of zero. This
happens through spicctrl ([ -x /usr/bin/spicctrl ] /usr/bin/spicctrl -b 0 )
which is run if you try to lower
** Summary changed:
- [Gutsy] sonybrightness.sh doesn't use the correct value range
+ [Gutsy] sonybright.sh doesn't use the correct value range
** Description changed:
Binary package hint: acpi-support
According to http://www.linux.it/~malattia/wiki/index.php/Sony-
laptop#Brightness
