Bluetooth works fine for me with GNOME 3.12, so it is definitely not completely broken. Does it work when used on the command line, i.e. is really gnome-bluetooth the culprit here, or is there something wrong further down the Bluetooth stack? What else have you upgraded? Have you tried to reboot your computer? Some Bluetooth adapters tend to "die" from time to time, requiring a reboot.

As for me, bluetooth works almost 100%. The only thing I cannot do is receive files from my tablet, albeit I CAN send files from my laptop to my tablet. I observed the output of 'journalctl -f' while I tried to send a picture from my tablet and this was the output:

Apr 17 00:56:20 maxwell obexd[8033]: CONNECT(0x0), (null)(0xffffffff)
Apr 17 00:56:20 maxwell obexd[8033]: CONNECT(0x0), (null)(0x0)
Apr 17 00:56:21 maxwell obexd[8033]: PUT(0x2), (null)(0xffffffff)
Apr 17 00:56:21 maxwell obexd[8033]: PUT(0x2), FORBIDDEN(0x43)
Apr 17 00:56:21 maxwell obexd[8033]: DISCONNECT(0x1), (null)(0xffffffff)
Apr 17 00:56:21 maxwell obexd[8033]: DISCONNECT(0x1), SUCCESS(0x20)
Apr 17 00:56:21 maxwell obexd[8033]: disconnected: Transport got disconnected

The file does not show up in "~/Downloads" and on my Android-powered tablet a message says there was a 'connection problem'.

I don't know if:

1. It's a bug in bluez
2. It's a bug in gnome-bluetooth
3. Something is wrong with my bluetooth adapters (either on the laptop or tablet)

Maybe, we should rebuild gnome-shell for /usr/lib/libgnome-bluetooth.so.13.0.0?

Apr 18 10:37:02 pc2007 org.gnome.Nautilus.SearchProvider[1511]: ** (nautilus:1962): WARNING **: libgnome-bluetooth.so.12: cannot open shared object file: No such file or directory

At least nautilus-search-provider (used from gnome-shell, nautilus, …) uses the wrong libgnome-bluetooth Version.

@Stefan,

gnome-shell-3.12.1-1 did the trick - I have /usr/lib/libgnome-bluetooth.so.13.0.0 on my system... and now receiving files from my tablet works! :)

@Karol,

are you still having problems?

After the upgrade to 3.12 every time I try to toggle on the bluetooth switch in the GNOME Control Center it toggles off again immediately. The command 'journal -fu bluetooth.service' yields:

Apr 22 15:32:10 heidegger bluetoothd[558]: Bluetooth management interface 1.4 initialized
Apr 22 15:32:27 heidegger bluetoothd[558]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSource
Apr 22 15:32:27 heidegger bluetoothd[558]: Endpoint registered: sender=:1.42 path=/MediaEndpoint/A2DPSink
Apr 22 15:32:27 heidegger bluetoothd[558]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSource
Apr 22 15:32:27 heidegger bluetoothd[558]: Endpoint registered: sender=:1.24 path=/MediaEndpoint/A2DPSink
Apr 22 15:32:28 heidegger bluetoothd[558]: Wrong size of start discovery return parameters
Apr 22 15:32:28 heidegger bluetoothd[558]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSource
Apr 22 15:32:28 heidegger bluetoothd[558]: Endpoint unregistered: sender=:1.42 path=/MediaEndpoint/A2DPSink
Apr 22 15:32:28 heidegger bluetoothd[558]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSource
Apr 22 15:32:28 heidegger bluetoothd[558]: Endpoint unregistered: sender=:1.24 path=/MediaEndpoint/A2DPSink


The output of 'rfkill list' is:

0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

Edit:

This is on a Thinkpad T420 (not on a T440s as previously stated, sorry.)

For those who cannot connect, what happens if you try to connect using bluetoothctl? Install the bluez-utils package. Then in a terminal run these commands:

bluetoothctl
power on
connect <dev>

where <dev> is the device's mac address.

If this fails then that indicates that the problem is not with gnome-bluetooth but with bluez itself.

What kind of device are you folks having problems with? A Phone or Tablet that can be used as a bluetooth hotspot? For those devices to connect, I suggest:

1. Remove them with gnome-bluetooth or bluetoothctl
2. Remove all files related to these devices in /etc/NetworkManager/system-connections
3. Pair these devices again
4. Use them as a network device. This should establish a stable connection. Then you can connect them as an audio sink and there will be no more trouble.

That's how I got my particular device to work with gnome, pulseaudio and bluez...

@Chazza: the command "power on" in bluetoothctl only gives me "No default controller available".

@lmello: I don't even get to the point of connecting. The switch in gnome-control-center just toggles off again after I try to toggle in on.

@andre,

If you get "No default controller available" in bluetoothctl, then something is wrong with bluez not recognizing your hardware, so it's not a problem in gnome-bluetooth.

EDIT:

Have you tried as root:

# systemctl daemon-reload
# systemctl restart bluetooth.service

?

@lmello,

yes, but with no success.

My problem has been solved and was totally my fault. I wrote a faulty custom systemd service that disables the bluetooth after the bluetooth.service is started. I changed it, so that it only runs after the multi-user.service is started.

Thanks again for your efforts!