looking at the releases, there have been 2 newer releases  (5.82) after only a few days, whereas it took ~4 month between 5.79 and 5.80.
The commit messages are not obviously fixing the described problem.

Thank you for the report.
"Downgrading to bluez-5.79-1 makes it work again" is clear enough.

Assigning to DavidG who committed v5.80 & 5.81; CC'ing Giuseppe who did v5.79.
Maybe it is worth trying the most recent update 5.81?

Assignee: bugsquad => geiger.david68210
CC: (none) => ghibomgx

I've updated bluez to 5.82. I also added a systemd-253.31 update since it's often involved in suspend process (and it also fixes several bug including some memleak). See whether it fixes the problem.

Do you have these updates in udpates_testing or is this only in caludron?

updates_testing of mga9 as well as core/release of cauldron.

And systemd-253.31 for mga9's updates_testing, build in progress. Should be ready soon.

Due to my vaccation next week, I probably can test afterwards

tested the update - it looks good.
bluetooth reconnects the device after suspend, as it was in 5.79

There is version 5.82 in updates_testing, which fixes the issue.

Assignee: geiger.david68210 => qa-bugs

I guess we can move it. It works since weeks (both)

MGA9-64, Xfce, Celeron N2840, Chromebook

Bluetooth


installed 5.82

spent several hours using it.  No issues.

CC: (none) => brtians1

Plse give the exact rpmname.

CC: (none) => herman.viaene

Created attachment 14997 [details]
files list

Used the same HW in testing bug 34123, but now
# systemctl enable bluetooth
Created symlink /etc/systemd/system/dbus-org.bluez.service → /usr/lib/systemd/system/bluetooth.service.
Created symlink /etc/systemd/system/bluetooth.target.wants/bluetooth.service → /usr/lib/systemd/system/bluetooth.service.
[root@mach3 ~]# systemctl restart bluetooth
[root@mach3 ~]# systemctl -l status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
     Active: active (running) since Tue 2025-05-27 17:01:31 CEST; 5s ago
       Docs: man:bluetoothd(8)
   Main PID: 4213 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 8806)
     Memory: 728.0K
        CPU: 244ms
     CGroup: /system.slice/bluetooth.service
             └─4213 /usr/libexec/bluetooth/bluetoothd

May 27 17:01:30 mach3.hviaene.thuis (uetoothd)[4213]: ConfigurationDirectory 'bluetooth' already exists but the mode is different. (File system: 755 Configu>
May 27 17:01:30 mach3.hviaene.thuis systemd[1]: Starting bluetooth.service...
May 27 17:01:31 mach3.hviaene.thuis bluetoothd[4213]: Bluetooth daemon 5.82
May 27 17:01:31 mach3.hviaene.thuis systemd[1]: Started bluetooth.service.
May 27 17:01:31 mach3.hviaene.thuis bluetoothd[4213]: Starting SDP server
May 27 17:01:31 mach3.hviaene.thuis bluetoothd[4213]: Bluetooth management interface 1.22 initialized
and
# bluetoothctl list
returns nothing and in lspcidrake -v I get:
btusb           : Qualcomm Atheros Communications|Unknown [Wireless|Radio Frequency|Bluetooth] (vendor:0cf3 device:3121)

and
# rfkill list
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
Googling hasn't brought me any furter yet.

Long shot: I've just upgraded to kernel92, but Len had no problem on that.
-

(In reply to Herman Viaene from comment #14)
> Long shot: I've just upgraded to kernel92, but Len had no problem on that.
> -

Check if you not miss some of the firmware packages in bug#34302
Run harddrake and click on the bluethoot icom and see if you get some extra package

Just to confirm Herman's comment in comment #15.

kernel linus 6.6.92-1.mga9

Clean update.  Restarted bluetooth.  Audio connected over bluetooth immediately.

$ rpm -qa | grep bluez
bluez-tools-0.2.0-0.git20201025.1.mga9
lib64kf5bluezqt6-5.114.0-1.mga9
bluez-qt-5.114.0-1.mga9
python3-pybluez-0.22-9.mga9
bluez-5.82-1.mga9
lib64bluez3-5.82-1.mga9
lib64bluez-devel-5.82-1.mga9
bluez-mesh-5.82-1.mga9
bluez-cups-5.82-1.mga9
bluez-hid2hci-5.82-1.mga9

$ rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

CC: (none) => tarazed25

In reply to comment #16;

With the test audio device still connected:
$ bluetoothctl
Agent registered
[Bose SLIII]> 

So, yes, no problems.

Since everything is fine I think this can be validated.

used on an old intel chromebook.  Works

Installed on some other equipment, no issues.

I agree - I'll validate

Whiteboard: (none) => MGA9-64-OK

Validating.

Keywords: (none) => validated_update
CC: (none) => andrewsfarm, sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2025-0057.html

Resolution: (none) => FIXED
Status: NEW => RESOLVED