Hide Forgot
Description of problem: After pairing my mouse, it will work for a few hours but then stop working. Version-Release number of selected component (if applicable): bluez-4.101-9.fc19.x86_64 How reproducible: 100% with enough time (usually just a few hours) Steps to Reproduce: 1. pair mouse 2. use it 3. wait (while using even) Actual results: Mouse will stop working. Expected results: Mouse should keep working. Additional info: When the mouse stops working, the kernel starts reporting: Nov 28 19:20:36 pc kernel: [2351144.771977] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:24:34 pc kernel: [2351383.357759] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:24:52 pc kernel: [2351401.353492] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:25:00 pc kernel: [2351409.320353] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:25:01 pc kernel: [2351410.047354] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:25:03 pc kernel: [2351411.490360] Bluetooth: Unexpected continuation frame (len 0) At which point I have to delete the device in the bluetooth manager and re-pair (no pun intended) it which yields: Nov 28 19:25:22 pc bluetoothd[554]: bluetoothd[554]: Discovery session 0x7f30d1cacef0 with :1.2567 activated Nov 28 19:25:22 pc bluetoothd[554]: Discovery session 0x7f30d1cacef0 with :1.2567 activated Nov 28 19:25:34 pc bluetoothd[554]: bluetoothd[554]: Unknown command complete for opcode 37 Nov 28 19:25:34 pc bluetoothd[554]: Unknown command complete for opcode 37 Nov 28 19:25:38 pc bluetoothd[554]: bluetoothd[554]: Stopping discovery Nov 28 19:25:38 pc bluetoothd[554]: Stopping discovery Nov 28 19:25:45 pc bluetoothd[554]: bluetoothd[554]: Stopping discovery Nov 28 19:25:45 pc bluetoothd[554]: Stopping discovery Nov 28 19:25:48 pc kernel: [2351456.640740] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:25:48 pc kernel: [2351456.728708] Bluetooth: Unexpected continuation frame (len 0) Nov 28 19:25:48 pc kernel: [2351456.821427] hid-generic 0005:045E:077C.0013: unknown main item tag 0x0 Nov 28 19:25:48 pc kernel: [2351456.821841] input: Microsoft Sculpt Touch Mouse as /devices/pci0000:00/0000:00:02.0/usb2/2-1/2-1.3/2-1.3:1.0/bluetooth/hci0/hci0:11/input28 Nov 28 19:25:48 pc kernel: [2351456.827145] hid-generic 0005:045E:077C.0013: input,hidraw3: BLUETOOTH HID v1.1e Mouse [Microsoft Sculpt Touch Mouse] on 00:02:72:1e:e0:12 Nov 28 19:25:48 pc bluetoothd[554]: bluetoothd[554]: Stopping discovery Nov 28 19:25:48 pc bluetoothd[554]: Stopping discovery
OK. Frustratingly enough, it seems it doesn't even have to take hours for it to go AWOL. I just had it happen again, a mere 20 minutes from the log samples in the previous comment. Having to have a second mouse handy to stop and pair your primary mouse every few hours is frustrating enough. If I have to do it every 20 minutes, something's going to get broken. :-/ As an additional data point, this is a new mouse that is causing this problem. I had a previous mouse that worked just fine (up until yesterday), never needed re-pairing, etc. Sadly the previous mouse is now dead after it's primary button was sending double-clicks when I only pressed it once. I offer that data point just to prove this this is not a problem with a faulty dongle, etc. Yes, it seems like the problem could be the mouse, but what does this "unexpected continuation frame" mean?
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.