I've been looking in to this recently as I have the same problem with my thinkpad and we're currently dealing with Lenovo on this. The problem on the thinkpad side is pretty well understood, it's probably exactly the same here. The reason we can increment and decrement by 3 but not by 1 is that we have 3 different devices that control the brigthness of these:
from dmesg:
[936941.841019] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[936941.851964] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input90
This causes two "XF86MonBrignessUp" events to happen, g-s-d responds accordingly. The one additional is brightness_switch_enabled, which is the kernel responding to brightness events and setting the brightness before the key events ever reach g-s-d.
Something I'd like to test is if this is the same situation on the vostro. One way to try it out is to kill gnome-settings-damon and then use xev to confirm that you are in fact getting two key events from xev.
I've been looking in to this recently as I have the same problem with my thinkpad and we're currently dealing with Lenovo on this. The problem on the thinkpad side is pretty well understood, it's probably exactly the same here. The reason we can increment and decrement by 3 but not by 1 is that we have 3 different devices that control the brigthness of these:
from dmesg:
[936941.841019] thinkpad_acpi: detected a 8-level brightness capable ThinkPad platform/ thinkpad_ acpi/input/ input90
[936941.851964] input: ThinkPad Extra Buttons as /devices/
This causes two "XF86MonBrignessUp" events to happen, g-s-d responds accordingly. The one additional is brightness_ switch_ enabled, which is the kernel responding to brightness events and setting the brightness before the key events ever reach g-s-d.
Something I'd like to test is if this is the same situation on the vostro. One way to try it out is to kill gnome-settings- damon and then use xev to confirm that you are in fact getting two key events from xev.