Trying to send files over Bluetooth gives "Connection Refused (111)"

[Ian Santopietro]

After pairing a device (Computer, Smartphone, etc.) to an Ubuntu 11.10 machine, it is not immediately possible to send a file to the device over bluetooth.

Ubuntu 11.10 AMD64, using bluez 4.96-0ubuntu4.

3: Upon initiating the file transfer, the file should be sent to the remote device.

4: Upon initiating the file transfer, an error message appears indicating "Connection Refused (111)". Subsequently retrying several times in quick succession will transfer the file.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: bluez 4.96-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
Date: Wed Nov 9 15:45:06 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterestingModules: btusb bnep rfcomm bluetooth
MachineType: System76, Inc. Serval Professional
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=94f7fc1e-fa27-4b24-99f3-4b461665a4a4 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.4
dmi.board.asset.tag: Not Applicable
dmi.board.name: Serval Professional
dmi.board.vendor: System76, Inc.
dmi.board.version: serp7
dmi.chassis.asset.tag: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: serp7
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd01/18/2011:svnSystem76,Inc.:pnServalProfessional:pvrserp7:rvnSystem76,Inc.:rnServalProfessional:rvrserp7:cvnSystem76,Inc.:ct10:cvrserp7:
dmi.product.name: Serval Professional
dmi.product.version: serp7
dmi.sys.vendor: System76, Inc.
hciconfig:
 hci0: Type: BR/EDR Bus: USB
  BD Address: 74:F0:6D:E0:27:FF ACL MTU: 310:10 SCO MTU: 64:8
  UP RUNNING PSCAN ISCAN
  RX bytes:14758 acl:222 sco:0 events:519 errors:0
  TX bytes:11218 acl:234 sco:0 commands:120 errors:0

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[kkraju4u (kkraju4u)]

me too having the same problem.
using blueman, it says "Method "CreateBluetoothSession" with signature "vvs" on interface "org.openobex.Manager" doesn't exist"

dell inspiron n5110 ubuntu 11.10

[Jan Bee (jbe-g)]

I was able to reproduce this in kernel 3.0 and 3.2. This seems to be a timing issue and can be isolated in a simple socket-connection (using python-lightblue in this case):

sock = lightblue.socket()
sock.connect((addr, port))
# adding a sleep of a couple of seconds made it work more reliable
sock.send(data)

stracing that shows:

socket(PF_BLUETOOTH, SOCK_SEQPACKET, 0) = 4
connect(4, {sa_family=AF_BLUETOOTH, sa_data="\1\0\317,\17\234\320\260\0\0\0\0\0\0"}, 12) = 0
// and right afterwards:
socket(PF_BLUETOOTH, SOCK_STREAM, 3) = 4
connect(4, {sa_family=AF_BLUETOOTH, sa_data="\317,\17\234\320\260\10\0\0\0\0\0\0\0"}, 10) = -1 ECONNREFUSED (Connection refused)

[3vi1 (launchpad-net-eternaldusk)]

"Subsequently retrying several times in quick succession will transfer the file." - I can confirm seeing this too. However, thanks to the wonderful bluetooth implementation in my fully updated Blackberry Torch, retrying multiple times in rapid succession is 99.999% guaranteed to cause the phone to crash and reboot. :\

[Ian Santopietro (isantop)]

Testing this in 12.04 to see if it's fixed:

Appears to work just fine on my machine.

System76 Pangolin Performance (PanP7)

ID:0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI Mode)

Sent to Samsung Google Galaxy Nexus CDMA i515

[Mathieu Trudel-Lapierre (cyphermox)]

I agree, it seems to be as though we've fixed this (via another bug) in Precise. Is anyone still seeing such issues, and if so, we'd need a copy of /var/log/syslog at least to figure out what is going on.

[Mathieu Trudel-Lapierre (cyphermox)]

We've had no answers for a while with regards to this particular issue. Since there has been reports that it was fixed, I'll mark this bug as Fix Released for Ubuntu. Thanks!