[Feisty] Bluetooth pairing fails due to bug in init script

[Terminator]

Binary package hint: bluez-utils

Distribution: Kubuntu 7.04 beta

After upgrading Edgy to Feisty the message "Failed to connect to SDP server" appears three times.
Then there is no connection to the bluetooth peripherals (mouse and modem). The Bluetooth light at the notebook shines however.
There is no sdp daemon process running. In the package "bluez-utils" I can't find sdpd, only it's manpages.

Before upgrading it works fine.

[Daniel Holbach (dholbach)]

Thanks for your bug report.

[Marcel Holtmann (holtmann)]

The "sdpd" process is no longer needed. All the functionality are provided by "hcid -s". No idea what KDE is trying to do, but this looks like a bug in KDE and not bluez-utils.

[Terminator (rene-doehler)]

Thank you, Marcel! "hcid -s" was the solution. I couldn't find this hint nowhere before.
During installation of Feisty I said no to replacement of /etc/init.d/bluetooth. This is the file which longs for "sdpd". I delete the correspondending code and set option "-s" for hcid.

It works, wery well!

[Mary Gardiner (puzzlement)]

I just did a fresh install of the "bluetooth" package on Ubuntu Feisty, and the /etc/init.d/bluetooth file still contains these lines:

SDPD=/usr/sbin/sdpd
SDPD_NAME=sdpd

test -x $SDPD || exit 0

As best I can tell, this means that /etc/init.d/bluetooth restart etc are having no effect.

[Mary Gardiner (puzzlement)]

Ooops, this bug is against kdebluetooth... I'll search for and file the same one against bluetooth.

[Kalex (register-goodoldalex)]

So, how do I solve this problem as a normal user? Edit /etc/init.d/bluetooth in what way?

Thanks.

[Joachim Beckers (jbeckers)]

this bug also exists on gutsy, but there the init script has:

SDPTOOL=/usr/bin/sdptool

is that correct? shouldn't it be "hcid -s"?

[Joachim Beckers (jbeckers)]

replying to myself here:

it is correct so it seems. furthermore hcid is started with the -s flag.

pairing doesn't work though.

[drewp (drewp)]

I find myself at this bug because the bluez-utils package indeed looks like it's accidentally missing sdpd:

 % dpkg -L bluez-utils
 ...
 /usr/sbin/hcid
 /usr/share/man/man8/hcid.8.gz
 /usr/share/man/man8/sdpd.8.gz

I would recommend removing the sdpd man page or better yet, augmenting that man page to say "we no longer include sdpd because hcid -s does the same thing".

Incidentally, I'm also having trouble with finding devices and pairing (treo 650 works; gps is 'permission denied').

[Tollef Fog Heen (tfheen)]

This seems to have been fixed in latest bluez-utils.

[no!chance (ralf-fehlau)]

I have the same problem with Hardy Heron. I upgraded from Dapper to Hardy. /etc/init.d/bluetooth tests for an existing sdpd and stops, because it cannot find it.

[no!chance (ralf-fehlau)]

I compared the /etc/init.d/bluetooth with a fresh Installation of hardy: they differ. Trying "aptitude reinstall bluez-utils" gave me no new version of this init script. I also checked the installed version on both systems: 3.26-0ubuntu6. Now i copied the file over the old version and it works.