Bug 472847 - All playback devices are muted when bluetooth keyboard is switched
Summary: All playback devices are muted when bluetooth keyboard is switched
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-07-31 15:57 UTC by Jee
Modified: 2023-08-04 19:21 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jee 2023-07-31 15:57:27 UTC
SUMMARY

Hi, I am new to linux and started off with Nobara KDE and facing a problem with my bluetooth keyboard. It can store up to 3 devices and can switch between them. Whenever I switch out of the system to my laptop it force mutes all playback device without interfering with media and I have to toggle it back on manually or spam commands for unmute with script. I believe its a bug in powerdevil from the logs and got an suggestion to post a bug report here.

Links for images and logs:
1. Screenshots: https://imgur.com/a/EcMbW26
2. Log from inxi: https://pastebin.com/gDUtZgbY


STEPS TO REPRODUCE
1. Connect keyboard to system with bluetooth
2. Switch to another device with keyboard key combination

OBSERVED RESULT
All playback devices are muted immediately and have to turned back on manually

EXPECTED RESULT
Audio devices shouldn't be muted and continue operating


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Nobara Linux 38
KDE Plasma Version: 5.27.6
KDE Frameworks Version: 5.108.0
Qt Version: 5.15.10
Comment 1 Nate Graham 2023-08-04 19:21:27 UTC
Hello, and thanks for the bug report. Powerdevil doesn't have the ability to do this, so it's not that. Bluez might, but that's not a KDE component; it's something in the Linux Kernel. It's also possible that PipeWire is watching for Bluetooth connections and it's mistakenly classified your keyboard as a headset or something. But that again does not involve any KDE code; all of this stuff takes place at a level below us.

So at the moment it is not clear that there's a bug in any KDE code here. I'd recommend that you follow up with your distro and ask them to help you pinpoint the exact cause and they can direct you to the right place to submit a bug report.

If they directed you here, ask them to try again. :)