GNOME Bugzilla – Bug 602409
automatically reconnect to the last used audio device
Last modified: 2013-12-12 14:25:52 UTC
Pairing/connecting to my bluetooth speakers through the bluetooth applet works fine. However, when I restart the computer, I need to manually reconnect to my audio device in order to use it again. Ideally, the bluetooth applet should automatically reconnect to the last used audio device when it starts up.
Just my 2 cents: i think this should be an opt-in on a per-device basis. I wouldnt want my bluetooth devices auto-connected only because I have previously paired it. Ideally you'll get an additional question in the pairing wizard "Would you like to automatically connect this device from now on?" and a complementary checkbox in the "paired devices" dialog. This would be useful for example bluetooth printers too (just speculating, i dont know how a bluetooth printer behaves with gnome-bluetooth)
The Bluetooth device (the speakers) are supposed to reconnect to the computer when you turn it on, so this shouldn't be necessary. (In reply to comment #1) > Just my 2 cents: i think this should be an opt-in on a per-device basis. > I wouldnt want my bluetooth devices auto-connected only because I have > previously paired it. > > Ideally you'll get an additional question in the pairing wizard "Would you like > to automatically connect this device from now on?" and a complementary checkbox > in the "paired devices" dialog. > > This would be useful for example bluetooth printers too (just speculating, i > dont know how a bluetooth printer behaves with gnome-bluetooth) Printers don't need to be connected, the computer connects automatically to them when you print, and that's it. Just like you're not always connected to a network printer.
(In reply to comment #2) > The Bluetooth device (the speakers) are supposed to reconnect to the computer > when you turn it on, so this shouldn't be necessary. I think this is the key point. Currently, the computer doesn't connect the known bluetooth devices when they are powered on. I have a bluetooth headset (Motorola S305). When I power on, the computer sees it, tries to connect to it but fails all the time. I have to manually connect the headset. It's certainly a bug, but before it is fixed, the behavior is not what we expect.
(In reply to comment #3) > (In reply to comment #2) > > The Bluetooth device (the speakers) are supposed to reconnect to the computer > > when you turn it on, so this shouldn't be necessary. > > I think this is the key point. Currently, the computer doesn't connect the > known bluetooth devices when they are powered on. > > I have a bluetooth headset (Motorola S305). When I power on, the computer sees > it, tries to connect to it but fails all the time. The computer tries to connect to the headset? That's not something we've setup... > I have to manually connect > the headset. > It's certainly a bug, but before it is fixed, the behavior is not what we > expect. Reading the device's manual, I see that it's supposed to connect back to the computer/phone. There's also that snippet which you might want to try: > To clear the paired devices list in your headphones, > press and hold ">II" and "-" buttons for about 8 seconds. > The headphones are turned off upon clearing the list. In any case, we cannot start connecting to audio devices on start up, especially when in most cases they wouldn't be there, headphones should be the ones initiating the connection.
(In reply to comment #4) > The computer tries to connect to the headset? That's not something we've > setup... I didn't know that, thanks for the point. > Reading the device's manual, I see that it's supposed to connect back to the > computer/phone. There's also that snippet which you might want to try: > > To clear the paired devices list in your headphones, > > press and hold ">II" and "-" buttons for about 8 seconds. > > The headphones are turned off upon clearing the list. I just tried this. After clearing the list of paired devices, the headphones successfully connect to the computer the first time and fail the other times. I join the log from journalctl, I can see some "Connection refused" but I don't know if it's refused from the computer or the headphones...
Created attachment 264065 [details] Log from journalctl
That's weird: déc. 12 14:21:37 bart bluetoothd[599]: No agent available for request type 0 déc. 12 14:21:37 bart bluetoothd[599]: device_request_pin: Operation not permitted Which version of bluez/distro is that with? Was the wizard already running? A step-by-step reproducer would be appreciated, but that looks like a different bug. Best file a new bug against gnome-bluetooth which we can look into. There's also plenty of SELinux warnings. Try putting SELinux in permissive mode.
SELinux is already disabled and I'm on Fedora 20 with bluez 5.11. The log is a grep for bluetooth from "journalctl --since today". When I cleared the paired devices list in the headphones, I also remove the headphones from the paired devices in GCC. So I re-added it after that, turned it off and on with a successfull connection this first time. I will file a new bug for that. Thank you for your time!