Search Criteria
Package Details: bluez-alsa-git 1.4.0.r9.g1557602-1
| Git Clone URL: | https://aur.archlinux.org/bluez-alsa-git.git (read-only) |
|---|---|
| Package Base: | bluez-alsa-git |
| Description: | Bluetooth Audio ALSA Backend |
| Upstream URL: | https://github.com/Arkq/bluez-alsa |
| Keywords: | alsa bluetooth bluez |
| Licenses: | |
| Submitter: | nheird |
| Maintainer: | nheird |
| Last Packager: | nheird |
| Votes: | 13 |
| Popularity: | 0.838444 |
| First Submitted: | 2016-10-28 17:41 |
| Last Updated: | 2019-04-01 20:17 |
Latest Comments
1 2 Next › Last »
keithspg commented on 2019-03-31 22:28
I am able to build this, but it does not run. I posted to the bluealsa package as well, but am wondering if this is an Arch systemd permission issue? The current version builds as: bluez-alsa-git 1.4.0.r9.g1557602-1
Also, the tmpfiles references /var/run and should be changed to /run in the package...
I have installed the bluetooth-raspberrypi AUR as well as installed the standard bluez packages:
bluetooth-raspberrypi 6-2 bluez 5.50-6 bluez-alsa-git 1.4.0.r9.g1557602-1 bluez-libs 5.50-6 bluez-utils 5.50-6
Every launch of the service gives this error in the journal:
Mar 31 17:17:48 rune dbus-daemon[270]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.51" (uid=974 pid=1385 comm="/usr/bin/bluealsa ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=272 comm="/usr/lib/bluetooth/bluetoothd ") Mar 31 17:17:48 rune bluealsa[1385]: /usr/bin/bluealsa: Couldn't get managed objects: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 2 matched rules; type="method_call", sender=":1.51" (uid=974 pid=1385 comm="/usr/bin/bluealsa ") interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" error name="(unset)" requested_reply="0" destination="org.bluez" (uid=0 pid=272 comm="/usr/lib/bluetooth/bluetoothd ") Mar 31 17:17:48 rune bluealsa[1385]: /usr/bin/bluealsa: Couldn't acquire D-Bus name: org.bluealsa Mar 31 17:17:48 rune systemd[1]: bluealsa.service: Main process exited, code=exited, status=1/FAILURE Mar 31 17:17:48 rune systemd[1]: bluealsa.service: Failed with result 'exit-code'.
azmeuk commented on 2019-03-17 20:12
Hi. The installation fails with this error message:
install: cannot stat '/tmp/yaourt-tmp-azmeuk/aur-bluez-alsa-git/src/bluez-alsa-git/LICENSE.txt': No such file or directory
capoeira commented on 2019-03-10 16:16
Hi folks. Even with the service loading at boot my audio devices wont connect. They connect fine with pulseaudio installed. any hints? it's the standard "Failed to connect: org.bluez.Error.Failed" error
actionless commented on 2019-01-02 00:22
hi! package version shouldn't start from
v, just numbernheird commented on 2018-10-29 13:51
Hi @kempniu, thanks for the report. I added sysconfdir as you mentioned.
kempniu commented on 2018-10-29 13:04
Hi! Thank you for maintaining this package. Please note that upstream commit dae0699, which was committed roughly a week ago, necessitates adding "--sysconfdir /etc" to the list of ./configure options used, otherwise the 20-bluealsa.conf file lands in /usr/etc/alsa/conf.d, which breaks things. Could you please take a look? Thanks!
chowbok commented on 2018-08-05 03:03
Hi... can you add "aarch64" to the supported architectures? It builds fine.
yodor commented on 2018-03-16 09:07
Thank you for maintaining this package
hexvalid commented on 2018-03-07 17:08
thanks for maintaining
nheird commented on 2017-09-20 19:41
Updated thanks