When g-p-m fails the first attempt to connect via Bluetooth it will keep printing "** Message: Can't connect twice" even if you change port in the Preferences.

I would expect it to print an error message that doesn't suggest a connection has bee already established and to try to connect to another device if I change settings.

I think this is different from Bug #495278 where failure to reconnect happens after successful connections, here all attempts fail.

Steps to reproduce:
1. configure g-p-m and phone for Bluetooth connection (make sure it works)
2. exit g-p-m and turn phone Bluetooth off
3. start g-p-m --debug and it prints (I added a g_message() to show app->status):
** Message: bdaddr 00:1A:75:D7:C4:69
** Message: New connection device is 00:1A:75:D7:C4:69 (changed)
** Message: app->status 0
** Message: New connection device is 00:1A:75:D7:C4:69 (not changed)
** Message: Connecting...
** Message: Status 1
** Message: Making serial port connection
** Message: Using serial channel -1 for device 00:1A:75:D7:C4:69
** Message: Failed connection to device on 00:1A:75:D7:C4:69
** Message: Exiting connect thread

[it apparently stops here forever, open Preferences and close it without changes]

** Message: New connection device is 00:1A:75:D7:C4:69 (not changed)
** Message: app->status 1
** Message: Can't connect twice

[open Preferences and change port settings]

** Message: New connection device is /dev/ttyS0 (changed)
** Message: app->status 1
** Message: Can't connect twice