-
Notifications
You must be signed in to change notification settings - Fork 34k
Description
Issue Summary:
Using the "Read Aloud" feature from GitHub Copilot Chat in VS Code causes PipeWire audio to break entirely on Kubuntu 24.04. After triggering speech, all system audio stops working except for headphone output. Even after restarting PipeWire and PulseAudio services, speakers and some audio devices are no longer detected. Only a full system reboot restores audio functionality.
Environment:
- OS: Kubuntu 24.04
- VS Code Version: 1.101.2
- GitHub Copilot Chat Extension Version: 1.344.0
- Installation Type: Snap
- Selected Model: Claude 4 Sonnet
Steps to Reproduce:
-
Open a GitHub Copilot Chat panel in VS Code.
-
Click the speaker button to trigger the "read aloud" feature.
-
Observe that all otner audio stops, yet Copilot is able to keep reading to the end.
-
Immediately after or during playback, all system audio stops.
-
No more audio is able to come out, even for Copilot speech.
-
Run
pactl list short sinks
— speakers are gone, but headphones show up. -
Restart PipeWire with:
systemctl --user restart pipewire pipewire-pulse wireplumber
-
Audio remains broken until a full reboot.
What I've Tried:
- Restarting PipeWire and PulseAudio services.
- Monitoring
pactl list
before/after crash: internal speakers disappear from device lists. - Attempted workaround using only Snap-constrained apps, but only VS Code + Copilot causes this.
Logs & Diagnostics:
- [GitHub Copilot Log](https://pastebin.com/Z1m6YqMA)
- [GitHub Copilot Chat](https://pastebin.com/wATpsXqy)
- [Extension Host Log](https://pastebin.com/05vq7pM6)
- [Main Log](https://pastebin.com/t0eaG1d6)
- [Window Log](https://pastebin.com/DPyRCMgv)
- Interestingly, VS Code Speech's logs are empty.
Additional Notes:
- I do not use accessibility features.
- This bug occurs consistently every time I use the read-aloud feature.
- This has made the feature unusable despite its potential productivity boost.
- Downgrading the extension or using the
.deb
version of VS Code will be tested next. - I have not experienced any issue like this with any other application, with Brave Snap, e.g.
- I wasn't able to find any similar issues
Request: Any insights or fixes would be appreciated. Is this a Copilot TTS bug? Are there any other examples of issues like this with PipeWire? or Snap confinement problem? Maybe some issue acquiring/releasing audio streams/socket?
Thank you!