Bugzilla – Bug 691094
Sending files via KDE bluetooth applet (OBEX) fails
Last modified: 2011-05-02 16:35:17 UTC
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.0) Gecko/20100101 Firefox/4.0 When trying to send a file a progress bar in the notification area of the KDE panel pops up but nothing is sent. Manually sending a file via obexftp -v -b <BT_ADDR> --noconn --uuid none --nopath --put <FILE> works. Receiving files does work, too. Perhaps this related to bug 680770 ? Reproducible: Always Steps to Reproduce: 1. Right click bluetooth icon in system area of panel 2. Select "Send file" 3. Select target devive and file in wizard that pops up Actual Results: Progress bar in notification area is shown. But the bar doesn't move and no file is sent. The target device doesn't see anything. Expected Results: The file should be sent.
RPMs installed: $ rpm -qa | grep blue | sort bluedevil-1.0.2-3.8.1.x86_64 bluez-4.88-2.1.x86_64 libbluedevil1-1.8-3.1.x86_64 libbluetooth3-4.88-2.1.x86_64 pulseaudio-module-bluetooth-0.9.22-6.11.1.x86_64 As for the logs I couldn't find anything that seemed helpful. If there's more information I can provide, I'd be happy to do so.
Have you installed obexd-client?
(In reply to comment #2) Thanks for the quick reply. > Have you installed obexd-client? No, it wasn't installed. After installing it (and the 14 other packages it pulled in as dependencies) sending the file works as expected. :-) So I guess the issue is more of a dependency issue. If you do touch the dependencies, could you perhaps find a way not having to install half of the evolution packages? "zypper install obexd-client" pulled in these packages on my system: evolution-data-server libcamel-1_2-19 libebackend-1_2-0 libebook-1_2-10 libecal-1_2-8 libedata-book-1_2-8 libedata-cal-1_2-10 libedataserver-1_2-14 libegroupwise-1_2-13 libgdata7 libgweather libgweather1 obexd obexd-client pidgin-evolution
That huge list of dependencies is the reason why this dependency was not simply added. There was somebody looking how to decrease the list, but it turned out that it was not so simple. I am not sure really sure what the status is at the moment. *** This bug has been marked as a duplicate of bug 675398 ***