Comment 14 for bug 261318

I would agree with the 'invalid' evaluation on the Xorg task, since evdev refusing to handle the device is merely because the device does not present itself as a valid keyboard (as shown in /proc/bus/input/devices). I had marked Xorg as affected due to its interaction with the bug. I would like to see this marked 'confirmed', but I am not sure which tasks should be marked as such. In addition, this seems very important to fix before release... and needs merely a kernel configuration change to bring back the old toshiba_acpi and 'toshiba' modules.