kbluetoothd, SuSE 9.2 Pro and a Plantronics M2300 headset

The place to post if you need help or advice

Moderators: ChrisThornett, LXF moderators

kbluetoothd, SuSE 9.2 Pro and a Plantronics M2300 headset

Postby odubtaig » Thu Apr 21, 2005 12:14 am

In short: managed to pair it once but now kbluetoothd complains of authentication errors whichever end I try to connect from.

Pin is set to 0000 (this is mandatory for this device and can't be changed).

Device pairs and re-pairs successfully with a Nokia 3650 and Nokia 3650 does likewise with kbluetoothd.

I've tried switching auth and encryption on and off, changed 'security' from auto to user (in hcid.conf) and even un and re-installed all the bluetooth RPMs to reset the config (and I checked, it moved all conflicting files to rpmsaves).

Of course, if anyone can help me out with this and help me hook it up to Skype (it came up as rfcommchannels 1 and 2 before) then someone *cough*notme*cough* should send them a prize :twisted: 'cause I'm bloody stuck :cry:
User avatar
odubtaig
 
Posts: 4
Joined: Wed Apr 20, 2005 11:57 pm

RE: kbluetoothd, SuSE 9.2 Pro and a Plantronics M2300 headse

Postby odubtaig » Thu Apr 21, 2005 10:26 am

Eeeenteresting...

OK, so this morning I get no authentication error (I mean what, did the CPU need a holiday or something?) and I can pair the device which comes up as
    sdp://[00:03:89:79:DF:60]/params?name=M2300%20by%20Plantronics&rfcommchannel=1
and
    sdp://[00:03:89:79:DF:60]/params?name=M2300%20by%20Plantronics&rfcommchannel=2
(one with a handset icon and one as a blank page) but I can't tell if anything's actually connecting (not to mention kbluetoothd keeps losing it) and I know Skype has had issues dealing with bluetooth headsets on other platforms (in that it doesn't). Is there any way anyone knows of testing this?
User avatar
odubtaig
 
Posts: 4
Joined: Wed Apr 20, 2005 11:57 pm

RE: kbluetoothd, SuSE 9.2 Pro and a Plantronics M2300 headse

Postby odubtaig » Thu Apr 21, 2005 7:35 pm

As an asides, despite the notes in hcid.conf (which are innacurate as hell) there is no bluepin, only /bin/bluepincat and /opt/kde3/lib/kdebluetooth/kbluepin.

As well as this, bluepincat has been substantially rewritten in that it now contains:

Code: Select all
KBLUETOOTHD_RUN=`ps -ea|grep kbluetoothd`
   if [ -f /opt/kde3/lib/kdebluetooth/kbluepin \
   -a -x /usr/X11R6/lib/sax/tools/testX \
   -a "X$KBLUETOOTHD_RUN" != "X" ]; then
   /usr/X11R6/lib/sax/tools/testX --fast && \
        exec /opt/kde3/lib/kdebluetooth/kbluepin
fi;

echo -n "PIN:"
cat /etc/bluetooth/pin


So it appears that someone's tried to marry bluepin and bluepincat and messed it up.

After it checks that kbluetoothd is running, the first bit (for the uninitiated) checks if kbluepin exists, if testX exists and is executable and if $KBLUETOOTHD_RUN doesn't exist (if it does then bluepincat has probably been called by kbluetoothd) in which case it runs testX (which exits if a WM is already running) and kbluepin.

At this point kbluepin then outputs PIN:xxxx (or whatever you've entered) to stdout.

Of course the problem here is, whether or not any of this is done bluepincat then goes and outputs PIN:xxxx (whatever is in /etc/bluetooth/pin).

Another distro, another non-standard usage of a file breaking everything.... and I thought FC2 was bad.

Soooo, I've taken bluepincat out of the equation replacing it with kbluepin in /etc/bluetooth/hcid.conf and pairing was aided by manually kickstarting hcitool (to find the bdaddr) and sdptool (to get it pointing on the right direction).

Currently the situation is that a) pairing needs to be initiated from the client end if it's to stick (although I really need to know why the headset not only disconnects but switches off after about 30 seconds) b) kbluepin is initialised each time a device tries to connect which is just how I want it but c) every time I've tested this with the Nokia 3650 I need to put the PIN in 4 times (Computer, then phone, then phone, then computer) even though the headset only requires it once (on the computer). This might merit further investigation but I've still got the rest of this headset malarkey to figure out with all the rfcomm stuff but that's for another question.
User avatar
odubtaig
 
Posts: 4
Joined: Wed Apr 20, 2005 11:57 pm


Return to Help!

Who is online

Users browsing this forum: Narendra and 2 guests