kdebluetoothbluezmobile phone file transfer problem

On and off for longer than I care to recall I've been attempting to transfer pictures from my mobile phone to my Linux machine with Bluetooth. I've read more HOW-TOs and usenet postings than I can remember and I've still not got it working so I'd be grateful if anyone can provide any suggestions. I know this is quite a long post but I figure providing details of what I've tried already is a good idea.

I'm running Fedora Core 4 with these rpms installed,

bluez-hcidump.i386 1.18-1 installed bluez-libs.i386 2.15-1 installed bluez-libs-devel.i386 2.15-1 installed bluez-pin.i386 0.24-2 installed bluez-utils.i386 2.15-7 installed kdebluetooth.i386 1.0-0.3.beta1.fc4.kde installed kdebluetooth-devel.i386 1.0-0.3.beta1.fc4.kde installed

kdebluetooth rpms are from kde-redhat.sourceforge.net. The phone is a Motorola V500 and the Bluetooth Dongle is a D-Link DBT-120.

If I plug in the dongle I get the kbluetoothd icon in the system tray and if I click it then I can see my phone and the services it supports. hcid and sdpd are both running.

If I attempt to initiate the sending of a picture from my phone it scans, finds the computer but then when I attempt to actually send the picture the phone says it is 'seeking' for a few seconds and then says 'unable to connect'. The computer doesn't appear to have anything to say on the matter.

If I double click the 'OBEX file transfer' icon in the KDE browser then my phone asks if I want to pair with the computer. I say yes, the phone asks for a PIN. I enter the same PIN I have inetc-bluetooth-pin, then the phone says 'verifying PIN' followed by 'Invalid PIN' and the computer says 'unable to connect'. Nothing comes up on the computer asking my to enter a PIN.

In hcid.conf I have commented out the line

dbuspinhelper;

because if it isn't commented out then hcid keeps crashing. I forget where I found this tip.

If I set pinhelper tousr-lib-kdebluetooth-kbluepin then when I enter a PIN on the phone the following appears invar-log-messages -

Dec 21 20:39:25 continuity hcid1871: pincoderequest (sba=XX:XX:XX:XX:XX:XX, dba=XX:XX:XX:XX:XX:XX) Dec 21 20:39:26 continuity hcid5327: PIN helper exited abnormally with code 256

usr-lib-kdebluetooth-kbluepin runs when invoked manually from a command prompt and outputs the number I enter to stdout prefixed by 'PIN:' which I understand is the expected behaviour.

If I set pinhelper tousr-bin-bluez-pin I get

Dec 21 20:43:35 continuity hcid6126: pincoderequest (sba=XX:XX:XX:XX:XX:XX, dba=XX:XX:XX:XX:XX:XX) Dec 21 20:43:35 continuity hcid6180: PIN helper exited abnormally with code 256

usr-bin-bluez-pin doesn't appear to do anything at all when invoked manually from a command prompt.

If I set pin helper to a script -

----endetc-bluetooth-givepin.sh----- #!-bin-sh echo -n "PIN:" catetc-bluetooth-pin ----endetc-bluetooth-givepin.sh-----

----beginetc-bluetooth-pin---- 1234 ----endetc-bluetooth-pin-----

then I get -

Dec 21 20:46:16 continuity hcid6659: pincoderequest (sba=XX:XX:XX:XX:XX:XX, dba=XX:XX:XX:XX:XX:XX) Dec 21 20:46:16 continuity hcid6701: Can't exec PIN helperetc-bluetooth-givepin.sh: Permission denied (13)

Even if I set the permissions on givepin.sh to rwxrwxrwx.

I've been unable to find out what 'code 256' or 'permission denied (13)' mean.

I don't especially want to pair the devices, I just want to be able to copy pictures or mp3s to-from my phone.

As I said, any suggestions greatfully received.

thanks,

mike