bluetooth file transfer data inconsistency

[Matthew]

Hello,

I am using Ubuntu Karmic, with gnome environment. When I send a file via bluetooth, it's seems everything goes fine, no error reported in neither side, but still, something wrong.
I can't open any of received file on my phone (K800i), or if i can, it's seem clearly the file is damaged.
I compared the original, and the sent file, and I experienced that both sizes are equal, but when I used a binary diff utility (vbindiff) the light is thrown on the binary difference between these files.
I don't know exactly where is the problem, and what further information I should provide you.
If I can do something more to move forward, please let me know,

Matthew

[Sean (svz90)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in gnome-bluetooth.
For future reference you might be interested to know that a lot of applications have bug reporting functionality built in to them. This can be accessed via the Report a Problem option in the Help menu for the application with which you are having an issue. You can learn more about this feature at https://wiki.ubuntu.com/ReportingBugs.

[Matthew (matthew-linux)]

Thank you for your reply, i have some news.

My friend was upgraded his ubuntu today, and we experiented the same problame, with some differences, that could help us.
He have two phone, a Sony Ericcson, and a Samsung. I tryed the file transfer both on them, and this time also no error reported neither phone. On SE the file was demaged, like in my case (I also have a SE, as I mentioned previously), but the Samsung recived the file correctly.

I also took an other experiment. I installed the obexftp package, and I sent the file with it. The file was recived on both phone correctly, so my opinion is, the bug must somewhere in the bluetooth management of gnome, or maybe an incompatibily in the protocoll.

Matthew

[Ben (benmoss1)]

Same problem here.

I have tried two different machines with Ubuntu 9.10 and both behave the same. I would also say that is problem really only started to affect me after the 11th or 12th of Nov 2009.. It was working fine for me till that point. I am developing J2ME programs, so I transfer for testing regularly. Program files may also be less tolerant to errors.

Further as mentioned above, it seems to not affect some phones.
Motorola v535 still works fine. No apparent errors. The programs transferred work as expected.
LG KU990 does not work anymore.. All programs transfered to this phone will arrive corrupted.

One machine was tested multiple times using alternate transfers using Windows and then Ubuntu 9.10 in turn. Transfers were ok with windows and corrupted with Ubuntu 9.10. So hardware failure would seem ruled out.

Ben

[Sean (svz90)]

Same problem when transferring files from my Ubuntu system to my Mac: files transferred via the gnome-bluetooth system are corrupted.

[effell (effell)]

Also experiencing the same bug when moving files from Ubuntu 9.10 to a palm phone.

Two different files arrived at the palm with copies of their own first 256+12=268 bytes
written onto themselves at locations 3828, 7656, 11484, 15312, 19140, etc. (thats
every 3828d bytes)

[Jeremy Visser (jeremy-visser)]

Having the same problem. Bluetooth file transfers are corrupted with my phone (ZTE F252), but work fine to a friend's (Motorola MQ5-4411A). When he then sends from his Motorola phone to ZTE, the file transfers work fine.

[Biji (biji)]

i experience this bug too... sent to motorola v8 and k810i both CORRUPT!

[Biji (biji)]

any workaround?

[Sant (sant)]

The latest version of Blueman solves this problem.You will have to add the ppa repository of Blueman:
http://blueman-project.org/downloads.html
https://edge.launchpad.net/~blueman/+archive/ppa

[Nicolò Chieffo (yelo3)]

Does Blueman have anything to do with gnome bluetooth?

[Sean (svz90)]

No. However, you can remove gnome-bluetooth, and install blueman as an alternative.

As another option, as Matthew said in comment #2, you can use the obexftp program to transfer files.

[Sant (sant)]

If you install Blueman gnome-bluetooth is automatically removed.

[clubsoda (clubsoda)]

I think effell has hit the nail on the head, although I am getting slightly different numbers for the locations of the corrupt regions:-
0x0f38-0x0fff (inclusive)
0x1e70-0x1f37
0x2da8-0x2e6f
i.e. The first 200 bytes of the file are overwriting the original data at intervals of 3896 bytes.
This is almost certainly an error in obexd's "Resizing stream chunks to 3896" (from 4096).

See also:-
http://bugs.gentoo.org/297624
Perhaps this was first noted in October 2008:-
http://article.gmane.org/gmane.linux.bluez.devel/16186

Cheers.

[Nicolò Chieffo (yelo3)]

Now bluetooth seems to send correct files in lucid. have you upgraded?

[Sean (svz90)]

Added watch for same bug in Fedora.

[Baptiste Mille-Mathias (bmillemathias)]

Hello,

Could someone test the package obexd-client I have in my ppa, it seems to fix the corruption issue.
My ppa id is ppa:bmillemathias/ppa.
Just install the obexd-client package and not the other bluetooth related package (because they could cause other defect).

kill all obex processes, and try sending the file as you did before, and post result here.

Thanks.