Bluetooh-Speaker not starting – bluealsa-service failed code=exited, status=127

Max2Play Home 2016 (en) Forums Max2Play Add-ons Bluetooh-Speaker not starting – bluealsa-service failed code=exited, status=127

This topic contains 0 replies, has 1 voice, and was last updated by  fsarrias 4 days, 17 hours ago.

Viewing 1 post (of 1 total)
  • 1. Dezember 2019 at 1:03 #47649

    I want to stream music from my Android phone to a Raspi4+HifiBerry DAC+ connected to my music equipment through Bluetooth with max2play 2.51 installed.
    I succesfully installed the bluetooth add-on in max2play.
    I succesfully paired my phone with max2play through bluetooth.
    But when I try to start Bluetooth-Speaker it gives me an error and the streaming does not work, the debugging info is:

    #### Bluetooth Installation ####

    #### Bluetooth Dongle ####
    hci0: Type: Primary Bus: UART
    BD Address: DC:A6:32:0E:42:8A ACL MTU: 1021:8 SCO MTU: 64:1
    RX bytes:48913 acl:25 sco:0 events:2966 errors:0
    TX bytes:126221 acl:24 sco:0 commands:2920 errors:0

    #### BLUEALSA ERROR ####
    ● bluealsa.service – Start Bluealsa for Bluetooth on Alsa (not compatible with Pulseaudio)
    Loaded: loaded (/etc/systemd/system/bluealsa.service; enabled; vendor preset: enabled)
    Active: activating (auto-restart) (Result: exit-code) since Sat 2019-11-30 23:56:18 CET; 2s ago
    Process: 8684 ExecStartPre=/bin/rm -Rf /var/run/bluealsa (code=exited, status=0/SUCCESS)
    Process: 8685 ExecStartPre=/usr/bin/killall bluetoothd (code=exited, status=0/SUCCESS)
    Process: 8686 ExecStartPre=/bin/systemctl start sys-subsystem-bluetooth-devices-hci0.device (code=exited, status=0/SUCCESS)
    Process: 8687 ExecStartPre=/bin/hciconfig hci0 down (code=exited, status=0/SUCCESS)
    Process: 8688 ExecStartPre=/bin/systemctl start bluetooth (code=exited, status=0/SUCCESS)
    Process: 8690 ExecStartPre=/bin/sleep 5 (code=exited, status=0/SUCCESS)
    Process: 8691 ExecStart=/usr/bin/bluealsa -p a2dp-sink -p a2dp-source (code=exited, status=127)
    Main PID: 8691 (code=exited, status=127)

    Nov 30 23:56:18 max2play systemd[1]: bluealsa.service: Failed with result ‚exit-code‘.

    #### BLUEALSA RUNNING ####

    It seems I have the same problem as another german user here:
    I get also the same library not found error in the SYSLOG:

    Dec 1 00:38:33 max2play bluealsa[5586]: /usr/bin/bluealsa: error while loading shared libraries: cannot open shared object file: No such file or directory

    Please any help will be very valuable
    Best regards

    • This topic was modified 4 days, 17 hours ago by  fsarrias.
Viewing 1 post (of 1 total)

You must be logged in to reply to this topic.

Register here