SUMMARY When I first connected to Yandex Station Lite (Яндекс Станция Лайт) speaker via Bluetooth, Pipewire chose an HSP/HFP AG profile (Адаптер аудиогарнитуры (приёмник A2DP и HSP/HFP AG)) by default — it is not supported by this speaker, but still suggested by Pipewire (I think that should be a separate bug, however I do not know where to report it). As a result of this, the speaker didn't show up in audio settings despite being connected via Bluetooth, resulting in inability to change speaker profile with default tools. In the end, I managed to change profile with pavucontrol. STEPS TO REPRODUCE 1. Connect to a Bluetooth speaker that supports only SBC. 2. Choose HSP/HFP AG profile OBSERVED RESULT The speaker is gone from audio settings, it isn't even shown as an inactive device. EXPECTED RESULT The speaker should remain in audio settings with ability to switch profiles. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.2.3 KDE Frameworks Version: 6.8.0 Qt Version: 6.8.0 Kernel Version: 6.11.8-300.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 30.7 ГиБ of RAM Graphics Processor: AMD Radeon Graphics ADDITIONAL INFORMATION Bluetooth adapter: 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8852AE 802.11ax PCIe Wireless Network Adapter [10ec:8852]
What's the output of these commands when the problem happens pactl list QT_LOGGING_RULES="org.kde.pulseaudio*=true" systemsettings kcm_pulseaudio
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
Created attachment 177775 [details] pactl list output
Created attachment 177776 [details] QT_LOGGING_RULES="org.kde.pulseaudio*=true" systemsettings kcm_pulseaudio output
(In reply to Harald Sitter from comment #1) > What's the output of these commands when the problem happens > > pactl list > QT_LOGGING_RULES="org.kde.pulseaudio*=true" systemsettings kcm_pulseaudio I've attached logs
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-pa/-/merge_requests/318
Git commit 93f7c38450b44c20d455d8a5b9b299591419230d by Harald Sitter. Committed on 31/01/2025 at 09:19. Pushed by sitter into branch 'master'. kcm: make inactive detection more robust a device that has neither sources nor sinks ought to be considered inactive, since it is functionally equal to the off profile M +5 -1 src/kcm/ui/main.qml https://invent.kde.org/plasma/plasma-pa/-/commit/93f7c38450b44c20d455d8a5b9b299591419230d
Git commit 01d4d68630da3386c8ee5edf6b6d604cff291150 by Harald Sitter. Committed on 31/01/2025 at 11:22. Pushed by sitter into branch 'Plasma/6.3'. kcm: make inactive detection more robust a device that has neither sources nor sinks ought to be considered inactive, since it is functionally equal to the off profile (cherry picked from commit 93f7c38450b44c20d455d8a5b9b299591419230d) Co-authored-by: Harald Sitter <sitter@kde.org> M +5 -1 src/kcm/ui/main.qml https://invent.kde.org/plasma/plasma-pa/-/commit/01d4d68630da3386c8ee5edf6b6d604cff291150