FedoraForum.org - Fedora Support Forums and Community
Results 1 to 8 of 8
  1. #1
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    6,144

    Talking Bluetooth - Bluez 5.0 policy change workaround and recommended blueman build

    F24 is released officially today. I downloaded the Gold Release ISO this morning from the official torrents page.

    I've been trying to get F23 build of blueman-2.1-0.3.git7a2e20e installed and running today on my notebook with both dnf and rpm methods.

    It has F24 installed but all available versions of blueman for this release do not work with the Intel Bluetooth adaptor in my notebook.

    If I try installing the aforementioned F23 build there are library dependency issues. The correct libraries cannot be installed because dnf requires newer conflicting ones. So they can't be removed.

    So I have no choice but to go back to F23 for the foreseeable future unless anyone can point me in the right direction to a fix.

    to stop blueman updating i'll add the following to the yum configuration file:

    exclude=blueman*

    That said, because of my report last night the latest update was pulled by Leigh and there may not be any more because of upstream support issues.

    Blueman support upstream is not great. This is not the Fedora blueman packagers fault and just means it may get orphaned for this distribution yet again for which I don't blame them. As the problems are upstream, I'll file a report myself on github just on the off-chance they can do something or at least advise me of a workaround.

    EDIT - filed this
    https://github.com/blueman-project/blueman/issues/537

    ***far better working build of blueman for F24 since located here as per post #7 below, refer to that post for downgrade instructions***

    still follow the instructions in this thread for full functionality though. if obex still doesn't work, make sure you have all obex packages installed
    Last edited by antikythera; 10th October 2016 at 09:44 PM. Reason: url for github bug filed

  2. #2
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    6,144

    Re: F24 - Blueman version 2.0.4 not working for Intel internal USB device

    The upstream team came through so here is the solution I've used to the problem. It is actually down to a policy change in bluez 5.0 onwards where bluetooth adaptors are not powered on by default when detected any longer:

    Create a file in /etc/udev/rules.d/ (eg 50-bluetooth-hci-auto-poweron.rules) with the following content
    Code:
    ACTION=="add", SUBSYSTEM=="bluetooth", KERNEL=="hci[0-9]*", RUN+="/bin/hciconfig %k up"
    EDIT - bluez-5.40-2 policy changed to fix this part of the conundrum. update F24 to that version after install. all other measuers in the thread still apply though. Should that revert at any stage then you will of course need to do the above file creation
    Last edited by antikythera; 1st November 2016 at 09:31 AM.

  3. #3
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    6,144

    Re: Bluetooth - Bluez 5.0 policy change workaround

    IMPORTANT OBEX FILE TRANSFER INFORMATION

    There is an issue with the obex dbus service not being found by gnome or blueman. to correct this do the following with root or sudo rights to create a symbolic link to it:

    Code:
    cd /usr/lib/systemd/user/
    ln -s obex.service dbus-org.bluez.obex.service
    then restart your bluetooth application and you should be able to transfer files properly.

  4. #4
    Join Date
    Apr 2005
    Location
    Toronto, Ontario, Canada
    Posts
    271

    Re: Bluetooth - Bluez 5.0 policy change workaround

    That was very helpful. Thanks!!

    I still have problems with support of my USB bluethooth device (below) and I am stranded at bluez-5.36 which I had to rebuild for F24 to make it work. Frustrating.

    Bus 007 Device 005: ID 0a5c:2148 Broadcom Corp. BCM92046DG-CL1ROM Bluetooth 2.1 Adapter[COLOR="Silver"]

  5. #5
    Join Date
    Apr 2014
    Location
    Brooklyn
    Posts
    58

    Re: Bluetooth - Bluez 5.0 policy change workaround

    Thanks :-)
    Currently using Fedora 23 on a laptop. Before the fix you mentioned, when I power up my laptop blueman-applet would show bluetooth is off and it would not let me power it on, but after when my laptop starts bluetooth is on and I can turn it off, how ever turning it back on it looks like it closes blueman-applet and then come back again, but this time it is on.
    A bit different from Fedora 22, but I will accept this :-)
    Thank you for your help.

  6. #6
    Join Date
    Mar 2011
    Posts
    183

    Re: Bluetooth - Bluez 5.0 policy change workaround

    Quote Originally Posted by antikythera
    IMPORTANT OBEX FILE TRANSFER INFORMATION

    There is an issue with the obex dbus service not being found by gnome or blueman. to correct this do the following with root or sudo rights to create a symbolic link to it:

    Code:
    cd /usr/lib/systemd/user/
    ln -s obex.service dbus-org.bluez.obex.service
    then restart your bluetooth application and you should be able to transfer files properly.
    I found the same issue with obex and used this to fix my issue.

    https://bbs.archlinux.org/viewtopic.php?id=202815

  7. #7
    Join Date
    Dec 2013
    Location
    United Kingdom
    Posts
    6,144

    Re: Bluetooth - Bluez 5.0 policy change workaround

    recommended build of blueman to use with this:

    https://kojipkgs.fedoraproject.org/p...ta0408c1.fc24/

    blueman has been orphaned as a package. This is the build I found works best with my mobile phone for obex file transfer in both directions.

    to apply it, you need to do so as a downgrade. even though the version number is higher, it is an older package build. if blueman tray applet is running close it before proceeding.

    open a terminal window, navigate to the directory you downloaded the rpm file to and enter the following command

    Code:
    sudo dnf downgrade *.rpm
    you will be asked to confirm the downgrade after entering your password.

    after applying this, to prevent it being updated by dnf or yumex-dnf, add it as an exclusion to dnf.conf using the following line. if you already have excludes, add it on the list and save the change.

    exclude=blueman

    same applies to yum.conf if using yum-deprecated or yumex

  8. #8
    Join Date
    Mar 2011
    Location
    /
    Posts
    5,150

    Re: Bluetooth - Bluez 5.0 policy change workaround and recommended blueman build

    Stuck and closed. Please open new threads with questions and reference this thread as appropriate.

    Thanks to everyone who contributed here to this guide.
    Fedora 28 x86_64 XFCE - Sager | Intel Core i7 - 4810 MQ | NVIDIA GeForce GTX 860M | 16 GB RAM | 480 GB ADATA SSD |
    Fedora 28 x86_64 XFCE - Dell Precision M4800 | Intel Core i7 - 4900 MQ | NVIDIA Quadro K1100M | 16 GB RAM | 750 GB 7200 RPM HDD |


    The Linux Documentation Project | Fedora Documentation

Similar Threads

  1. bluetooth serial port, no bluez-compat package in 20
    By MariaHanson in forum Using Fedora
    Replies: 1
    Last Post: 13th October 2015, 06:49 PM
  2. Blueman / Bluetooth NAP - reverse tethering
    By kosieh in forum Servers & Networking
    Replies: 1
    Last Post: 7th October 2015, 07:33 PM
  3. Replies: 0
    Last Post: 31st January 2014, 09:29 AM
  4. No Bluetooth on XFCE4 with Blueman
    By FreedomFighter in forum Servers & Networking
    Replies: 0
    Last Post: 19th August 2013, 12:08 PM
  5. F10 Bluetooth Files - hcid.conf & bluez-utils, where are they?
    By Newbie_from_NJ in forum Hardware & Laptops
    Replies: 2
    Last Post: 5th January 2009, 08:37 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •