After my last update KDE, Dolphin and Konqueror can no longer browse bluetooth devices through obexftp.

It always stays at The device is busy, waiting....



Obexftp can access the same devices normally.

obexftp -b 00:xx:xx:xx:xx:78 -l

Code: Select all

Browsing 00:xx:xx:xx:xx:78 ...
Connecting..\done
Receiving "(null)"...|<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE folder-listing SYSTEM "obex-folder-listing.dtd">
<!--
 XML Coder, (C) 2001 Sony Ericsson Mobile Communications AB
-->
<folder-listing version="1.0"><folder name="Phone Memory"/>
<folder name="Memory Stick"/>
</folder-listing>
done
Disconnecting../done

kde4-config --version
Qt: 4.8.4
KDE Development Platform: 4.10.4
kde4-config: 1.0

Any ways to debug it?

This is the kioobexftp output.

Code: Select all

kioobexftp(14922) KioFtp::setHost: setHost:  "00-23-45-0c-62-78"
kioobexftp(14922) KioFtp::setHost: Waiting to stablish the connection
kioobexftp(14922) KioFtp::sessionClosed: Session closed:  "00:xx:xx:xx:xx:78"
kioobexftp(14922) KioFtp::listDir: listdir:  KUrl("obexftp://00-xx-xx-xx-xx-78")
kioobexftp(14922) KioFtp::blockUntilNotBusy: Blocking, kded is busy
kioobexftp(14922) KioFtp::blockUntilNotBusy: Blocking, kded is busy
...
kioobexftp(14922) KioFtp::blockUntilNotBusy: Blocking, kded is busy
kioobexftp(14922) KioFtp::blockUntilNotBusy: Blocking, kded is busy
kioobexftp(14922) KioFtp::blockUntilNotBusy: Blocking, kded is busy
kioobexftp(14922) KioFtp::blockUntilNotBusy: Blocking, kded is busy
...

Please file a bug report at bugs.kde.org, so ensure the maintainers are aware of the problem.

I did yesterday. For Solid, bluetooth-kio-obex. I am sure if I had to report it for KDED though.

https://bugs.kde.org/show_bug.cgi?id=321560

A single bug report should be sufficient - it has been assigned to the correct person in this case. You'll need to wait for their response at this point i'm afraid.

One other thing you could try though, is attempting to reproduce under a new user, after rebooting the system.

I have tested it with 3 different systems (ArchLinux to all of them). I will try and the new user suggestion.

Just tried with a fresh user. It's the same as before.

Okay, it is very likely a bug/regression in Bluedevil. You'll need to await for a response from the developers unfortunately.