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. > > https://bugs.archlinux.org/task/53442 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@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - "If you can't fix it...duct tape it!" -- Tim Allen - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
