OpenSuSE 13.1 64 bit Blueooth issues

I just upgraded to OpenSuSE 13.1 64 bit and my Bluetooth is not working. I can not use my Logitech Bluetooth laser mouse. I can’t even pair the device. When I run the Bluetooth adapter configuration, it says that no Bluetooth adapters were found. I made sure to turn on my Bluetooth on my System76 Lemur Ultra Thin (lemu4) notebook PC. What’s going wrong here and how do I fix it?

On 2013-11-20 02:06, wellywu wrote:
>
> I just upgraded to OpenSuSE 13.1 64 bit and my Bluetooth is not working.
> What’s going wrong here
> and how do I fix it?

Please read the release notes.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

You need to do a full system update to get the required fix.

YaST (root password) / Software / Software Management / Options / Check "Allow Vendor Change"

Next while still in Software Management:

Package / All Packages / Update if newer version available / accept the many files that need an update.

Next you need to follow this blog for multimedia support:

openSUSE 13.1 Multi-media and Restricted Format Installation GuideThank You,

On 2013-11-20 03:16, jdmcdaniel3 wrote:

> You need to do a full system update to get the required fix.

Are you sure? Remember that the bluetooth stack is officially reported
as broken under 13.1 KDE. The release notes explain what to do.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Thank you James. I followed your instructions and my Logitech Bluetooth mouse works again.

You are very welcome. It was the recommended way to get all fixes including for Bluetooth. I have a BT mouse and it started working along with connecting to my smart phone. The actual fix came out too late to make it to the DVD, but was in the first batch of fixes put into the update repo. This update procedure should be followed the same way on all new installations no matter if you have a known issue or not to fix. I was very happy to help.

Thank You,

Carlos E. R. wrote:
> On 2013-11-20 03:16, jdmcdaniel3 wrote:
>
>> You need to do a full system update to get the required fix.
>
> Are you sure? Remember that the bluetooth stack is officially reported
> as broken under 13.1 KDE. The release notes explain what to do.
>
The “online” version of release notes doesn’t mention anything about
bluetooth

http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/
https://www.suse.com/releasenotes/i386/openSUSE/13.1/RELEASE-NOTES.en.html

GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop

Well done with that advice James! :slight_smile:

Those are outdated. (October 17th).

The current 13.1 release notes (you can find them in /usr/share/doc/release-notes/openSUSE/, or use YaST->Support->Release Notes to read them) contain this:

5.10. KDE and Bluetooth

The Bluetooth stack is provided by Bluez 5 (a major, backwards-incompatbile
version), a necessary upgrade for GNOME desktop and some other components
of the base system. Unfortunately, the KDE workspace only supports Bluez
version 4 in its currently-released versions.


Therefore, the openSUSE KDE community team offers an unofficial Bluedevil
package providing at least basic functionality such as device pairing or
support for bluetooth mice; Some other features are known not to work jet,
like file transfer.


For the moment, bugs should not be filed against Bluetooth support in KDE
as the Bluez 5 port of Bluedevil is still ongoing.



Of course installing all updates is always recommended.
And there are already quite a lot updates in the 13.1 update repo.

But allowing vendor change for that is not necessary, in fact if you only have the standard repositories, this has no effect whatsoever.

And I have to admit I’m a bit puzzled here.
The update repo doesn’t contain any bluetooth related update yet.
So could it be that the DVD contains an older version than the standard OSS repo?
Maybe the RC2 DVD was used for upgrading?

On 2013-11-20 08:46, wolfi323 wrote:
>
> vazhavandan;2599048 Wrote:

>> ‘openSUSE 13.1 Release Notes’
>> (http://doc.opensuse.org/release-notes/x86_64/openSUSE/13.1/)
>> http://tinyurl.com/m5c7t8h
>>
> Those are outdated. (October 17th).

which is a bug I keep forgetting to report.

> The current 13.1 release notes (you can find them in
> /usr/share/doc/release-notes/openSUSE/, or use YaST->Support->Release
> Notes to read them) contain this:
>
> Code:
> --------------------
> 5.10. KDE and Bluetooth
>
> The Bluetooth stack is provided by Bluez 5 (a major, backwards-incompatbile
> version), a necessary upgrade for GNOME desktop and some other components
> of the base system. Unfortunately, the KDE workspace only supports Bluez
> version 4 in its currently-released versions.
>
>
> Therefore, the openSUSE KDE community team offers an unofficial Bluedevil
> package providing at least basic functionality such as device pairing or
> support for bluetooth mice; Some other features are known not to work jet,
> like file transfer.
>
>
> For the moment, bugs should not be filed against Bluetooth support in KDE
> as the Bluez 5 port of Bluedevil is still ongoing.
>
>
>
> --------------------

Yes, and they do not mention the fix that James talks about, unless it
is that bluedevil package :-?


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

There is no newer bluedevil package yet, the current one is from Nov. 2nd (this is included in 13.1 GM, in the standard OSS repo):

* Sat Nov 02 2013 tittiatcoke@gmail.com
- Update to a git snapshot of the bluez5 branch. This would allow
  at least some bluetooth functionality in KDE with Bluez5.
  Will be replaced by an official version as soon as available.
- Dropped patch bluedevil-confirmmodechange-typo.patch due to
  upstream changes

This wasn’t in RC2 yet though, that’s why I asked if the installation was maybe done with the RC2 DVD.

Or maybe he meant switching bluedevil back to the (working) bluez4 version from KDE:Extra?
But the question is then where to get bluez4 from. I can only find that in the KDE3 repo… (for 13.1 that is)
And you would have to forcefully install that anyway, regardless of “Allow Vendor Change”.

Hi,
I am also having problem to connect my BT mouse and keyboard. Even after update, I’ve done according to James recommendation, I am constantly receiving bluedevil crash report and I am not able to connect BT devices.
Using hcitool everything pass OK but it does not connect BT device on the end.

Finally, using this method:

user@linux:~> bluetoothctl 
[NEW] Controller C0:18:85:D7:80:CF linux.jozmi [default]
[NEW] Device 00:12:5A:9E:3C:88 Microsoft Keyboard
[NEW] Device 00:12:5A:9D:E6:F0 Microsoft Mouse
[bluetooth]# list
Controller C0:18:85:D7:80:CF linux.jozmi [default]
[bluetooth]# select C0:18:85:D7:80:CF
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller C0:18:85:D7:80:CF Discovering: yes
[CHG] Device 00:12:5A:9E:3C:88 RSSI: -43
[bluetooth]# devices
Device 00:12:5A:9E:3C:88 Microsoft Keyboard
Device 00:12:5A:9D:E6:F0 Microsoft Mouse
[bluetooth]# trust 00:12:5A:9E:3C:88
Changing 00:12:5A:9E:3C:88 trust succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# pair 00:12:5A:9E:3C:88
Attempting to pair with 00:12:5A:9E:3C:88
Pairing successful
[bluetooth]# connect 00:12:5A:9E:3C:88
Attempting to connect to 00:12:5A:9E:3C:88
[CHG] Device 00:12:5A:9E:3C:88 Connected: yes
Connection successful
[CHG] Device 00:12:5A:9E:3C:88 Modalias: usb:v045Ep0099d0010
[CHG] Device 00:12:5A:9E:3C:88 Modalias: usb:v045Ep0099d0010

Even though I receive crash report somehow MS bt mouse connects and works but not the keyboard.
Does anybody know the status of this fix?

Update to the previous post:
I’ve managed to finally connect the keyboard combining bluedevil and the above mentioned [bluetoothctl] way by inputting [connect [MACADR] just after bluedevil finishes pairing.
Afterwards I’ve fixed the linkkey not to change if dual booting. So now this BT pair works correctly.

So could you provide more details on this fix? I can not tell you how important this might be. I have a mouse and a phone that could be used in testing if required. Screen captures are good tools to use and post online. Thank You,

Hi,

Well, I simply started bluedevil KDE graphical interface which normally finds BT mouse and keyboard. I click on the MS keyboard and started pairing which yields a pairing code that I enter. In the same time via console I’ve started [bluetoothctl].

After pairing via graphical bluedevil, connecting process automatically starts which usually results in crash. This time when waiting for bluedevil connection I input

[bluetooth]# connect 00:12:5A:9E:3C:88
Attempting to connect to 00:12:5A:9E:3C:88
[CHG] Device 00:12:5A:9E:3C:88 Connected: yes
Connection successful
[CHG] Device 00:12:5A:9E:3C:88 Modalias: usb:v045Ep0099d0010
[CHG] Device 00:12:5A:9E:3C:88 Modalias: usb:v045Ep0099d0010

So [bluetoothctl] reacted before [bluedevil] interface crashed and connection was completed. Both mouse and keyborad work perfectly since then.

Since, for somethings as CATIA, I use dual dual boot, I went to windows registry and copy the 16bit key of keyboard MACaddr, I have input this 16bit key into linkkeys of /var/lib/bluetooth/BTaddrr/info. So now MS keyboard and mouse work in openSuSE 13.1 and Windows 7 constantly without need to re-pair or reconnect.

Unfortunately, I think I’ll head back to 12.3 until this is resolved.

Could anyone suggest how or where to monitor progress so I’ll know when 13.1 is viable again?

I think I’ve finally found a mid to long term work-around for my bluetooth headphones. :slight_smile: I installed a minimal Gnome desktop. But you don’t need to use Gnome, just its control centre.

Anyone else that can’t get their bluetooth devices working via one of the other methods described in this thread may want to try this. I’m not sure if all steps are necessary because I tried various things before I finally found something that worked.

  1. Delete Bluedevil using Yast or Zypper
  2. Install the patterns-openSUSE-gnome-basis metapackage (I use Yast - I assume Zypper can also install metapackages)
  3. Install gnome-bluetooth (if it’s not already installed as part of the metapackage - I installed it first so I don’t know.)
  4. In a terminal, type gnome-control-center
  5. Click the bluetooth icon in the Hardware section.
  6. Now you should be able to pair, connect, turn bluetooth on and off etc.

Hope this helps someone.

Just a quick update …

  1. It’s not necessary to remove Bluedevil, just don’t use it. That way, when it’s finally fixed, you should get the updated version.

  2. There’s a bug (https://bugs.kde.org/show_bug.cgi?id=325364) report in KDE if you want to follow progress.
    Looking at recent history of KDE and bluetooth, I’m not holding my breath though :frowning:

  3. Another alternative, if you don’t want to install gnome, is bluetoothctl, which is part of bluez-utils. It’s an interactive shell front-end with quite a user-friendly interface. Just type “help” and it will give you a list of commands to pair, trust, connect, disconnect etc.

(Thanks to Christian Gomez from the KDE bug-list for that last hint. If I’d known about that, I might not have installed Gnome!)

Thanks for the info. I might give it a whirl when I get a chance…