Bluetooth devices won't reconnect after suspend/resume

Bug #1133054 reported by Rick Ucker
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I use a bluetooth keyboard and a bluetooth mouse. After I suspend/resume the system, I have issues using them. Sometimes one will work normally and not the other; sometimes neither will work.

Toggling bluetooth off and on doesn't help. I have even gone so far as to delete the offending device from the Bluetooth settings and re-pair it. When I do this, the pairing always fails--it will see the device but the pairing will error out when I try to pair it.

The only workaround I have found is to log out. As soon as I get back to the login screen, both devices immediately start working again.

HCI log attached, per instructions given by apport-bug.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: bluetooth 4.101-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-25.38-generic 3.5.7.4
Uname: Linux 3.5.0-25-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
Date: Mon Feb 25 18:31:59 2013
InstallationDate: Installed on 2012-09-22 (156 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
InterestingModules: bnep rfcomm btusb bluetooth
MachineType: TOSHIBA Satellite A305
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-25-generic root=UUID=dcedb5c2-7281-4ce4-9463-6fdf34bc89c5 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to quantal on 2012-10-24 (124 days ago)
dmi.bios.date: 02/13/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: 1.80
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Base Board Product Name
dmi.board.vendor: Intel Corp.
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnINSYDE:bvr1.80:bd02/13/2009:svnTOSHIBA:pnSatelliteA305:pvrPSAG0U-02701V:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: Satellite A305
dmi.product.version: PSAG0U-02701V
dmi.sys.vendor: TOSHIBA
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 00:1B:DC:0F:A6:6A ACL MTU: 310:10 SCO MTU: 64:8
  UP RUNNING PSCAN
  RX bytes:73345 acl:4132 sco:0 events:246 errors:0
  TX bytes:1723 acl:55 sco:0 commands:55 errors:0

Revision history for this message
Rick Ucker (rick-ucker) wrote :
Revision history for this message
Andreas (mr-pink37) wrote :

Experiencing the same issue w/ 13.04.
Have you been able to resolve this in the meantime?

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in bluez (Ubuntu):
status: New → Confirmed
Revision history for this message
Rick Ucker (rick-ucker) wrote :

Andreas,

Unfortunately, I have not been able to resolve this. I just switched back to using an external bluetooth keyboard after several months of using the mouse only + my laptop's internal keyboard, in which time I did not experience this issue at all.

I am trying to figure out a scenario in which I can reproduce this reliably, but unfortunately I have not yet been able to do so. Sometimes when I resume, one or both of my bluetooth devices won't reconnect until I log out. Sometimes they both work fine when I resume.

BTW, I'm using an Apple keyboard (model A1314) and a Gigabyte mouse (model GM-M7700B).

Revision history for this message
Konrad Zapałowicz (kzapalowicz) wrote :

This is reported against an old version of Ubuntu and many things has changed since then. Because of that we won't fix this issue however if this behavior repeats on a modern version please fill a bug report against it and we will take it from there.

Changed in bluez (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.