Bluetooth mouse does not connect after hibernate

Bug #250468 reported by Joost Cassee
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: bluez-utils

Many people report problems with Bluetooth after hibernation, but the errors I'm getting are different, so I'm posting a new bug report.

Although it work normally after startup, my Bluetooth mouse (Logitech Bluetooth Travel Mouse) not longer connects after resume from hibernation. The system is a Dell Inspiron 510m. After coming back from hibernation I get the following line in /var/log/syslog:
input[*]: Failed to listen on control channel

The same occurs when I deselect and select the 'input' service in the Gnome Bluetooth applet.

When I turn on the Bluetooth mouse I get the following lines (repeatedly):
input[*]: Incoming connection on PSM 17
input[*]: Incoming connection on PSM 19
input[*]: Authorization denied: Not authorized

This does not help:
/etc/init.d/bluetooth stop
/etc/init.d/bluetooth start

I can not removed the rfcomm module (2 unidentified deps), so I cannot confirm whether reloading the kernel modules would work.

Revision history for this message
gpothier (gpothier) wrote :

Same problem here. Dell Latitude D810, ubuntu hardy kernel (2.6.24-19-generic), integrated usb bluetooth adapter:
Bus 002 Device 024: ID 413c:8103 Dell Computer Corp. Wireless 350 Bluetooth

This happens from time to time after resume from suspend, although most of the time it works correctly.

Revision history for this message
Mario Limonciello (superm1) wrote :

Hi:
This problem should be fixed on the latest Intrepid Release Candidate. Can you please download a copy and test on there? If the problem persists, we can see what other options there are to fixing it.

Changed in bluez-utils:
status: New → Incomplete
Changed in bluez:
importance: Undecided → Low
Revision history for this message
Joost Cassee (jcassee) wrote : Re: [Bug 250468] Re: Bluetooth mouse does not connect after hibernate

On 24-10-08 23:38, Mario Limonciello wrote:

> This problem should be fixed on the latest Intrepid Release
> Candidate. Can you please download a copy and test on there? If the
> problem persists, we can see what other options there are to fixing
> it.

Unfortunately, things appear more broken in Intrepid. Currently,
bluetooth will not work at all after resume. The Gnome bluetooth applet
is completely empty, as if the system has no bluetooth adapter at all.
When I restart the bluetooth subsystem from init.d I get the following
lines in syslog:

Oct 31 09:29:20 eye bluetoothd[11012]: Bluetooth daemon
Oct 31 09:29:20 eye bluetoothd[11012]: Starting SDP server
Oct 31 09:29:20 eye bluetoothd[11012]: Starting experimental netlink support
Oct 31 09:29:20 eye bluetoothd[11012]: Failed to find Bluetooth netlink
family
Oct 31 09:29:20 eye bluetoothd[11012]: Can't init plugin
/usr/lib/bluetooth/plugins/netlink.so
Oct 31 09:29:21 eye bluetoothd[11012]: bridge pan0 created
Oct 31 09:29:21 eye bluetoothd[11012]: HCI dev 0 registered
Oct 31 09:29:21 eye kernel: [ 1105.301583] btusb_submit_intr_urb: hci0
urb ee3f1b80 submission failed (2)
Oct 31 09:29:21 eye bluetoothd[11023]: Can't init device hci0:
Input/output error (5)

But things are strange after resume in general, for example top now
tells me the CPU is used for 100% while the cumulative process CPU time
is something like 15%. So maybe bluetooth does not work for unrelated
problems.

Regards,

Joost

--
Joost Cassee
http://joost.cassee.net

Revision history for this message
Brian Lagoni (lagonix) wrote :

Hi,

I have the same problem in Intrepid, it often happens after resuming from hibernation.

But if I use my wireless killswitch on my Dell laptop, the "Wireless 360 Bluetooth" usb adapter is reconnected.
And I can use bluetooth ones again.

I don't know if this is any help, but please say if I can do anything to help..

Regards

Brian

Revision history for this message
NetSpec2008 (djdelimat) wrote :

Mario: wish I could try another release of Ubuntu to test on unfortunately this compaq cq60 only would load the Jaunty 64 distro. If I could load intrepid or hardy I would have.

I did get an answer on my question and gave that option a try and it did not work either... same results with it asking for authorization upon waking up...

Revision history for this message
Unai Uribarri (unaiur) wrote :

I've upgraded to 9.04 beta and is resolved. Also, adding the blueman repository from https://edge.launchpad.net/~blueman/+archive/ppa solves it for 8.10.

Revision history for this message
pet (pet-mueller1) wrote :

[jaunty] bluetooth mouse doesn't connect automatically

Description: Ubuntu 9.04
Release: 9.04
bluez:
  Installiert: 4.39-0ubuntu1
  Kandidat: 4.39-0ubuntu1
  Versions-Tabelle:
 *** 4.39-0ubuntu1 0
        500 http://ppa.launchpad.net jaunty/main Packages
        100 /var/lib/dpkg/status
     4.32-0ubuntu4.1 0
        500 http://ch.archive.ubuntu.com jaunty-updates/main Packages
     4.32-0ubuntu4 0
        500 http://ch.archive.ubuntu.com jaunty/main Packages

The bluetooth mouse is not recognized after wake up or restart. Even a reconnection with the applet isn't possible. Only after erase the definitions of the mouse and a fresh configuration, the mouse can correctly be recognized.

Revision history for this message
Leo Arias (elopio) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 250468, and any other logs that are relevant for this particular issue.

Revision history for this message
Joost Cassee (jcassee) wrote :

I am no longer using any bluetooth devices. If the problem occurs again with a current version of Ubuntu I will create a new issue. You may close this issue.

Leo Arias (elopio)
Changed in bluez (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Manuel FLURY (manuel-flury) wrote :
Download full text (15.0 KiB)

I have the same issue in ubuntu version 10.10

I can reuse my mouse by deleting the mouse bluetooth config (bluetooth icon in the tray bar) and reconfiguring it.

I've tried to use rfcomm instead of the graphical interface but it doesn't work either.

Here is an extract of daemon.log :

Nov 23 19:28:17 manolo bluetoothd[2848]: Authentication requested
Nov 23 19:28:17 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:28:17 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:28:17 manolo bluetoothd[2848]: link_key_notify (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0, type=6)
Nov 23 19:29:03 manolo bluetoothd[2848]: HCI dev 0 down
Nov 23 19:29:03 manolo bluetoothd[2848]: Adapter /org/bluez/2847/hci0 has been disabled
Nov 23 19:29:03 manolo bluetoothd[2848]: Stopping security manager 0
Nov 23 19:29:03 manolo bluetoothd[2848]: HCI dev 0 unregistered
Nov 23 19:29:03 manolo bluetoothd[2848]: Unregister path: /org/bluez/2847/hci0
Nov 23 19:29:12 manolo bluetoothd[2848]: HCI dev 0 registered
Nov 23 19:29:12 manolo bluetoothd[2848]: HCI dev 0 up
Nov 23 19:29:12 manolo bluetoothd[2848]: Starting security manager 0
Nov 23 19:29:12 manolo bluetoothd[2848]: ioctl(HCIUNBLOCKADDR): Invalid argument (22)
Nov 23 19:29:12 manolo bluetoothd[2848]: Adapter /org/bluez/2847/hci0 has been enabled
Nov 23 19:30:04 manolo bluetoothd[2848]: Authentication requested
Nov 23 19:30:04 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:30:04 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:30:04 manolo bluetoothd[2848]: link_key_notify (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0, type=6)
Nov 23 19:31:06 manolo bluetoothd[2848]: Authentication requested
Nov 23 19:31:06 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:06 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:10 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:10 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:10 manolo bluetoothd[2848]: No agent available for 0 request
Nov 23 19:31:12 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:12 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:12 manolo bluetoothd[2848]: No agent available for 0 request
Nov 23 19:31:13 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:13 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:13 manolo bluetoothd[2848]: No agent available for 0 request
Nov 23 19:31:17 manolo bluetoothd[2848]: link_key_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:17 manolo bluetoothd[2848]: pin_code_request (sba=00:22:43:D8:7B:BD, dba=00:22:48:DE:A2:D0)
Nov 23 19:31:17 manolo bluetoothd[2848]: No agent available for 0 request
Nov 23 1...

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.