[Bug 979268] Re: Toshiba Satellite L30-134 adjust backlight using function keys does not work

2012-04-12 Thread Andrey Derfehler
** Description changed: After one of kernel update, adjust the backlight using the function keys (Fn + F6, Fn + F7) does not work. In dmesg - [ 586.199550] atkbd serio0: Unknown key released (translated set 2, code 0x55 on isa0060/serio0). [ 586.199557] atkbd serio0: Use

[Bug 979268] Re: Toshiba Satellite L30-134 adjust backlight using function keys does not work

2012-04-12 Thread Andrey Derfehler
in the mainline kernel 3.3.1 there are errors in dmesg, but the adjustment is working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979268 Title: Toshiba Satellite L30-134 adjust backlight using

[Bug 979268] Re: Toshiba Satellite L30-134 adjust backlight using function keys does not work

2012-04-12 Thread Andrey Derfehler
AT Translated Set 2 keyboard shows the event -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979268 Title: Toshiba Satellite L30-134 adjust backlight using function keys does not work To manage

[Bug 979268] [NEW] Toshiba Satellite L30-134 adjust backlight using function keys does not work

2012-04-11 Thread Andrey Derfehler
Public bug reported: After one of kernel update, adjust the backlight using the function keys (Fn + F6, Fn + F7) does not work. In dmesg - [ 586.199550] atkbd serio0: Unknown key released (translated set 2, code 0x55 on isa0060/serio0). [ 586.199557] atkbd serio0: Use 'setkeycodes 55 keycode'

[Bug 979268] Re: Toshiba Satellite L30-134 adjust backlight using function keys does not work

2012-04-11 Thread Andrey Derfehler
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979268 Title: Toshiba Satellite L30-134 adjust backlight using function keys does not work To manage notifications about this bug go to: