unable to transfer files by bluetooth obex push from phone to kubuntu

Bug #664079 reported by lucck
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
bluedevil (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: bluedevil

I upgraded kubuntu from 10.04 to 10.10, and after upgrade I'm unable to send any files from remote device to the kubuntu 10.10 via Obex Push. When i tried to push the file from example for another phone or netbook with debian squeeze the file start transfer and just after start connection is dropped. I have configured BT properly , device is paired and obex server is enabled. Bellow are listed running obex processes:

lucck 2386 0.0 0.0 22220 1316 ? S 20:08 0:00 /usr/lib/obexd/obex-client
lucck 2848 0.0 0.0 90108 3364 ? S 20:20 0:00 /usr/bin/obex-data-server --no-daemon

I also included the logs from dbus-monitor tool.

Revision history for this message
lucck (lucjan-bryndza) wrote :
description: updated
summary: - unable to transfer files by obex push from phone to kubuntu
+ unable to transfer files by bluetooth obex push from phone to kubuntu
Revision history for this message
Ezio Vergine (virgolus) wrote :

Same issue for me.
I have an external usb dongle and I only send file from pc to phone.
With the old 10.04 I sent files quietly.
Kubuntu 10.10.

Revision history for this message
Linuxboy (linuxboy) wrote :

kubuntu 10.10, package bluedevil_1.0~rc4-0ubuntu2.1_i386.deb. Bluetooth send file works only from pc to phone, it is impossible to send a file from phone to pc. Note that the "browse phone" function works good, but if I try to use dolphin to copy file from phone to pc, the copy goes wrong very often.

Revision history for this message
Everthon Valadão (valadao) wrote :

If I do a pairing with my PC and phone, in the first time I can successfully send files from my phone to the PC (and vice-versa). After restarting the PC, if I try to send a file from my phone to the PC, I get a message "Connection FAIL", BUT, if I try it again, it succeed!

So, maybe the "bluetooth obex daemon" (or something like that) isn't running or ready at the first attempt, but at the second trial it is. If someone could instruct me what log files and debug info do you need to try to fix this problem, I'm happy to provide them.

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.