It is correct that MacBookPro3,1 and later are not listed to use the macbookpro addon. However, the light_sensor and keyboard_backlight devices are also driven by the same addon, and thus the newer macbooks should not be listed there either.
Assuming that the gnome-power-manager still treats the listed but missing light sensor, the symptom described in this bug makes sense.
The suggested fix is to remove MacBookPro3,1;MacBookPro3,2;MacBookPro4,1 completely from fdi/policy/10osvendor/10-macbookpro-utils.fdi, and instead implement keyboard_backlight and light_sensor through the mechanism outlined in https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/125918.
This is a continuation of the problem adressed with upstream commit 551461841d64f6f 1cdea6a92e, to this problem: https:/ /bugs.launchpad .net/ubuntu/ +source/ hal/+bug/ 226894
95bd4f1bf9a62f1
It is correct that MacBookPro3,1 and later are not listed to use the macbookpro addon. However, the light_sensor and keyboard_backlight devices are also driven by the same addon, and thus the newer macbooks should not be listed there either.
Assuming that the gnome-power-manager still treats the listed but missing light sensor, the symptom described in this bug makes sense.
The suggested fix is to remove MacBookPro3, 1;MacBookPro3, 2;MacBookPro4, 1 completely from fdi/policy/ 10osvendor/ 10-macbookpro- utils.fdi, and instead implement keyboard_backlight and light_sensor through the mechanism outlined in https:/ /bugs.launchpad .net/ubuntu/ +source/ linux-source- 2.6.22/ +bug/125918.