Package Details: bluez-utils-compat 5.61-1

Git Clone URL: https://aur.archlinux.org/bluez-utils-compat.git (read-only, click to copy)
Package Base: bluez-utils-compat
Description: Development and debugging utilities for the bluetooth protocol stack. Includes deprecated tools.
Upstream URL: http://www.bluez.org/
Keywords: hciconfig hcidump hcitool
Licenses: GPL2
Conflicts: bluez-hcidump, bluez-hcitool, bluez-utils
Provides: bluez-hcidump, bluez-hcitool, bluez-utils=5.61
Submitter: thurstylark
Maintainer: twa022
Last Packager: twa022
Votes: 42
Popularity: 2.08
First Submitted: 2017-03-02 17:34
Last Updated: 2021-08-26 14:22

Required by (48)

Sources (1)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Zoddo commented on 2021-08-14 09:46

@Galaxy: Arch Linux is using systemd and the bluez systemd integration is needed.

If you need to disable it on Artix, you can add the flag locally on your machine (you can commit the change in your local repository; it will be kept when using "git pull". That's also working with most AUR helpers as they usually do a git pull)

Galaxy commented on 2021-08-14 09:25

Would you disable systemd so that it can be built in Artix Linux ?

@@ -38,6 +38,7 @@ build() {
           --enable-mesh \
           --enable-experimental \
           --enable-library \
+          --disable-systemd \
           --enable-deprecated # to enable deprectated tools
   make

sayonalion commented on 2021-03-06 16:20

hcitool lescanSet scan parameters failed: Input/output error

Aberts10 commented on 2020-11-29 07:11

When trying to use hcitool lescan, i can only get "Could not create connection: Input/output error"

What's going on here?

Zepman commented on 2020-09-10 10:56

Note:

Package is updated and the below information is no longer relevant.

Building fails:

==> ERROR: Failure while downloading https://git.archlinux.org/svntogit/packages.git/plain/trunk/refresh_adv_manager_for_non-LE_devices.diff?h=packages/bluez
    Aborting...

The cause for this is that the diff file is not included in the bluez package anymore.

Workaround

In PKGBUILD, replace the URL for refresh_adv_manager_for_non-LE_devices.diff (the last value of source) with:

https://mirror.slackbuilds.org/slackware/slackware-current/source/n/bluez/refresh_adv_manager_for_non-LE_devices.diff.gz

Replace the last value of sha512sums with:

7e633031175298c4711f49843a6e3e2eb4ad93e49c200d5401aec159f36ae7a0f2172be7935f0f1dc88780b7aae22b8c08de61cfc26001c4e4579811aa8be451

makepkg will extract the diff file automatically, so do not worry about that.

Build and install the package as normal.

Suggestion to package maintainer

Include the diff file in the AUR package.

JohnnyDeacon commented on 2020-08-05 21:30

==> PGP keys need importing: -> E932D120BC2AEC444E558F0106CA9F5D1DCF2659, required by: bluez-utils-compat ==> Import? [Y/n] Y :: Importing keys with gpg... gpg: keyserver receive failed: General error problem importing keys

twa022 commented on 2020-07-29 12:44

If there's an issue retrieving the key, you can always skip the pgp check by passing --skippgpcheck to makepkg when building.

ZReC commented on 2020-07-26 05:02

I'm having the same issue.

bluez-5.54.tar ... FAILED (unknown public key 06CA9F5D1DCF2659) ==> ERROR: One or more PGP signatures could not be verified!

And then when I input: gpg --recv-keys 06CA9F5D1DCF2659

It throws: gpg: keyserver receive failed: General error

I got a "Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)" that is not working, the only place I could make it to work was under Ubuntu thanks to this > https://github.com/jeremyb31/newbtfix-4.15. I tried as well here in Arch but it won't work. Then I came here just to try https://bugzilla.kernel.org/show_bug.cgi?id=60824, I couldn't install this package yet.

aleheavyjoy commented on 2020-07-25 17:00

nope

$ gpg --recv-keys 06CA9F5D1DCF2659
gpg: keyserver receive failed: Erro genérico

artaxlives commented on 2020-03-23 05:03

@Marc.2377 is correct. Run 'gpg --recv-keys 06CA9F5D1DCF2659' as the same user running yaourt.

@twa022 Do NOT use the sudo pacman-key solution suggested below. That will install it to the wrong (root's) gpg keyring.