SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,081
Rep:
Blueman-manager not working properly
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?
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.
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,081
Original Poster
Rep:
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).
Distribution: Slackware 64 -current multilib from AlienBob's LiveSlak MATE
Posts: 1,081
Original Poster
Rep:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.