Sending files over Bluetooth fails

Bug #447836 reported by Dimitris Kogias
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
obexftp (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: obexftp

In Jaunty, using obexftp version 0.19-7ubuntu2 I can send files to my Nokia E71/N95 using obexftp in both these two ways:

obexftp -b xx:xx:xx:xx:xx:xx -p file.pdf
obexftp -b <friendly_name> -p file.pdf

In Karmic however, both fail:

d@detritus:~/tmp$ obexftp -b <friendly_name> -p file.pdf
Scanning for <friendly_name> ...
Seen: aa:aa:aa:aa:aa:aa
Seen: bb:bb:bb:bb:bb:bb
Seen: xx:xx:xx:xx:xx:xx
Browsing <friendly_name> ...
Connecting...failed: connect
error on connect(): Invalid argument
Still trying to connect
Connecting...failed: connect
error on connect(): Invalid argument
Still trying to connect
Connecting...failed: connect
error on connect(): Invalid argument
Still trying to connect

In this case, the mobile doesn't even seem to receive the (browse? OBEX push?) request. I'm saying that because although it and the Karmic host are paired, the Karmic host is not trusted on the mobile (neither is the Jaunty host).

Trying without the friendly name:

d@detritus:~/tmp$ obexftp -b xx:xx:xx:xx:xx:xx -p file.pdf
Browsing xx:xx:xx:xx:xx:xx ...
Connecting..\done
Sending "file.pdf"...-failed: file.pdf
Disconnecting..\done

In this case the mobile did respond to the OBEX push, and once authorized the transfer "seemed" to happen - the "spinner" was moving. However the transfer fails at the end.

ProblemType: Bug
Architecture: amd64
Date: Sat Oct 10 00:32:48 2009
DistroRelease: Ubuntu 9.10
Package: obexftp 0.22-1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.43-generic
SourcePackage: obexftp
Uname: Linux 2.6.31-13-generic x86_64

Revision history for this message
Dimitris Kogias (dimitris-k) wrote :
Revision history for this message
Dimitris Kogias (dimitris-k) wrote :

Update:

If I manually specify the bluetooth MAC *and* the correct channel for the OBEX FTP service, the push works:

Service Name: OBEX File Transfer
Service RecHandle: 0x1000c
Service Class ID List:
  "OBEX File Transfer" (0x1106)
Protocol Descriptor List:
  "L2CAP" (0x0100)
  "RFCOMM" (0x0003)
    Channel: 11
  "OBEX" (0x0008)
Language Base Attr List:
  code_ISO639: 0x454e
  encoding: 0x6a
  base_offset: 0x100
Profile Descriptor List:
  "OBEX File Transfer" (0x1106)
    Version: 0x0100

obexftp -b xx:xx:xx:xx:xx:xx -B 11 -p <file>

succeeds.

Revision history for this message
Philippe Coval (rzr) wrote :

I confirm dimitris' workaround works (on nokia E61 at least) ,
btw how to discover existing chanels ?

Revision history for this message
Dimitris Kogias (dimitris-k) wrote :

You can get the current channels for all services by running:

sdptool browse <device BT address>

Revision history for this message
Philippe Coval (rzr) wrote :

Ok thanks seems it's 11 on nokia and 4 on SonyErricson ... have fun with awk and grep now ...

Revision history for this message
Dimitris Kogias (dimitris-k) wrote :

Same failure mode under Lucid, obexftp package 0.23-1

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in obexftp (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.