When you don't use the mouse for a long enough time, the mouse disconnects and won't reconnect. I have to go into bluetooth settings, remove it, and re-pair it. This is the same bug as here: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1094744 I have bluez-4.101-6.fc18.x86_64 How reproducible: every time Steps to Reproduce: 1. wait to enter standby 2. exit standby by pressing any key 3. try to move mouse, mouse is disconnected Expected results: mouse pointer should move Additional info:
dmesg output when first connecting: [25476.140823] hid-generic 0005:045E:077C.000A: unknown main item tag 0x0 [25476.141156] input: Microsoft Sculpt Touch Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input26 [25476.141905] hid-generic 0005:045E:077C.000A: input,hidraw0: BLUETOOTH HID v1.1e Mouse [Microsoft Sculpt Touch Mouse] on 9c:b7:0d:ab:1c:ee
I have observed that the pairing is also lost when a new device is inserted, like a usb stick. Otherwise, the pairing lasts 20 minutes max...
I see what I think is the same problem with: bluez-4.101-8.fc19.x86_64.rpm kernel 3.9.5-301.fc19.x86_64 Thinkpad Laser Mouse - [Re-]discover mouse and pair: Jun 27 18:48:45 gaspode bluetoothd[10091]: bluetoothd[10091]: Discovery session 0x7f898f20a5c0 with :1.453 activated Jun 27 18:48:45 gaspode bluetoothd[10091]: Discovery session 0x7f898f20a5c0 with :1.453 activated Jun 27 18:48:47 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command complete for opcode 37 Jun 27 18:48:47 gaspode bluetoothd[10091]: Unknown command complete for opcode 37 Jun 27 18:48:50 gaspode bluetoothd[10091]: bluetoothd[10091]: Unknown command complete for opcode 37 Jun 27 18:48:50 gaspode bluetoothd[10091]: Unknown command complete for opcode 37 Jun 27 18:48:54 gaspode bluetoothd[10091]: bluetoothd[10091]: Stopping discovery Jun 27 18:48:54 gaspode bluetoothd[10091]: Stopping discovery Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: unknown main item tag 0x0 Jun 27 18:48:56 gaspode kernel: input: ThinkPad Bluetooth Laser Mouse as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.0/bluetooth/hci0/hci0:11/input22 Jun 27 18:48:56 gaspode kernel: hid-generic 0005:17EF:6038.0006: input,hidraw3: BLUETOOTH HID v2.00 Mouse [ThinkPad Bluetooth Laser Mouse] on 00:27:13:96:48:a Jun 27 18:48:56 gaspode /etc/gdm/Xsession[1422]: ** Message: has_config_widget F0:65:DD:67:A2:B9 HumanInterfaceDeviceService - After using the mouse for a little, bit, turn it off (hardware switch); then, a little while later: Jun 27 18:49:35 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: driver failed to report `capacity' property: -5 Jun 27 18:49:40 gaspode kernel: power_supply hid-f0:65:dd:67:a2:b9-battery: driver failed to report `capacity' property: -5 Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Adapter /org/bluez/10091/hci0 has been disabled Jun 27 18:51:22 gaspode bluetoothd[10091]: Adapter /org/bluez/10091/hci0 has been disabled Jun 27 18:51:22 gaspode bluetoothd[10091]: bluetoothd[10091]: Unregister path: /org/bluez/10091/hci0 Jun 27 18:51:22 gaspode bluetoothd[10091]: Unregister path: /org/bluez/10091/hci0 - Turn mouse back on; Nothing happens (was expecting it to reconnect). The machine is a Thinkpad X200s using a: Bus 004 Device 009: ID 0a5c:217f Broadcom Corp. BCM2045B (BDC-2.1) built-in adapter.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.