Transfer failure (CreateBluetoothSession doesn't exist)

Bug #235824 reported by sebseb01
6
Affects Status Importance Assigned to Milestone
bluez-gnome (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: bluez-gnome

After a normal fail ("host down", I forget to turn on the device).
If I click on retry this error apears :
Method "CreateBluetoothSession" with signature "ssb" on interface "org.openobex.Manager" doesn't exist

I don't found any information in log files

Revision history for this message
Peter Belm (peterbelm) wrote :

I'm also seeing this error. Transfer would consistently fail before pairing, yet after pairing it will fail once then get this error.

The device I'm connecting to is a HTC Tytn II.

Revision history for this message
sebseb01 (sebseb01) wrote :

It's too with a HTC TyTN II

sebseb01 (sebseb01)
Changed in bluez-gnome:
status: New → Confirmed
Revision history for this message
sebseb01 (sebseb01) wrote : Re: Transfer failure to HTC TyTN II (CreateBluetoothSession doesn't exist)

With wich version of Windows mobile (i doesn't try with Windows Mobile 6.1, but he sovled other problem with bluethoot)

I'll try later

Revision history for this message
ariendj (ariendj) wrote :

Same problem with a Samsung SGH-E770 and a Nokia N70. Most probably this is not dependant on the model of the phone.

The Nokia doesn't even respond, it's just idle with its bluetooth on. Nothing happens (might be because it is already paired while the Samsung is not).

With the Samsung the "Host Down" message appears even though I'm still pairing (pairing - to me - indicates that the host is not down). After a retry I get the CreateBluetoothYadayada message. With the Samsung I end up with a 1kb empty file.

Revision history for this message
Mario Limonciello (superm1) wrote :

This should be fixed in the BlueZ Gnome 1.8 package that entered intrepid yesterday as well as the newer obex-data-server that got uploaded.

Changed in bluez-gnome:
status: Confirmed → Fix Released
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.