Bug 1010649
Summary: | Bluetooth mouse is not connecting after suspending | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | RudraB <bnrj.rudra> |
Component: | bluez | Assignee: | Don Zickus <dzickus> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 19 | CC: | berend.de.schouwer, bnocera, circular, dimitris.on.linux, dwmw2, dzickus, extras-orphan, hdegoede, kalevlember, marcel |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-28 13:43:42 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
RudraB
2013-09-22 09:19:08 UTC
$ systemctl status bluetooth.target bluetooth.target - Bluetooth Loaded: loaded (/usr/lib/systemd/system/bluetooth.target; static) Active: active since Sun 2013-09-22 10:05:05 BST; 16min ago Docs: man:systemd.special(7) Sep 22 10:05:05 localhost.localdomain systemd[1]: Starting Bluetooth. Sep 22 10:05:05 localhost.localdomain systemd[1]: Reached target Bluetooth. $ systemctl status bluetooth.service bluetooth.service - Bluetooth service Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled) Active: active (running) since Sun 2013-09-22 10:13:29 BST; 7min ago Main PID: 12612 (bluetoothd) CGroup: name=systemd:/system/bluetooth.service └─12612 /usr/sbin/bluetoothd -n Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: bluetoothd[12612]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: Parsing /etc/bluetooth/input.conf failed: No such file or directory Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: bluetoothd[12612]: Bluetooth Management interface initialized Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: Bluetooth Management interface initialized Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: bluetoothd[12612]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: bluetoothd[12612]: Adapter /org/bluez/12612/hci0 has been enabled Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: bluetoothd[12612]: Unknown command complete for opcode 19 Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: Adapter /org/bluez/12612/hci0 has been enabled Sep 22 10:13:29 localhost.localdomain bluetoothd[12612]: Unknown command complete for opcode 19 Not exactly an elegant workaround, but: - Bluetooth on. - Start GNOME 3 add bluetooth device dialog. - Make mouse discoverable. - Select mouse in the GNOME dialog. - Select "PIN options", "0000" option. - Mouse pairs and connects. - Suspend laptop. - Resume laptop. - Turn bluetooth off. - Turn bluetooth on. - Mouse reconnects. Explicitly selecting the "0000" PIN option is necessary, otherwise the pairing is "forgotten" - device shows up but "not paired" in the GNOME dialog. Bouncing bluetooth after resume is also necessary, otherwise even though paired the mouse doesn't reconnect after resume. I've got the same (or similar) I can reconnect without bouncing bluetooth, but I have to enable/disable bluetooth multiple times, and hit the 'connect' button on the mouse multiple times. Started a few days ago. Possibly related from yum.log: Aug 01 09:51:50 Updated: bluez-4.101-9.fc19.x86_64 Sep 19 10:34:07 Installed: kernel-3.11.1-200.fc19.x86_64 I don't think it was a problem in August. Hi Berend, I just hit the same problem, and I've managed to fix it for my case (Dell E6430 laptop with integrated bluetooth). As such I believe this bug is a duplicate of bug 988481, so lets discuss this further there. Regards, Hans *** This bug has been marked as a duplicate of bug 988481 *** |