Description of problem: fn-buttons does not longer work in Fedora, last time I used release 17 and it worked flawlessly (all fn-fx combinations). Currently using release 19 (schrödingers cat), and it gives me a huge problem as I can't activate my touchpad (with fn-f5 on Toshiba Satellite P850-133), rendering the touchpad useless. I was able to boot Fedora 17 from an USB-stick and activate the touchpad, and then reboot into the installed Fedora 19 on my HDD, and can now use my touchpad. Version-Release number of selected component (if applicable): 19 How reproducible: Need a Toshiba Satellite (P850-133 ?) laptop Steps to Reproduce: 1. Move from release 17 to 19 on a Toshiba Satellite laptop Actual results: fn-buttons does not work (except volumebuttons) Expected results: fn-buttons works just as they did in release 17 Additional info: Using a Toshiba Satellite P850-133
possibly related bug (for fc20 and different hardware model): https://bugzilla.redhat.com/show_bug.cgi?id=1008898
*********** 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 19 kernel bugs. Fedora 19 has now been rebased to 3.11.1-200.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
slightly different hardware (see comment#1) but no change with kernel-3.11.1-200.fc19
slightly different hardware (see comment#1) but no change with kernel-3.12.5-301.fc20.x86_64 on fc20 system kernel-3.13.0-0.rc4.git0.1.fc21.x86_64 on otherwise fc20 system
slightly different hardware (see comment#1) but no change with kernel-3.13.0-1.fc21.x86_64 on otherwise fc20 system
*********** MASS BUG UPDATE ************** This bug has been in a needinfo state for more than 1 month and is being closed with insufficient data due to inactivity. If this is still an issue with Fedora 19, please feel free to reopen the bug and provide the additional information requested.