[feisty] bluetooth mouse doesn't connect automatically

Bug #84541 reported by calimarno
34
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Undecided
Unassigned
Declined for Feisty by Mario Limonciello
bluez-utils (Ubuntu)
Undecided
Unassigned
Declined for Feisty by Mario Limonciello

Bug Description

Binary package hint: bluez-utils

I add the following lines to the /etc/default/bluez-utils configuration file :

HIDD_ENABLED=1
HIDD_OPTIONS="--connect 00:07:61:48:65:B9 --master --server"

However, I have to reconnect manually my bluetooth mouse (Logitech) every time I restart the computer or even after a while I didn't use the mouse with "sudo hidd --search".

I'm running up-to-date feisty.

Revision history for this message
calimarno (calimarno) wrote :

I forgot to mention that my mouse connects automatically with dapper!

Revision history for this message
Marcel Holtmann (holtmann) wrote :

Installing bluez-utils-3.9 should solve all the race conditions on system boot and then HIDD_OPTIONS="--master --server" should be enough.

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

@Calimarno,

Edgy onwards the file to be edited is /etc/default/bluetooth.
Please see if you can find the file. If not your installation may have some problem and tell us version of bluez-utils.

Revision history for this message
Alexis Saettler (asbin) wrote :

I have exactly the same problem.

I'm running on feisty.

asbin@socrate:~$ dpkg -l | grep bluez
ii bluez-cups 3.9-0ubuntu1 Bluetooth printer driver for CUPS
ii bluez-pin 0.30-2.1ubuntu3 Bluetooth PIN helper with D-BUS support
ii bluez-utils 3.9-0ubuntu1 Bluetooth tools and daemons

Here is some output from kernel and hidd :

asbin@socrate:~$ tail -f /var/log/syslog &
asbin@socrate:~$ sudo /usr/bin/hidd -n --master --server &
asbin@socrate:~$ hidd[30334]: Bluetooth HID daemon
Mar 11 12:45:25 socrate hidd[30334]: Bluetooth HID daemon

asbin@socrate:~$ #turning on my mouse
asbin@socrate:~$ #nothing happen
asbin@socrate:~$ sudo hidd --search
Searching ...
        Connecting to device 00:07:61:64:A2:98
asbin@socrate:~$ Mar 11 12:46:09 socrate hidd: New HID device 00:07:61:64:A2:98 (Logitech Bluetooth Mouse)
Mar 11 12:46:09 socrate kernel: [124826.726286] input: Bluetooth HID Boot Protocol Device as /class/input/input25

asbin@socrate:~$ #turning off my mouse
asbin@socrate:~$ #turning on my mouse
asbin@socrate:~$ #nothing happen
asbin@socrate:~$ sudo hidd --search
Searching ...
        Connecting to device 00:07:61:64:A2:98
asbin@socrate:~$ Mar 11 12:46:48 socrate hidd: New HID device 00:07:61:64:A2:98 (Logitech Bluetooth Mouse)
Mar 11 12:46:48 socrate kernel: [124852.199551] input: Bluetooth HID Boot Protocol Device as /class/input/input26

Everything I run "hidd --search" I have to push the pairing button on my mouse even if it's not working. It's like it's always the first time I connect it.

In /etc/default/bluetooth file, I've tried to write :
HIDD_ENABLED=1
HIDD_OPTIONS="--master --connect 00:07:61:64:A2:98 --server"
This was working some weeks ago, on edgy (I don't remeber the version). Some regression should has come ...

Fell free to ask me for other output/tests ...

Laur Mõtus (vprints)
Changed in bluez-utils:
status: Unconfirmed → Confirmed
Revision history for this message
lightenup (chrisweakland) wrote :

I have encountered the same exact problem. I have also noticed that if I perform a "hidd --kill 00:12:34:56:78:90" and then try and do a "hidd --connect 00:12:34:56:78:90" it will not re-connect unless I press the reset button on the bottom of the mouse.

If you need me to test anything please ask.

Revision history for this message
tomitoma (thomas-testasecca) wrote :

Hi,

Same problem here ... the Logitech V270 doesn't connect automatically on startup under feisty up to date !

I installed bluetooth, gnome-bluetooth, bluez-(pin/pin/utils/cups/gnome), configure /etc/default/bluetooth with
HIDD_ENABLED=1
HIDD_OPTIONS=" --master --server"

I tried --connect 00:AA:BB:CC ... and it changes nothing ...

I am a little bit disappointed since it worked yesterday under feisty (not perfectly because i had to switch off/on the mouse to have it detected) ... today i reinstall ... and it doesn't work !

If i hidd --search it works ... at least there is a work around.

If you need some tests, please ask.

Bye
Tom

Revision history for this message
calimarno (calimarno) wrote :

I found a solution for a feisty updated to edgy... You need to replace your /etc/default/bluetooth file by the one provided in the package during the update process.
Alternatively, you can to uninstall bluez-utils and then to delete manually the file /etc/default/bluetooth and then to reinstall the package.
I hop this would help!

Revision history for this message
Alexis Saettler (asbin) wrote :

Reinstallation of bluez-utils didn't have any effect ...

When I do
 "sudo hidd --connect 00:07:61:64:A2:98"
I get :
 "Can't create HID control channel: Connection refused"
is anyone having the same problem ?

Revision history for this message
aalcock (aalcock+ubuntu) wrote :

I have the same problem - Feisty 7.0.4 fully patched and a Logitech V270 bluetooth mouse and the appropriate changes to /etc/default/bluetooth

I always succeed when:
1) I use the command line to run the "sudo hidd ..." command (might be --search or --connect)
2) Press the reset (pairing) button on the mouse.

However, when the mouse disconnects (eg computer reboots, mouse is switched on or mouse disconnects after a timeout), the pairing is lost and does not reestablish.

One further observations: When the mouse is unpaired but is moved, the kbluetoothd icon in my status bar flashes a few times. I think the mouse is attempting to reconnect to the computer

Revision history for this message
rowanrook (brentrowan) wrote :

I have also experienced this problem on a Dell Inspiron 600m with Logitech Bluetooth mouse.

Revision history for this message
Superglue (pakhotin) wrote :

Same here. I am getting this problem on a Dell Precision M60 with Logitech V270 Bluetooth mouse. Mouse does not connect after reboot automatically. I have to do "sudo hidd --search" and press reset button on the mouse.

Revision history for this message
rowanrook (brentrowan) wrote : Re: [Bug 84541] Re: [feisty] bluetooth mouse doesn't connect automatically

Yeah, it's awkward. I tried to make a shortcut command for the desktop but
it didn't work. I know that the mouse works when I boot of the System Rescue
CD <http://www.sysresccd.org/Main_Page> (Gentoo Linux), so good code exists.
I just don't know exactly how to extract it from the CD and install it to
Ubuntu.

On 9/21/07, Superglue <email address hidden> wrote:
>
> Same here. I am getting this problem on a Dell Precision M60 with
> Logitech V270 Bluetooth mouse. Mouse does not connect after reboot
> automatically. I have to do "sudo hidd --search" and press reset button
> on the mouse.
>
> --
> [feisty] bluetooth mouse doesn't connect automatically
> https://bugs.launchpad.net/bugs/84541
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Brent "Rowan" Hopkins

Revision history for this message
Marcel Holtmann (holtmann) wrote :

The "hidd --connect ..." command needs to be used only once. After that there is not need to use it ever again. The same applies to "hidd --search ...". What you are doing is attempting to make something work, but with no idea how Bluetooth HID is designed. Stop messing around and make only sure that "hidd --server" is running to handle the re-connects from your devices.

Revision history for this message
Jim Carroll (mrmaple) wrote :

I also have to run hidd --search dozens of times every day on my feisty install.

When I run hidd --server, it tells me Can't listen on HID control channel: Address already in use.

I do have hidd --server set up in /etc/defaults/bluetooth.

Is there a write-up anywhere that would help me understand exactly what is going on
instead of just just telling me what to type? (Of course, if you can help me get it working
by telling me what to type I'd be very grateful!)

-Jim

Revision history for this message
aalcock (aalcock+ubuntu) wrote :

Hi Marcel

Running ps | grep hidd | grep -v grep I get:
root 5670 1 0 Sep25 ? 00:00:00 /usr/bin/hidd -i 00:07:61:84:B3:03 --server

(00:07:61:84:B3:03 is my mouse; running hidd --server without the -i MAC address doesn't allow a reconnect under any circumstance)

And yet my bluetooth mouse does not reconnect either at startup, KDE login or when the mouse times out its bluetooth connection after a period of inactivity.

So far the ONLY way I have found to get the mouse working again is, like Jim and rowanook, to use an hidd --connect. Believe me, I don't want to do this.

I think that this thread is actually saying that the approach you fairly bluntly proscribe doesn't work - and that's (we believe) a bug.

Revision history for this message
Superglue (pakhotin) wrote :

Does any developer of hidd look inside this thread?

To Marcel: I am sure that "hidd --server" is running but it does not handle the re-connects from my mouse. It seems that hidd with option "--server" is running fine (because all people reporting problems above are able to make mouse work with "hidd --search" or "hidd --connect"), but not in *scanning* mode. Is it possible to run hidd (with some hidden option) in scanning mode?

Revision history for this message
Superglue (pakhotin) wrote :

Hm, after my last message I spent half of an hour browsing this forum and looks like I found a solution for this problem in the thread: https://launchpad.net/ubuntu/+source/bluez-utils/+bug/59222

The bottom line is: file /var/lib/bluetooth/*/config has to have "mode discoverable" but not "mode connectable". After reboot my mouse has been discovered without manual typing "hidd --search". Please report if it does help you. Good luck!

Revision history for this message
Chris Edwards (caedwa) wrote :

Yes that fixes the problem for me too. You don't need to reboot. Here's what I did:

/etc/init.d/bluetooth stop
vim /var/liib/bluetooth/*/config (Changed mode off to mode discoverable)
/etc/init.d/bluetooth start

My mouse and keyboard then magically connected!

Revision history for this message
Marcel Holtmann (holtmann) wrote :

The mode "discoverable" is non-sense. Only mode "connectable" is needed. When calling hciconfig and it doesn't show "pscan" then no HID device can re-connect.

Revision history for this message
AusIV (linux-ausiv) wrote :

I'd like to note that I was having the same problem, and the fix described by Superglue solved the problem.

Revision history for this message
aalcock (aalcock+ubuntu) wrote :

The above solution didn't work for me, but, after an upgrade to Gutsy, the mouse is working perfectly.

Revision history for this message
Welson (welson-sun) wrote :

OK, this finally WORKS for me (Ubuntu 7.04, everything up to date, Logitech v470)

1. /etc/default/bluetooth
HIDD_ENABLED=1
HIDD_OPTIONS="--master --connect xx:xx:xx:xx:xx:xx --server"

2. This is the weird part, add a blank line at the end of /etc/bluetooth/hcid.conf

3. I have bluez-gnome installed, don't know if needed.

Good luck!

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

Bluetooth input devices are trusted by default on 4.x packages that are in Intrepid.

bluez (4.12-0ubuntu1) intrepid; urgency=low

  * Initial Release. (LP: #274950)
    - This package replaces bluez-utils and bluez-libs source packages.
    - It was generated by merging the contents of bluez-utils and bluez-libs
      and updating content.
    - Legacy functionality for hidd, dund, and pand are not present, and
      have been removed from all configuration files.
  * This release introduces encryption (LP: #182191)
  * debian/patches:
    - bluez-utils-oui-usage.patch was borrowed from the Fedora 10 packaging.
    - sco-connect-git.patch was taken from bluez git shortly after 4.12 release.
      It should "help" with some sco headset issues.
  * debian/control:
    - Update different packages per upstream's recommendations.
    - Update conflicts/replaces for earlier packages.
    - Add a transitional bluez-utils package to help with the transition.

 -- Mario Limonciello < <email address hidden>> Tue, 07 Oct 2008 12:10:29 -0500

Changed in bluez-utils:
status: Confirmed → Fix Released
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Is this bug now fixed in bluez-utils?

Changed in bluez-utils (Ubuntu):
status: New → Incomplete
Changed in bluez-utils (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers