[PATCH] gnu: bluez: Update to 5.79.

  • Open
  • quality assurance status badge
Details
3 participants
  • Danny Milosavljevic
  • Dakota Logan
  • Julian Flake
Owner
unassigned
Submitted by
Julian Flake
Severity
normal
J
J
Julian Flake wrote on 28 Nov 22:11 +0100
(address . guix-patches@gnu.org)(name . Julian Flake)(address . flake@uni-koblenz.de)
1a0c0cfb41a0f7421e2e70d73ee6803c2a33c923.1732828088.git.flake@uni-koblenz.de
* gnu/packages/linux.scm (bluez): Update to 5.79.

Change-Id: I5928664f929d1bda6e8c8c5e37cb9020a9889881
---
gnu/packages/linux.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Toggle diff (26 lines)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index f7e7126c3d..a7c2678540 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -6203,7 +6203,7 @@ (define-public sbc
(define-public bluez
(package
(name "bluez")
- (version "5.72")
+ (version "5.79")
(source (origin
(method url-fetch)
(uri (string-append
@@ -6211,7 +6211,7 @@ (define-public bluez
version ".tar.xz"))
(sha256
(base32
- "0vjk4ihywzv8k07bxq7clqgi2afrw54nfp0gcnxw35m98nipz7a9"))))
+ "12pal1m4xlr8k7kxb6isv5lbaca2wc5zcgy0907wfwcz78qaar21"))))
(build-system gnu-build-system)
(arguments
(list

base-commit: 294386674c417355a24586fab5528c643d495b86
--
2.46.0
J
J
Julian Flake wrote on 3 Dec 14:28 +0100
Reason for why I'm interested
(address . 74597@debbugs.gnu.org)
87ldwwzyjf.fsf@uni-koblenz.de
The reason, why I'm interested in this update is that I hope it
fixes an issue I have with my headset:


Best Regards,
nutcase
D
D
Dakota Logan wrote on 17 Dec 04:48 +0100
(no subject)
(address . 74597@debbugs.gnu.org)
41af4ff659491f984e6e1b3dd72f1243@riseup.net
I'm having the same issue so would love to see it fixed!
D
D
Danny Milosavljevic wrote 4 days ago
Confirming problem
(address . 74597@debbugs.gnu.org)
20241221164545.612C61121371@dd30410.kasserver.com
Hi,

I have the same problem with Linux 6.11.11 and bluez 5.72.

I would like the fix to be in guix, but unfortunately it would cause
2455 packages (including erlang, gtk, gnome, gdm, qemu, qt, kde,
mate and enlightenment) that depend on bluez to rebuild (WTF!).

And I don't think there are a lot of Guix users using bluetooth.

So I should not just apply it to master as it is.

We could make a graft with just the patch[1]--even though it's not a
security patch. What do you all think? Make an exception here?

The cause was that the kernel reverted a bugfix. The bugfix would have
done a link type fixup (see below). But it was a userspace-visible change
(broke the interface guarantee between kernel and user space) and so
that's a no-no, and hence was reverted. So now someone else has to do
the bugfix in userspace--in this case bluez[1].

Reverted bugfix was[2]:

If two Bluetooth devices both support BR/EDR and BLE, and also
support Secure Connections, then they only need to pair once.
The LTK generated during the LE pairing process may be converted
into a BR/EDR link key for BR/EDR transport, and conversely, a
link key generated during the BR/EDR SSP pairing process can be
converted into an LTK for LE transport. Hence, the link type of
the link key and LTK is not fixed, they can be either an LE LINK
or an ACL LINK.

Because the keys are (and were) stored on disk, userspace will always
have to do this kind of sanity check anyway--so this patch[1] will
likely stay in bluez releases forever.

[2] https://www.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.206, search for "59b047bc98084f8af2c41483e4d68a5adf2fa7f7"
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 74597@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 74597
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch