Hi there,
I reported a few weeks ago an issue I observed when trying to pair and use a bluetooth audio speaker to a Fedora26 system. The issue was reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1469961
However so far there had not been any reaction. The issue was observed from multiple users I know and had been reproduced with different audio speakers. So my assumption currently is that the bluetooth audio is completely broken under Fedora 26. Can anyone confirm this issue or at least confirm that it is working for him? As this is an issue that not allow to use existing hardware correctly, I would appreciate if anyone having ideas to possibly working arround the segfaults.
I am looking forward for any suggestions :)
Best regards, Florian
On 08/17/2017 11:18 AM, Florian Sievert wrote:
Hi there,
I reported a few weeks ago an issue I observed when trying to pair and use a bluetooth audio speaker to a Fedora26 system. The issue was reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1469961
However so far there had not been any reaction. The issue was observed from multiple users I know and had been reproduced with different audio speakers. So my assumption currently is that the bluetooth audio is completely broken under Fedora 26. Can anyone confirm this issue or at least confirm that it is working for him? As this is an issue that not allow to use existing hardware correctly, I would appreciate if anyone having ideas to possibly working arround the segfaults.
I am looking forward for any suggestions :)
I'd suggest reporting it to the upstream bluez team. They don't have a bugzilla, but they do have a mailing list. See
http://vger.kernel.org/vger-lists.html#linux-bluetooth
for subscribing details. Include all your bugzilla info in your email once you've subscribed.
The bluez people are also available on IRC (freenode.net) in the channels:
#bluez (development related topics) #bluez-users (non-development related topics) #bluez-gsoc (for Google Summer of Code)
so that's also an option. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - su -; find / -name someone -exec touch {} ; - - - The UNIX way of touching someone - ----------------------------------------------------------------------
On 08/18/2017 02:18 AM, Florian Sievert wrote:
Hi there,
I reported a few weeks ago an issue I observed when trying to pair and use a bluetooth audio speaker to a Fedora26 system. The issue was reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1469961
However so far there had not been any reaction. The issue was observed from multiple users I know and had been reproduced with different audio speakers. So my assumption currently is that the bluetooth audio is completely broken under Fedora 26. Can anyone confirm this issue or at least confirm that it is working for him? As this is an issue that not allow to use existing hardware correctly, I would appreciate if anyone having ideas to possibly working arround the segfaults.
I am looking forward for any suggestions :)
I have a BlueTooth headset. An Optoma NuForce BE6i. I'd not previously tried to connect it to my Linux systems. But I did so today.
Strangely, it connects and works just fine on one system while failing on the other. Both are currently running F26 and I'm using KDE as my desktop.
When using the GUI to connect the devices I notices something strange. On the working system when the device is discovered an icon appears showing a Headset while on the failing system an icon appears showing a gray box with some music symbols.
Also, in the journal of the failing system I see this
Aug 18 08:12:47 acer.greshko.com plasmashell[1312]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js:34: TypeError: Cannot read property 'devices' of undefined Aug 18 08:12:47 acer.greshko.com plasmashell[1312]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/logic.js:34: TypeError: Cannot read property 'devices' of undefined Aug 18 08:12:47 acer.greshko.com systemd-coredump[3629]: Process 3542 (bluetoothd) of user 0 dumped core. #0 0x000000e083b9fcd4 ba2str (bluetoothd)
At the moment I don't know what the difference may be in the systems....
On 08/18/2017 08:40 AM, Ed Greshko wrote:
At the moment I don't know what the difference may be in the systems....
I'm going to label this under the heading of "strange".
The system with the failure is a "pure KDE" system in that is the only desktop installed. The only difference that I could find between it and the working system was 2 gnome packages related to bluetooth. gnome-bluetooth and gnome-bluetooth-libs. I installed those and it seemed to make no difference as I'm pretty sure it failed.
I then decided to install strace on the failing system and connect with the bluetoothd process and use bluetoothctl to pair and connect the device with the intention of capturing more about the failure.
Well, after doing that and using bluetoothctl the pair and connect worked and I have not seen another failure since. I even erased the 2 gnome packages I installed and everything still works.
Color me confused.....
On 08/18/2017 02:18 AM, Florian Sievert wrote:
Hi there,
I reported a few weeks ago an issue I observed when trying to pair and use a bluetooth audio speaker to a Fedora26 system. The issue was reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1469961
However so far there had not been any reaction. The issue was observed from multiple users I know and had been reproduced with different audio speakers. So my assumption currently is that the bluetooth audio is completely broken under Fedora 26. Can anyone confirm this issue or at least confirm that it is working for him? As this is an issue that not allow to use existing hardware correctly, I would appreciate if anyone having ideas to possibly working arround the segfaults.
I am looking forward for any suggestions :)
Also, this problem isn't limited to Fedora.
https://bugs.archlinux.org/task/53442
On 08/18/2017 05:21 AM, Ed Greshko wrote:
On 08/18/2017 02:18 AM, Florian Sievert wrote:
Hi there,
I reported a few weeks ago an issue I observed when trying to pair and use a bluetooth audio speaker to a Fedora26 system. The issue was reported at: https://bugzilla.redhat.com/show_bug.cgi?id=1469961
However so far there had not been any reaction. The issue was observed from multiple users I know and had been reproduced with different audio speakers. So my assumption currently is that the bluetooth audio is completely broken under Fedora 26. Can anyone confirm this issue or at least confirm that it is working for him? As this is an issue that not allow to use existing hardware correctly, I would appreciate if anyone having ideas to possibly working arround the segfaults.
I am looking forward for any suggestions :)
Also, this problem isn't limited to Fedora.
I have a bluetooth speaker at home and I'll try to couple it this weekend. However, since there is an archlinux bug also filed against it (see above), it's obviously upstream from the distributions. This is why I recommended emailing the bluetooth group directly:
http://vger.kernel.org/vger-lists.html#linux-bluetooth
or getting on their IRC channels to see if they can offer suggestions:
irc.freenode.net #bluez (development related topics) #bluez-users (non-development related topics) #bluez-gsoc (for Google Summer of Code)
Don't know if that'll be of any help, but live bodies on IRC may be useful. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - "If you can't fix it...duct tape it!" -- Tim Allen - ----------------------------------------------------------------------
-
Ed Greshko -
Ed Greshko -
Florian Sievert -
Rick Stevens