It seems that bluetooth is not working for me.
Slackware 14.0 RC4 64bit + multilib
bluez-4.99-x86_64-2

the daemon is running, kde bluetooth applet is running
I can scan for devices,
hcitool scan is working, ... shows the surrounding devices,
hcitool dev is working, .... shows the adaptor,

when I try to connect with:
obexftp -b D0:00:C7:1D:E1:E0 -p DSC_5053.JPG
the commands starts OK
Browsing D0:00:C7:1D:E1:E0 ...
Connecting...failed: connect
Tried to connect for 2125ms
error on connect(): Invalid argument
Still trying to connect
Connecting...failed: connect
Tried to connect for 76ms
error on connect(): Invalid argument
Still trying to connect
Connecting...failed: connect
Tried to connect for 13ms
error on connect(): Invalid argument
Still trying to connect

and that is it ... no connection, cannot send files, cannot browse device.

The other device is Samsung GT-I5500 phone, but the same happens to a Nexus7 tablet.
I have a feeling bluetooth used to work in Slackware 13.37

Does anybody have the same problem or is it only me?
It seems like an obexftp issue.

Hey there,

I just tried it with my phone (GT-I5700), it works for me (slackware 14.0 rc4 64bit + multilib, like you):
But I have a custom android version on the phone which doesn't handle bluetooth uploads out of the box (says connection refused).
So I run an APP on the phone for that it's called "bluetooth file transfer". When that APP is running I can use obexftp.

With the latest bluetooth update there was a small change to /etc/bluetooth/audio.conf ( Enable=Socket ),
filetransfer is not audio, but who knows... make sure you have that change.

I'm running a 32 bit clean install of slackware-14-stable and get the exact same message out of obexftp. Pairing works OK, and if I use the browsing commands on my cell (a Pantech C3B) I can pick up files from the computer and store them on the cell, but I cannot send files from the cell to the computer. And obexfs, which is a wrapper for opexftp, won't mount the cell file system. The same adapter dongle, a BCM2210, works fine on Windows XP.

Through trial and error I found it necessary to disable Bluedevil in KDE and use Blueman to get the job done.

I have done quite a lot of research about this and this is what it is like now:

the bluetooth card is ID 413c:8160 Dell Computer Corp. Wireless 365 Bluetooth,

I have another dell laptop which has exactly the same Slackware 14 system, 64bit multilib
but has another Bluetooth card inside : ID 413c:8156 Dell Computer Corp. Wireless 370 Bluetooth Mini-card,
which is working OK.

Having in mind that the 413c:8160 Dell Wireless 365 Bluetooth used to work with Slackware 13.37 - this may be
more than some config problem. More so the bluez stack is now on Dbus, this could be a Dbus connection issue as well.

On working Bluetooth comp. "hciconfig -a" gives:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1F:E1:BE:27:37 ACL MTU: 1021:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:1111 acl:0 sco:0 events:38 errors:0
TX bytes:896 acl:0 sco:0 commands:38 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'studio-0'
Class: 0x5a0100
Service Classes: Networking, Capturing, Object Transfer, Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.1 (0x4) Revision: 0x5115
LMP Version: 2.1 (0x4) Subversion: 0x423d
Manufacturer: Broadcom Corporation (15)

And on the Non-working comp:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:25:56:E0:7A:2A ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING PSCAN ISCAN
RX bytes:1307 acl:0 sco:0 events:54 errors:0
TX bytes:967 acl:0 sco:0 commands:54 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'jastreb-inspiron-0'
Class: 0x5a0100
Service Classes: Networking, Capturing, Object Transfer, Telephony
Device Class: Computer, Uncategorized
HCI Version: 2.1 (0x4) Revision: 0x50ad
LMP Version: 2.1 (0x4) Subversion: 0x423d
Manufacturer: Broadcom Corporation (15)

The only obvious difference is the HCI Version, Revision number:
for the working card - 0x5115
and for the non-working card - 0x50ad, whatever it may mean!

On the non-working comp any hcitool command except "scan and inq" gives an error (input/output error).
I tried to compile a bluez-4.101 package, but it didn't change anything. This cannot be hardware issue
because the card is working OK in Win7.

Looks more like a firmware issue, or a Dbus issue, or a kernel driver issue.
Both computers have the same kernel 3.2.29.
Maybe I should try a different kernel?