Description of problem: This problem occours only when powermanagement have been enabled on the computer and you start to using it again. The mousepointer changes to just a line (big I). Left and right click dont work, but you can move the pointer on the screen. I have not found any workaround on the issue, tough tried 5 different brand of mouse:s and switched usb ports. Only fix is to reboot. Version-Release number of selected component (if applicable): Fedora 20, updated to 2014-04-21 Kernel: 3.13.10-200.fc20.x86_64 Kde How reproducible: 100%, every time. Steps to Reproduce: 1. Boot up Fedora 20, everything works OK 2. Close the lid on the laptop, wait a minute. 3. Open the lid, the mouse is unoperable. Actual results: Expected results: Additional info: Apr 21 18:40:15 localhost mtp-probe: bus: 3, device: 5 was not an MTP device Apr 21 18:40:17 localhost kernel: [ 496.316601] psmouse serio4: Failed to enable mouse on isa0060/serio4 Apr 21 18:40:17 localhost kernel: psmouse serio4: Failed to enable mouse on isa0060/serio4 Apr 21 18:40:20 localhost kernel: [ 499.550438] psmouse serio4: Failed to enable mouse on isa0060/serio4 Apr 21 18:40:20 localhost kernel: psmouse serio4: Failed to enable mouse on isa0060/serio4
Created attachment 888230 [details] Lsmod
Created attachment 888231 [details] Lspci
Sorry, missed brand and type. Asus X550C Laptop.
*********** 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.14.4-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 experience different issues, please open a new bug report for those.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 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.