Hide Forgot
Description of problem: Key repeat doesn't work on X11 despite the settings. Scrolling up doesn't work on XFCE terminal with its default settings. It constantly goes to the end of scroll buffer as if a key was pressed. I can't login to virtual consoles either because there's a constant stream of "^@" characters generated on screen and it interferes with login (I get a login incorrect error). dmesg output is filled with "toshiba_acpi: Unknown key 1431" messages: ... [ 1084.325738] toshiba_acpi: Unknown key 1431 [ 1084.361172] toshiba_acpi: Unknown key 1431 [ 1084.388458] toshiba_acpi: Unknown key 1431 [ 1084.409273] toshiba_acpi: Unknown key 1431 [ 1084.450084] toshiba_acpi: Unknown key 1431 [ 1084.474388] toshiba_acpi: Unknown key 1431 [ 1084.500719] toshiba_acpi: Unknown key 1431 Version-Release number of selected component (if applicable): kernel-3.15.6-200.fc20.x86_64 How reproducible: 100% Steps to Reproduce: 1. Nothing special, just boot the system Additional info: Hardware is a Toshiba Satellite A350 notebook.
When system is booted to Windows, keybaord works without problem.
Seems to be fixed by a recent update.
Sorry, I don't know what caused the temporary recovery but problem still happens with latest (3.16.3-200.fc20.x86_64) kernel. Reopening...
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
I'm still experiencing this problem. Kernel version running: 3.17.2-200.fc20.x86_64
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.