Public bug reported:
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
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
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=/boot/vmlinuz-3.19.0-25-generic.efi.signed
root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq
vesafb.invalid=1 splash quiet nopat vt.handoff=7
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.asset.tag: 0000000000
dmi.board.name: KIRA
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias:
dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: KIRA
dmi.product.version: PSU7FA-00T00K
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..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug vivid
** Description changed:
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 name as other
+ 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
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
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=/boot/vmlinuz-3.19.0-25-generic.efi.signed
root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq
vesafb.invalid=1 splash quiet nopat vt.handoff=7
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.asset.tag: 0000000000
dmi.board.name: KIRA
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias:
dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: KIRA
dmi.product.version: PSU7FA-00T00K
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
+ 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..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1481136
Title:
Bluetooth mouse fails to reconnect after suspend + resume
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1481136/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
