http://bugzilla.opensuse.org/show_bug.cgi?id=961784 Bug ID: 961784 Summary: Bluez bluetooth support fails in pairing and gives erratic results Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: stakanov@freenet.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I have a problem here with pairing a Samsung E2152 Dual Sim Phone via bluetooth. When using a 10 year old pairing dongle with the 2.1 protocol it works after a bit of hassle with leap on a fix PC. But it fails or better gives totally and not understandable erratic results with leap on a X201 and a minicard WLAN/BT. What it does: in both cases the response is different. When pairing with the old dongle, on the screen of the PC is a number, on the phone there is a window with the number to be put in (with return as confirmation). If instead the newer card is used (laptop), on both laptop and phone there is appearing the same number concurrently with the question: does it correspond. If you say yes in the PC first the process aborts instantly. If you say yes in the phone and then in the PC then the pairing apparently succeeds. But the behavior of "associated, paired, trusted" is totally erratic as it seems. If I give the PC authorization to connect by default, it does connect but after short time it says time out. The laptop is also not able to correctly browse the phone. File transfer does not work reliably in the old dongle. It does not work at all with the new (3.0 Protocoll). Although both are connected (laptop and phone) it will not be possible to send files from the phone, instead the phone claims that connection to the PC is not possible (of course, it is connected, however it does not seem that this connection is correct and functional). Sometimes during pairing there may be a "protocol non supported" message, without me knowing what protocol would that be. It is not that I am dependent on this feature. But I wanted you to know that at least for not android smartphones of the "older generation" there is an issue with pairing and at least on machines with more recent dongle/btcard the sending of files does not work. I was able to achieve this functionality with the PC and the old dongle BUT the pairing alone was not sufficient. The device was "trusted" but not "associated". Actually, on the laptop, when it fails, in the window of "devices" it shows the device as "not trusted" and "not associated" with a hardware address. In the list of paired devices, it shows the very same device as trusted and associated. Under this conditions sending files does not work. -- You are receiving this mail because: You are on the CC list for the bug.