• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

Bluetooth failed / Permission Denied

Scheduled Pinned Locked Moved Help and Support
bluetooth.servibluetooth errorpermissions
8 Posts 2 Posters 4.2k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • V
    vantseattle
    last edited by 16 Dec 2016, 01:41

    Good evening all,

    I had purchased an 8bitdo a while back and attempted to get it working on my RetroPie before but to little success. Over the last week I have jumped back into the project and my attempts are a little further but now I'm coming across something that is making me sign up and reach out to the experts here. To get the nitty-gritty out of the way I have already updated RetroPie to 4.1.5 and updated the firmware on the 8bitdo. When I use "hcitool scan" from the terminal I am able to see the controller. When using the bluetooth script it will get stuck at the "Scanning..." dialogue and not progress or find any devices. I have left this for many minutes at a time. It would have at least found some bluetooth device in my house.

    I started to check the logs and found that I'm getting permission errors when it's trying to launch the service. The log is copied below.

    Something else that I will note, when I launched the bluetooth configuration script from the RetroPie-Setup script I received two prompts requesting to overwrite/replace existing scripts. I chose 'yes' at these while the default would have been 'no.'

    A few months prior, before the updates, I would have been able to see devices on the bluetooth script.

    I'm possibly wondering if those scripts that I overwrote caused this issue.

    HARDWARE SPECS
    Rasp Pi model: 3
    RetroPie Version used: 4.1.5
    Built From: Pre made SD image on RetroPie website
    BT Controller: 8bitdo SNES30
    BT Controller Firmware: 2.70 (pulled from site dated 2016-10-26)
    Error messages received: terminal copy/pasta is below

    GUIDES USED
    https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-a-Bluetooth-controller
    https://github.com/RetroPie/RetroPie-Setup/wiki/Setting-up-an-8bitdo-Bluetooth-controller

    CODE

    The programs included with the Debian GNU/Linux system are free software;
    the exact distribution terms for each program are described in the
    individual files in /usr/share/doc/*/copyright.
    Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
    permitted by applicable law.
    Last login: Tue Dec 13 02:31:02 2016
    .~~. .~~. Friday, 16 December 2016, 12:43:34 am UTC
    '. \ ' ' / .' Linux 4.4.34-v7+ armv7l GNU/Linux
    .~ .~~~..~.
    : .~.'~'.~. : Filesystem Size Used Avail Use% Mounted on
    ~ ( ) ( ) ~ /dev/root 118G 64G 49G 57% /
    ( : '~'.~.'~' : ) Uptime.............: 0 days, 00h15m10s
    ~ .~ ~. ~ Memory.............: 549552kB (Free) / 752852kB (Total)
    ( | | ) Running Processes..: 123
    '~ ~' IP Address.........: 192.168.1.107
    *--~-~--* Temperature........: CPU: 53°C/127°F GPU: 53°C/127°F
    The RetroPie Project, http://www.petrockblock.com
    pi@retropie:~ $ cat /var/log/daemon.log | grep bluetooth
    Dec 16 00:30:58 retropie systemd[1396]: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: Permission denied
    Dec 16 00:30:58 retropie systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC
    Dec 16 00:30:58 retropie systemd[1]: Unit bluetooth.service entered failed state.
    Dec 16 00:35:10 retropie systemd[2169]: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: Permission denied
    Dec 16 00:35:10 retropie systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC
    Dec 16 00:35:10 retropie systemd[1]: Unit bluetooth.service entered failed state.
    pi@retropie:~ $

    Thanks in advance for any insight!

    B 1 Reply Last reply 16 Dec 2016, 01:50 Reply Quote 0
    • B
      BuZz administrators @vantseattle
      last edited by 16 Dec 2016, 01:50

      @vantseattle did you install the ps3 driver?

      To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

      V 1 Reply Last reply 16 Dec 2016, 01:59 Reply Quote 0
      • V
        vantseattle @BuZz
        last edited by 16 Dec 2016, 01:59

        @BuZz Would the PS3 driver be needed if I'm not using a PS3 controller?

        I installed that driver anyways, went back to the RetroPie-Setup script and tried searching for Bluetooth devices again. Still stuck at "Searching..." dialogue with no progress.

        1 Reply Last reply Reply Quote 0
        • V
          vantseattle
          last edited by 16 Dec 2016, 02:10

          More code.

          pi@retropie:~/RetroPie-Setup $ sudo systemctl status bluetooth.service -l
          ● bluetooth.service - Bluetooth service
             Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
             Active: failed (Result: exit-code) since Fri 2016-12-16 02:02:28 UTC; 1min 10s ago
               Docs: man:bluetoothd(8)
            Process: 10115 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=203/EXEC)
           Main PID: 10115 (code=exited, status=203/EXEC)
          
          Dec 16 02:02:28 retropie systemd[1]: bluetooth.service: main process exited, code=exited, status=203/EXEC
          Dec 16 02:02:28 retropie systemd[1]: Failed to start Bluetooth service.
          Dec 16 02:02:28 retropie systemd[1]: Unit bluetooth.service entered failed state.
          
          B 1 Reply Last reply 16 Dec 2016, 02:18 Reply Quote 0
          • B
            BuZz administrators @vantseattle
            last edited by 16 Dec 2016, 02:18

            @vantseattle The reason I asked, is that installing the ps3 driver disables the bluetooth daemon and gives an error like you were seeing. Uninstall it and see if it helpers (as that resets the permissions again so it should load).

            To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

            V 1 Reply Last reply 16 Dec 2016, 02:19 Reply Quote 0
            • V
              vantseattle @BuZz
              last edited by 16 Dec 2016, 02:19

              @BuZz Ha! Okay that makes a little more sense then. I'll try that now.

              B 1 Reply Last reply 16 Dec 2016, 02:20 Reply Quote 0
              • B
                BuZz administrators @vantseattle
                last edited by 16 Dec 2016, 02:20

                @vantseattle If that doesn't help you can try removing/re-installing the bluetooth stack (making sure ps3 driver is removed first) sudo apt-get remove bluez; sudo apt-get install bluez

                To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                V 1 Reply Last reply 16 Dec 2016, 02:29 Reply Quote 0
                • V
                  vantseattle @BuZz
                  last edited by 16 Dec 2016, 02:29

                  @BuZz Thanks for the insight here. So installing then uninstalling the PS3 drivers had fixed the permission issues. I was able to attach the controller and configure the inputs. Thanks!! We can mark this one solved.

                  1 Reply Last reply Reply Quote 0
                  8 out of 8
                  • First post
                    8/8
                    Last post

                  Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                  Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.

                    This community forum collects and processes your personal information.
                    consent.not_received