BlueZ 5.79 to 5.80

[EaglePipe]

Hello everyone,

My name is Alexander, and I’m new here. I first gained experience with Linux using OpenSUSE, Ubuntu, and Debian. After spending a long time with macOS, I’ve been back on Linux for the past four months because I want to better understand what my system is doing in the background. I now use Manjaro as my sole production system—and I’m completely satisfied with it.

Now to my problem:
Since updating from BlueZ 5.79 to 5.80, my MX Master 3 and MX Keys no longer work. After downgrading to 5.79, everything functions smoothly again. However, I would like to update to the latest version.

I have already found a potential solution:
GitHub – Commit with relevant changes

However, I’m unsure where exactly to apply these changes. That’s why I’m reaching out here in the hope of getting some guidance.

Best regards,
Alex

[linux-aarhus]

The rebuild is caused by adding a dependency

Arch Linux / Packaging / Packages / bluez · GitLab

 $ mbn info bluez -q
Branch         : archlinux
Name           : bluez
Version        : 5.80-2
Repository     : extra
Build Date     : Thu 27 Mar 2025 06:34:45 
Packager       : Andreas Radke <andyrtr@archlinux.org>
Branch         : unstable
Name           : bluez
Version        : 5.80-2
Repository     : extra
Build Date     : Thu 27 Mar 2025 06:34:45 
Packager       : Andreas Radke <andyrtr@archlinux.org>
Branch         : testing
Name           : bluez
Version        : 5.80-2
Repository     : extra
Build Date     : Thu 27 Mar 2025 06:34:45 
Packager       : Andreas Radke <andyrtr@archlinux.org>
Branch         : stable
Name           : bluez
Version        : 5.80-1
Repository     : extra
Build Date     : Mon 17 Mar 2025 15:52:18 
Packager       : Andreas Radke <andyrtr@archlinux.org>

You would have to create a patch file and apply it in the source PKGBUILD

[EaglePipe]

@linux-aarhus

Assuming you are on stable branch - I see a rebuild of bluez package to 5.80-2.

I cannot say what has prompted the rebuild but you could try switching branch to testing.

I have already tried the testing branch, but unfortunately without success.

The issue seems to be known, but I can’t figure out the solution because I can’t find where the changes need to be made.

Here is the full post:
GitHub – BlueZ Issue #1138

[linux-aarhus]

I figured that much when I found the commit on Arch prompting the rebuild.

You would have to clone the repo mentioned in your link - then patch the file mentioned with the code mention in the rightmost pane.

Another approach is to clone the Arch PKGBUILD

• first use makepkg -os to fetch and unpack the sources
• then manually patch the file before you run makepkg -i

But it is likely better to wait on the next release of the bluez source code.

[EaglePipe]

Fixing it myself didn’t work, so I guess I’ll have to wait.

[EaglePipe]

This version (bluez 5.82-1) works
https://archlinux.org/packages/extra/x86_64/bluez/

_{Mod edit: added the relevant bluez version number to the post}