Bluetooth mouse fails to reconnect after suspend + resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Pocket Desktop |
In Progress
|
High
|
Unassigned | ||
Canonical System Image |
Confirmed
|
High
|
John McAleely | ||
bluez (Ubuntu) |
In Progress
|
High
|
Konrad Zapałowicz |
Bug Description
I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly.
However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect.
I have a workaround, which is to remove the device and pair it using the command line as follows:
sudo bluez-test-device remove 00:1F:20:EF:B1:00
sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove
sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00
sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes
sudo bluez-test-input connect 00:1F:20:EF:B1:00
Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming.
I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases.
Thanks.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: bluez 4.101-0ubuntu25
ProcVersionSign
Uname: Linux 3.19.0-25-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug 4 09:53:18 2015
InstallationDate: Installed on 2014-01-23 (557 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: TOSHIBA KIRA
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2013
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 1.30
dmi.board.
dmi.board.name: KIRA
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: KIRA
dmi.product.
dmi.sys.vendor: TOSHIBA
hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:587136 acl:36542 sco:0 events:271 errors:0
TX bytes:2913 acl:109 sco:0 commands:81 errors:0
mtime.conffile.
Changed in bluez (Ubuntu): | |
importance: | Undecided → High |
Changed in qtmir (Ubuntu): | |
importance: | Undecided → High |
no longer affects: | qtmir (Ubuntu) |
no longer affects: | qtmir |
Changed in canonical-pocket-desktop: | |
importance: | Undecided → High |
status: | New → In Progress |
tags: | added: after-bluez5 |
tags: | added: bt-retest |
Changed in canonical-pocket-desktop: | |
importance: | Medium → High |
Changed in bluez (Ubuntu): | |
importance: | Medium → High |
Changed in canonical-devices-system-image: | |
milestone: | ww04-2016 → ww08-2016 |
no longer affects: | linux (Ubuntu) |
Changed in canonical-devices-system-image: | |
milestone: | ww08-2016 → backlog |
Changed in bluez (Ubuntu): | |
assignee: | Simon Fels (morphis) → Konrad Zapałowicz (kzapalowicz) |
Changed in canonical-pocket-desktop: | |
assignee: | Simon Fels (morphis) → nobody |
Status changed to 'Confirmed' because the bug affects multiple users.