Bug 306632 - kde bluetooth wizard should bind rfcomm serial devices
Summary: kde bluetooth wizard should bind rfcomm serial devices
Status: CONFIRMED
Alias: None
Product: Bluedevil
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-11 19:55 UTC by manolis
Modified: 2023-01-03 12:13 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description manolis 2012-09-11 19:55:54 UTC
I wish there should be an option in kde bluetooth to automatically bind a serial bluetooth device (like a gps) to rfcomm devices.
At present there is no way to configure such devices with the gui, and you have to use the terminal to bind a hotplugged serial bluetooth device.


Reproducible: Always

Steps to Reproduce:
1. Connect a serial bluetooth device
2.
3.
Actual Results:  
KDE Bluetooth wizard cannot handle such device.

Expected Results:  
KDE Bluetooth wizard should give an option to add automatically or semi-automatically the expected rfcommX device.
Comment 1 Alex Fiestas 2012-12-30 16:06:47 UTC
Can you tell me which gps device are you using? 

Thanks.
Comment 2 manolis 2013-01-02 10:40:47 UTC
"hcitool scan" gives me that:

00:1C:88:11:1C:AB       Teleprovodnik GPS

Manually I can connect to gps, and use it in linux.
It would be great if there was a serial rfcomm binding wizard in bluedevil as in windows.
Comment 3 manolis 2013-01-02 10:46:39 UTC
"hcitool scan" gives me that:
 00:1C:88:11:1C:AB Teleprovodnik GPS 

Manually I can connect to gps, and use it in linux. It would be great if there was a serial rfcomm binding wizard in bluedevil as in windows.

I don't understand why the device is related. Is this feature implemented already, and does not work in my gps? It's a wish not a bug report.
Comment 4 Alex Fiestas 2013-03-03 14:56:18 UTC
Indeed we are not working with serial,  will try to fix for next release.
Comment 5 Kishore 2013-05-17 03:22:27 UTC
I would also like to see rfcomm management from the GUI.
Comment 6 Paul Jewell 2013-05-27 18:22:42 UTC
I would also like to see this capability so I don't have to manage rfcomm devices manually.
Comment 7 Artur 2015-03-08 16:03:35 UTC
(In reply to Alex Fiestas from comment #4)
> Indeed we are not working with serial,  will try to fix for next release.

Is this working? 
I can't bind to Bluetooth UART 00:06:66:67:E1:74 
https://www.sparkfun.com/products/12576
Comment 8 David Rosca 2015-03-11 16:24:56 UTC
(In reply to Artur from comment #7)
> Is this working? 
> I can't bind to Bluetooth UART 00:06:66:67:E1:74 
> https://www.sparkfun.com/products/12576

No, it is not working and is probably out of scope because there is no support for it in Bluez DBus API.
You should use "rfcomm" utility instead.
Comment 9 stu109382 2015-10-23 18:48:30 UTC
I would also like to have a serial connection via bluetooth shipped with KDE.

I use this to connect an arduino to my linux laptop. At the moment I am using blueman to open a serial connection with the HC-05 module.
Comment 10 Justin Zobel 2021-03-09 05:49:51 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 11 Nikolai Försterling 2023-01-03 12:13:44 UTC
Here (Kubuntu 22.04, Plasma 5.25.5) the issue still persists, the common bluetooth stack can't connect to my device (Columbus V900 GPS Data Logger) even before i'm able to manually use rfcomm to connect a serial port.
[bluetooth]# connect 00:18:E4:1F:5E:1F
Attempting to connect to 00:18:E4:1F:5E:1F
[CHG] Device 00:18:E4:1F:5E:1F Connected: yes
[CHG] Device 00:18:E4:1F:5E:1F ServicesResolved: yes
Failed to connect: org.bluez.Error.NotAvailable br-connection-profile-unavailable
[CHG] Device 00:18:E4:1F:5E:1F ServicesResolved: no
[CHG] Device 00:18:E4:1F:5E:1F Connected: no
[bluetooth]# info 00:18:E4:1F:5E:1F
Device 00:18:E4:1F:5E:1F (public)
Name: GPS Data Logger
Alias: GPS Data Logger
Class: 0x00001f00
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port               (00001101-0000-1000-8000-00805f9b34fb)

I tried blueman which can connect the serial port (under X11), but unfortunately segfaults under wayland.