GNOME Bugzilla – Bug 672114
Unable to browse bluetooth device: Connection refused (111)
Last modified: 2015-03-04 15:36:32 UTC
When I try to browse a mobile phone via Bluetooth, I see this error: "Connection refused (111)", and the device cannot be browsed. I think the same error happened when I tried in XFCE with blueman. But Bluetooth works very well in KDE with Bluedevil and also in old GNOME 2.30, where I can browse, send and receive files from the mobile phone via Bluetooth, therefore something regarding bluetooth is broken in distributions based on Gnome3/Gtk3. This issue has been confirmed by some people with OpenSUSE, and Ubuntu, both with GNOME 3.2, and using these phones: Nokia, Blackberry, and Android. This is also reported in Launchpad against Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/891444 The only idea I have is that gnome-bluetooth and blueman may be using the wrong channel to connect with the device. How do they know about the right channel to use? If I mount my device filesystem with obexfs, I need to manually set the channel 10.
Hi Rafael, Thank you for the bug report. However, this bug was introduced in Debian. Upstream was never affected. If SUSE is affected, they must have taken the bad patch from Debian, or the other way around.
(In reply to comment #1) > Hi Rafael, > > Thank you for the bug report. However, this bug was introduced in Debian. > Upstream was never affected. If SUSE is affected, they must have taken the bad > patch from Debian, or the other way around. Where did you get that from?
(In reply to comment #2) > (In reply to comment #1) > > Hi Rafael, > > > > Thank you for the bug report. However, this bug was introduced in Debian. > > Upstream was never affected. If SUSE is affected, they must have taken the bad > > patch from Debian, or the other way around. > > Where did you get that from? I tested the upstream version and it worked. Then we bisected and figured out that 05_shared_libdaemon.patch from Debian causes the issue. There are more details in the launchpad bug: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/891444
The right launchpad bug to read more information is: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/899858 OpenSUSE hasn't the 05_shared_libdaemon.patch and is suffering the same issue. Can you tell me any GNU/Linux distribution which is not affected by this bug in GNOME 3 because it is not diverging from upstream?
Fedora 16 is also affected, I just have checked it a moment ago.
I've read through the launchpad bug 899858 and it only confirms what I've discussed with Sebastien Bacher already. The discussion is going on about Debian patch 05_shared_libdaemon.patch (see also bug 561187) and possible clash of symbols of duplicate name, resolved by ld in random order, coming from libdbus-glib. I'm not going to investigate more since the gdbus port is around the corner and this issue will possibly go away. We would only have to watch for a possible symbol name clash again since with the gdbus port I left some internal functions the same name.
Sorry for the confusion, the "connection refused" and the "Error: DBus error org.freedesktop.DBus.Error.NoReply" are two different things. I mistakenly though this bug was related to the later when it's actually the former. Carry on.
Is this bug still unfixed? I cannot actually reproduce it in Ubuntu, nor in Debian. What about the rest of distributions?
Obexftp backend has been obsoleted in GNOME 3.10, because it is incompatible with Bluez 5, however limited bluetooth support is currently built-in in GNOME desktop.