https://bugzilla.novell.com/show_bug.cgi?id=450110 User swesemeyer@hotmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=450110#c14 --- Comment #14 from Steve Wesemeyer <swesemeyer@hotmail.com> 2009-01-26 04:30:37 MST --- Some more info... Using xev with the newly mapped keys I find that when I press FN+F2 (the battery power symbol), it generates a continuous stream of keypress and keyrelease events for the keycode 241 which I can only stop by pressing another key (eg 'a'). After that xev does not register any more events for Fn+F2 when it gets pressed again. The only way of getting xev to register the events again is by temporarily switch to a console (CTRL+ALT+F1 say) and then back to the graphics console again (CTRL+ALT+F7). Doing that and pressing FN+F2 again results in the continuous stream of keypress and keyrelease events again. Doing the same for FN+Up (Brightness up) results in the same behaviour, eg xev registers a continuous stream of keypress and keyrelease events for keycode 212 but the brightness only increases with each individual physical keypress. Incidentally, I also have Fedora 10 installed on this laptop and it seems to use a similar hal keyboard mapping set-up for the NC10 but here the brightness keeps on increasing when I press the FN+Up key once which seems to indicate that the continuous stream of keypress and keyrelease events actually gets used. Not sure whether this is hal problem anymore or a just a rubbish BIOS (probably)... Cheers, Steve -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.