Sound on Chromebook crashes to buzzing

[Steve Fowell]

Running Xubuntu 22.04.1 LTS on Acer Chromebook CB3-111. Sound works fine for about 6 minutes and then crashes to a loud buzzing noise. Same problem in both YouTube and Spotify. After closing the application and restarting it the sound is ok until it crashes again.
This bug does not seem to be unique to my Chromebook. I have seen a couple of other users with different Chromebooks reporting the same problem online. See: https://www.reddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: steve 1065 F.... pulseaudio
 /dev/snd/controlC0: steve 1065 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-02-26 (279 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220225)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:07dc Intel Corp. Bluetooth wireless interface
 Bus 001 Device 002: ID 1bcf:2c67 Sunplus Innovation Technology Inc. HD WebCam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GOOGLE Gnawty
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=f339847e-0075-4998-bf7f-16ae7e0f6e79 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-56-generic N/A
 linux-backports-modules-5.15.0-56-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.7
Tags: jammy
Uname: Linux 5.15.0-56-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/25/2021
dmi.bios.release: 4.14
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.14
dmi.board.name: Gnawty
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.ec.firmware.release: 0.0
dmi.modalias: dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnGnawty:pvr1.0:rvnGOOGLE:rnGnawty:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
dmi.product.name: Gnawty
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1998472/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Steve Fowell (srfman)]

I have been asked in a reply email to add a package name to this bug report. Even after reading the instructions I have no idea what package to specify. I presume that the problem is at kernel level (kernel-sound?). I have also read of the requirement to subscribe to the ubuntu-audio team. Again, I have no idea how to do that.
Incidentally, I forgot to mention, I am referring to the Chromebook speakers in my problem description.
If more information is required please ask and I will oblige!
Thanks
Steve

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1998472

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

apport information

[Steve Fowell (srfman)]

More information:
When using Spotify and sound starts buzzing on internal speakers, Spotify displays the message "Can't play the current song" although time into song keeps counting up. When using Youtube a spinning circle is displayed. In both cases sound keeps playing through USB headphones.

[Steve Fowell (srfman)]

Sorry, should have said in both cases sound keeps playing OK through USB headphones.