From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051118 Fedora/1.5-0.5.0.rc3 Firefox/1.5 Description of problem: When a jpeg file form my RAZR phone is being uploaded using gnome-obex-server, the server crashes with the message: conn_request: bdaddr 00:12:8A:63:14:3B conn_complete: status 0x00 ** Message: Incoming connection from 00:12:8A:63:14:3B ** Message: Device 00:12:8A:63:14:3B is about to send an object. *** glibc detected *** gnome-obex-server: double free or corruption (fasttop): 0x08b88150 *** .....[see attachment] According to this message: http://lists.gnomehack.com/pipermail/gnome-bluetooth/2005-October/000996.html this is a known bug fixed in cvs. Version-Release number of selected component (if applicable): gnome-bluetooth-0.6.0-2 How reproducible: Always Steps to Reproduce: 1. Start blue-tooth subsytem 2. Start gnome-obex-server 3. Send a file from your phone Actual Results: The gnome-obex-server crashes Expected Results: The file should be transferred or there should be dialog box asking if you want to receive the file Additional info:
Created attachment 121545 [details] Output from gnome-obex-server This a known bug fixed in CVS
These bugs are being closed since a large number of updates have been released after the FC5 test1 and test2 releases. Kindly update your system by running yum update as root user or try out the third and final test version of FC5 being released in a short while and verify if the bugs are still present on the system .Reopen or file new bug reports as appropriate after confirming the presence of this issue. Thanks
I have seen this bug with gnome-bluetooth-0.6.0 on core 4 and devel, but for me it's fixed in 0.7.0. File Transfer works fine again. Is there any chance to also get an update for core 4? I was able to rebuild the libbtcl-0.6.0 and gnome-bluetooth-0.7.0 by simply lowering the openobex BR from 1.1 to 1.0.1.
Please test http://www.redhat.com/archives/fedora-test-list/2006-May/msg00152.html
and http://www.redhat.com/archives/fedora-test-list/2006-May/msg00153.html
Yes, for me it's fixed in 0.7.0. Closing.