Closed Hurricos closed 6 years ago
Wow that seems annoying. Thanks for reaching out. I'll wait for your commit :)
I've got it done, but it was a pain in the ass on account of the format of the installation file. Going to tackle a few things in that next, but will offer two separate pull requests.
Pull request is up; I have done testing and it works fine. Feel free to close when you are satisfied with the results.
Similar issue to what is seen here.
Simply running
systemctl enable bluealsa
is not sufficient inbluealsa
version 0.9, though it worked fine in version 0.7. This is because thebluealsa
binary now requires you to specify on the command line which profile you would like to run with, if it is nota2dp-source
.From
/usr/bin/bluealsa --help
:In order to override manually, we must override
systemd
. We start off with the following output forsystemctl cat bluealsa.service
:We must edit this and add lines to override
ExecStart
, viasudo systemctl edit bluealsa.service
:Once we run
sudo systemctl daemon-reload && sudo systemctl restart bluealsa.service
,bluealsa
and thereforempradio
will return to functioning normally.I'm looking into what is required to automate the process of editing the
systemd
configuration for this; the issue I linked above discusses editing an init-file, but sincempradio
leveragessystemd
, this is not a solution. Instead, we should follow standard protocol for modifyingsystemd
files.As far as I can tell, this just then involves the addition of a few lines to
install.sh
near where wesystemctl enable bluealsa.service
:I will write the commit and test.