[SOLVED] Blueman-manager not working properly

kgha · 04-14-2024, 03:57 AM

Don't know when this happened, but I suddenly noticed that Blueman no longer works properly.

My BT devices connect OK, but the tray icon doesn't change colour to indicate connection, and when checking in the gui (Devices > Info) it says "connected no". No pop-up notifications when connecting/disconnecting.

Reverting to previous version (blueman-2.4) doesn't make any difference.

Anyone else experiencing the same? Possible solutions?

mickski56 · 04-14-2024, 04:29 AM

I think it's kernel related. Started happening for me from 6.6.23 onwards (or at least reverting to 6.6.22 made it go away), on slackware64 15.0.
Some possibly related discussion at "https://www.linuxquestions.org/questions/slackware-14/generic-kernel-config-changed-bluetooth-mouse-no-longer-works-4175735404/"
I haven't found a solution yet.

kgha · 04-14-2024, 05:18 AM

Interesting... although in the thread you mention the OP states that the regression was fixed in kernel 6.6.25, and I'm on 6.6.27 (lastest -current kernel).

I've raised the issue at https://github.com/blueman-project/blueman so let's see what happens there.

kgha · 04-14-2024, 08:54 AM

Got an explanation at github.com/blueman: apparently it's a kernel regression from 6.6.23 and onwards, not yet fixed in any release:
https://bugzilla.kernel.org/show_bug.cgi?id=218680

I've mentioned this in the "Requests" thread, maybe Pat can give us a kernel upgrade without the commit that's caused it.

mickski56 · 04-14-2024, 09:14 AM

The proposed fix does work on kernel 6.6.27. Here's hoping it makes it into the next kernel release.

Petri Kaukasoina · 04-14-2024, 10:18 AM

It's in Linus's tree since 2024-04-10, so it will be in 6.9-rc4 later today. But I didn't see it cc'd to stable@kernel.org.

kgha · 04-15-2024, 01:50 AM

At github.com/blueman, Christopher Schramm has written;
"Double checked now. 6.9 will work and I also expect the fix in 6.8.7 and 6.6.28."
Let's hope he's right about 6.6.28.

mickski56 · 04-15-2024, 10:31 AM

Fix is included in 6.6.28-rc1

kgha · 04-15-2024, 10:47 AM

Quote:

Originally Posted by mickski56

Fix is included in 6.6.28-rc1

Great, if no issues are discovered in the -rc1 it should be in the repo within a couple of days

kgha · 04-18-2024, 01:34 AM

Solved in latest kernel for -current (6.6.28).