CachyOS / CachyOS/distribution
[Bug]: Bluetooth headphones do not make sound without a disconnect cycle
- Dominant language
- No language data
- Stars
- 27
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
### Kernel
7.2.4-1-cachyos
### Desktop Environment / Window Manager
KDE Plasma
### CPU
AMD RYZEN AI MAX+ PRO 395
### GPU / Driver
AMD Radeon 8060S
### Description
My headphones are the Cleer ARC 4 Plus. They do automatically connect and disconnect as expected when taking them in and out of the charging case. But they don't actually make sound on first connection. They do appear as connected and working though. But disconnecting, then reconnecting fixes this.
Note: I realized this could be a sleep related issue, so I'm editing my steps to add that as a precondition.
### Steps to Reproduce
Preconditions:
Headphones paired with laptop.
Laptop asleep.
Have a process making sound.
1. Open case and pull either or both out.
2. Check that the device is connected, and there is a lack of sound
3. In the bluetooth control panel, disconnect them
4. In the same panel, connect them
5. Check that the device is connected, and sound is now playing.
### Expected Behavior
I expect the connected headphones to playback sound on first connection.
### Actual Behavior
There is no sound, just the bluetooth device acting as the playback device, without actually playing back sound.
### Logs / Error Messages
https://paste.cachyos.org/p/4735c76.log
### Additional Context
Let me know if you need hands on debugging and fixes. I do have developer experience, just not in OS programming.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the listed sleep-and-reconnect reproduction steps and inspect the linked log at paste.cachyos.org/p/4735c76.log. Determine which Bluetooth or audio component owns the failed first connection; done means the Cleer ARC 4 Plus plays sound immediately after waking and connecting, without a manual disconnect cycle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100