Summary: | Bluetooth headphones spontaneously disconnect | ||
---|---|---|---|
Product: | [Plasma] Bluedevil | Reporter: | Brian DuSell <bdusell> |
Component: | general | Assignee: | David Rosca <nowrep> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | audun, hacknorris, me, nate, nicolas.fella |
Priority: | NOR | ||
Version: | 5.16.5 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Brian DuSell
2019-10-08 01:07:35 UTC
Any thoughts? I came across this bug while reporting a unrelated bug, and I happen to have Sony WH-1000XM2 and KDE on arch. I haven't had any problems, but I'm using pipewire instead of pulseaudio. Are you still experiencing issues? Let me know and I might be able to help. *** Bug 458806 has been marked as a duplicate of this bug. *** Issues like this are almost always not caused by anything in Plasma. Plasma really only tells the underlying system (bluez) to connect to a device, what happens after that is outside of Plasma's involvement/control What part of the stack would it be in? Bluez or the kernel? Anyway to get logging to check (so I can write this down for my bug triaging notes and avoid bugging you in the future :) )? (In reply to Nate Graham from comment #5) > What part of the stack would it be in? Bluez or the kernel? I don't know. I'm not familiar enough with the lower workings of bluetooth to judge that > Anyway to get logging to check (so I can write this down for my bug triaging > notes and avoid bugging you in the future :) )? "journalctl _COMM=bluetoothd" gives you logs about bluetooth, but I don't really know what to look for in it in this case Anyone affected, could you gather a log with `journalctl _COMM=bluetoothd` that shows the output (if any) when the headphones disconnect? will do later. someone gonna play rick astley soon loudly so later means yet today :D Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |