Bug 550538 - Files sent by gnome-bluetooth arrive corrupted
Summary: Files sent by gnome-bluetooth arrive corrupted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-bluetooth
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Bastien Nocera
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-25 22:30 UTC by Pedro Matiello
Modified: 2010-06-08 19:31 UTC (History)
3 users (show)

Fixed In Version: obexd-0.12-2.fc11
Clone Of:
Environment:
Last Closed: 2010-03-16 00:39:28 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
corrupt audio file. (4.36 MB, audio/mp3)
2010-02-04 05:54 UTC, Ankur Sinha (FranciscoD)
no flags Details

Description Pedro Matiello 2009-12-25 22:30:11 UTC
Description of problem:
Files sent by gnome-bluetooth arrive corrupted

Version-Release number of selected component (if applicable):
gnome-bluetooth-2.28.3-1.fc12.x86_64

How reproducible:
Always. Tested with a Nokia cellphone and a Macbook running OS X.

Steps to Reproduce:
1. Pair with a cellphone or another computer.
2. Right-click some file on nautilus and click Send to
3. Select the appropriate bluetooth device and send.
  
Actual results:
Files arrive corrupted on destiny. No errors are reported.

Expected results:
No corruption.

Additional info:
It doesn't seem to be a Fedora-only bug. There's a little more on this launchpad thread:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/474397

Comment 1 Bastien Nocera 2010-01-09 12:38:50 UTC
Can you reproduce the problem using obexd's test program:
/usr/share/doc/obexd-*/send-files

Comment 2 Ankur Sinha (FranciscoD) 2010-02-04 05:48:59 UTC
(In reply to comment #1)
> Can you reproduce the problem using obexd's test program:
> /usr/share/doc/obexd-*/send-files    

hi,

I have the same problem. I'm attaching the file that my phone received. you'll notice it sounds choppy. I used obexftp --put to send the file and this dint happen. I havent tried with obexd yet, will try and post.

regards,
Ankur

Comment 3 Ankur Sinha (FranciscoD) 2010-02-04 05:54:44 UTC
Created attachment 388712 [details]
corrupt audio file.

this is the corrupt audio file that my phone recieved when i used the rightclick> send via bluetooth method.

Comment 4 Ankur Sinha (FranciscoD) 2010-02-04 06:07:11 UTC
hi,

i tried with send-files. Same output. The file is choppy. (I sent the same source file again to be sure)

using obexftp, the same source file came out fine, no glitches, no corruption.

regards,
Ankur

Comment 5 Bastien Nocera 2010-02-15 17:24:48 UTC
(In reply to comment #4)
> hi,
> 
> i tried with send-files. Same output. The file is choppy. (I sent the same
> source file again to be sure)

So the file gets corrupted when using obexd's send-files as well?

Which version of obexd are you using?

Comment 6 Pedro Matiello 2010-02-15 18:22:36 UTC
Sorry for the (very) late reply.

I still have the issue with an fully updated Fedora 12. Sending with obexftp works fine.

[pedro@pmatiello-notebook ~]$ rpm -qa | grep obex
gvfs-obexftp-1.4.3-4.fc12.x86_64
obexd-0.19-1.fc12.x86_64
obex-data-server-0.4.3-4.fc12.x86_64
obexftp-libs-0.23-2.fc12.x86_64
openobex-1.4-4.fc12.x86_64
obexftp-0.23-2.fc12.x86_64

Comment 7 Ankur Sinha (FranciscoD) 2010-02-16 05:01:17 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > hi,
> > 
> > i tried with send-files. Same output. The file is choppy. (I sent the same
> > source file again to be sure)
> 
> So the file gets corrupted when using obexd's send-files as well?
> 
> Which version of obexd are you using?    

[Ankur1@localhost ~]$ rpm -q obexd
obexd-0.19-1.fc12.x86_64


choppy for " > /usr/share/doc/obexd-*/send-files    "

Ankur

Comment 8 Fedora Update System 2010-03-08 16:09:48 UTC
obexd-0.12-2.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/obexd-0.12-2.fc11

Comment 9 Fedora Update System 2010-03-08 16:25:02 UTC
obexd-0.19-2.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/obexd-0.19-2.fc12

Comment 10 Fedora Update System 2010-03-08 16:34:44 UTC
obexd-0.21-2.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/obexd-0.21-2.fc13

Comment 11 Fedora Update System 2010-03-10 06:40:29 UTC
obexd-0.12-2.fc11 has been pushed to the Fedora 11 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update obexd'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/obexd-0.12-2.fc11

Comment 12 Fedora Update System 2010-03-10 06:49:19 UTC
obexd-0.19-2.fc12 has been pushed to the Fedora 12 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update obexd'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/obexd-0.19-2.fc12

Comment 13 Fedora Update System 2010-03-10 06:49:59 UTC
obexd-0.21-2.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update obexd'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/obexd-0.21-2.fc13

Comment 14 Adam Williamson 2010-03-10 18:17:12 UTC
can you guys please test the submitted updates on your release of Fedora and see if they solve the problem, and provide feedback via the admin.fedoraproject links? Thanks!

Comment 15 Fedora Update System 2010-03-16 00:39:21 UTC
obexd-0.19-2.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 16 Fedora Update System 2010-06-08 19:31:32 UTC
obexd-0.12-2.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.