New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal speakers randomly crashes on Voxel (Acer Chromebook Spin 713-3W Tiger Lake) #2
Comments
This is a known issue that affects a small amount of tgl devices. The only known workaround is to use pulseaudio instead of pipewire. pipewire-media-session instead of pipewire might also work but no one has tested that yet. |
Consider it tested then: I still get the same problem after replacing wireplumber with pipewire-media-session :(
I've tried to do that but seems impossible for my use case (Arch's Is there a relevant upstream bug ticket that I can follow? |
Just remove pipewire-pulse and install pulseaudio.
Not that I know of. |
Huh, that seems to work so far. Thanks! |
@nhanb switch back to pipewire and make sure you are using wireplumber and run the audio script again. It should be fixed now. |
I've switched back to pipewire-pulse and although startup logs still show the same errors, things seem to work fine so far. I'll report back in a few days.
|
Those errors are normal, you can ignore them. |
@nhanb is it still working good? |
Yeah everything seems fine. I don't daily drive the chromebook anymore, but the few times that I actually use it, nothing crashed. Thanks for your work! |
I'm on Arch Linux kernel 6.3.6, using
pipewire-pulse
and KDE. After running this script, the audio devices show up, but if I choose the internal speakers as output then it usually plays sound normally for a while then randomly crashes: sometimes it repeats the last sound indefinitely, sometimes it just stops playing sound at all. Runningsystemctl --user restart wireplumber
makes it work again but it'll eventually bug out the same way. Plugged in headphones and HDMI out seem to work just fine though.Error messages during startup:
Log messages when the crash happens:
More info of my system:
The text was updated successfully, but these errors were encountered: