Bug 28891

Summary: Sound from chromium is a loud square wave always
Product: Mageia Reporter: w unruh <unruh>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WORKSFORME QA Contact:
Severity: major    
Priority: Normal CC: davidwhodgins, lewyssmith, ouaurelien
Version: 8   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: chromium-browser-stable-89.0.4389.128-1.mga8.src.rpm CVE:
Status comment:

Description w unruh 2021-05-08 18:40:01 CEST
Description of problem: When running chromium  browser, and I for example watch an Amazon prime movie, the sound is simply a loud square wave-- as if there is stong feedback. This changes pitch somewhat if the browser is restarted.

Sound in google Chrome works. aplay file.wav works, but chromium does not.  
chromium-browser-stable-89.0.4389.128-1.mga8

Version-Release number of selected component (if applicable):chromium-browser-stable-89.0.4389.128-1.mga8


How reproducible: Always

Dell xps 13 9360 machine. 
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
lsmod|grep snd 
-----------------------------------
snd_hda_codec_hdmi     73728  1
snd_soc_skl           180224  0
snd_hda_codec_realtek   147456  1
snd_hda_codec_generic    98304  1 snd_hda_codec_realtek
snd_soc_hdac_hda       24576  1 snd_soc_skl
snd_hda_ext_core       36864  2 snd_soc_hdac_hda,snd_soc_skl
snd_soc_sst_ipc        20480  1 snd_soc_skl
snd_soc_sst_dsp        36864  1 snd_soc_skl
snd_soc_acpi_intel_match    45056  1 snd_soc_skl
snd_soc_acpi           16384  2 snd_soc_acpi_intel_match,snd_soc_skl
snd_hda_intel          57344  4
snd_intel_dspcfg       28672  2 snd_hda_intel,snd_soc_skl
soundwire_intel        45056  1 snd_intel_dspcfg
snd_soc_core          323584  3 soundwire_intel,snd_soc_hdac_hda,snd_soc_skl
snd_compress           32768  1 snd_soc_core
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_hda_codec         167936  5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda
ledtrig_audio          16384  2 snd_hda_codec_generic,dell_laptop
snd_hda_core          106496  8 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl
ac97_bus               16384  1 snd_soc_core
snd_hwdep              16384  1 snd_hda_codec
snd_pcm               163840  9 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,soundwire_intel,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core,snd_pcm_dmaengine
snd_timer              40960  1 snd_pcmsnd                   114688  18 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_compress,snd_soc_core,snd_pcm
soundcore              16384  1 snd
--------------------------------------------------------


Steps to Reproduce:
1.
2.
3
Comment 1 Aurelien Oudelet 2021-05-10 14:16:02 CEST
Thanks reporting this.

I can't reproduce on my system: chromium + Amazon Prime Video service.
Sound seems OK, not louder than in Firefox, not louder than other webservice, not louder than music files on my system.

$ inxi -Axx
Audio:     Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: Gigabyte driver: snd_hda_intel 
           v: kernel bus ID: 00:1f.3 chip ID: 8086:a170 
           Device-2: NVIDIA TU116 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel 
           bus ID: 01:00.1 chip ID: 10de:1aeb 
           Sound Server: ALSA v: k5.10.35-desktop-1.mga8

Note that sound comes from Device-1. Bluetooth Headset not affected too.

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0
CC: (none) => ouaurelien
Summary: chromium sound is a a loud square wave always => Sound from chromium is a loud square wave always

Lewis Smith 2021-05-10 21:10:47 CEST

Source RPM: chromium-browser => chromium-browser-stable-89.0.4389.128-1.mga8.src.rpm

Comment 2 w unruh 2021-05-16 21:13:14 CEST
Yes, it does seem to be restricted to the Dell XPS 13. Chromium works fine on my desktop machine. Any suggestions as to what could produce this? It seems that on Chromium the output and input are being fed into each other.
Comment 3 Dave Hodgins 2021-05-16 22:19:11 CEST
Try creating a new user and see if the problem applies for that user too.

CC: (none) => davidwhodgins

Comment 4 w unruh 2021-05-17 01:20:15 CEST
I tried with hnew user, and I still get a loud "square" wave sound with chromium on the new user. I could not run Amazon as chromium claimed that protected content was blocked, but their "solution" did not correspond to anything on my system. (Note that protected content was marked as allowed.) but that is another problem.
Comment 5 Dave Hodgins 2021-05-17 02:04:24 CEST
See if running pavucontrol, and on the input devices tab ensuring the microphone
is muted makes any difference.
Comment 6 w unruh 2021-05-17 19:39:52 CEST
Tried that. That particular computer has no active input so there is no microphone to mute.
As I said, Chrome works fine, Chromium does not. It did work fine on Mga7.
Comment 7 w unruh 2021-05-17 20:02:27 CEST
I just tested with both Mga7 and Mga8 having 89.0.4389.128 chromium-browser
(with an additional -1 at the end for Mga8) 
The sound works fine on Mga7. I get the squarewave on Mga8.
Same home directory, so same configuration on my end. Possibly different system configuration of something.
Comment 8 Lewis Smith 2021-05-17 20:53:19 CEST
Please look at bug 28931 which has references & even a 'fix' for another Chromium sound problem, which looks to be upstream.

CC: (none) => lewyssmith

Comment 9 w unruh 2021-05-17 22:52:03 CEST
I tried the quick fix (--disable-features=...)  but that made no difference. Still the same continuous sound rather than the sound that should be coming out. 

I do not get the same errors when I launch from the CLI
----------------------
planet:0[unruh]>chromium-browser --disable-features=AudioServiceOutOfProcess

(chromium-browser:5945): Gtk-WARNING **: 13:36:06.592: Theme parsing error: gtk.css:2:33: Failed to import: Error opening file /local/home/unruh/.config/gtk-3.0/window_decorations.css: No such file or directory
[5945:5945:0517/133606.700407:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11690 not in allowlist and is not being loaded as a result.
[5945:5945:0517/133606.701377:ERROR:allowlist.cc(66)] Component extension with manifest resource id 11691 not in allowlist and is not being loaded as a result.
ATTENTION: default value of option vblank_mode overridden by environment.
[5975:5975:0517/133607.066166:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[5978:6002:0517/133618.013922:ERROR:ssl_client_socket_impl.cc(924)] handshake failed; returned -1, SSL error code 1, net_error -107
[5975:5975:0517/133656.699185:ERROR:shared_context_state.cc(71)] Skia shader compilation error
------------------------

Errors:
----------------------------------------

I have no idea what "manifest resource id 11690" is supposed to mean, or what 
"/local/home/unruh/.config/gtk-3.0/window_decorations.css" (although that is also there on a machine on which chromium sound is working.)
Comment 10 Lewis Smith 2021-05-19 20:53:06 CEST
I do not thiink we have yet asked for the problem system details:
 $ inxi -MSAxx
plus perhaps:
 $ pactl info
This is all puzzling:
> I just tested with both Mga7 and Mga8 having 89.0.4389.128 chromium-browser
> The sound works fine on Mga7. I get the squarewave on Mga8.
> Same home directory, so same configuration on my end
> it does seem to be restricted to the Dell XPS 13.
> Chromium works fine on my desktop machine
> Chrome works fine, Chromium does not
If you use Plasma (I think you do), Bug 28299 may help the Gtk WARNING. See both the attachment, and this:
 https://bugs.mageia.org/show_bug.cgi?id=28299#c6

To clarify: this happens on one particular machine (Dell XPS 13). Does this have both M7 & M8 using the same home directory? This is what you seem to describe.
Comment 11 w unruh 2021-05-20 00:00:27 CEST
INXI
  
System:
  Host: planet Kernel: 5.10.33-server-1.mga8 x86_64 bits: 64 compiler: gcc v: 10.3.0
  Desktop: KDE Plasma 5.20.4 tk: Qt 5.15.2 wm: kwin_x11 dm: LightDM, SDDM
  Distro: Mageia 8 mga8
Machine:
  Type: Laptop System: Dell product: XPS 13 9360 v: N/A serial: <superuser required>
  Chassis: type: 9 serial: <superuser required>
  Mobo: Dell model: 0JGD96 v: A00 serial: <superuser required> UEFI: Dell v: 2.10.0
  date: 09/27/2018
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Dell driver: snd_hda_intel
  v: kernel bus ID: 00:1f.3 chip ID: 8086:9d71
  Sound Server: ALSA v: k5.10.33-server-1.mga8

PA

Server String: /run/user/1000/pulse/native
Library Protocol Version: 34
Server Protocol Version: 34
Is Local: yes
Client Index: 6
Tile Size: 65472
User Name: unruh
Host Name: planet
Server Name: pulseaudio
Server Version: 14.2.0-2.1.mga8
Default Sample Specification: s16le 2ch 44100Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_output.pci-0000_00_1f.3.analog-stereo
Default Source: alsa_output.pci-0000_00_1f.3.analog-stereo.monitor
Cookie: 9db2:9125




Yes, on both Mga7 and Mga8 I have the same home directory. However, I also ran a test in which I used a new test user on Mga8 and that had the same problem with Chromium.
I will try the gtk3 addition. That complaint did not seem to be relevant to my problem but included it just in case I was misunderstanding something.
Comment 12 Aurelien Oudelet 2021-05-21 03:11:18 CEST
One last question, does this system have microphone?

If there is one microphone, disable it in Plasma applet and try again chromium, please.

The gtk3 error is unrelated.

Ever confirmed: 0 => 1
Status: UNCONFIRMED => NEEDINFO

Comment 13 Lewis Smith 2021-05-21 21:25:20 CEST
(In reply to Aurelien Oudelet from comment #12)
> The gtk3 error is unrelated.
I suspect the same; it was 'just in case'.
Comment 14 w unruh 2021-06-29 23:12:57 CEST
Jus to report, the problem seems to have resolved itself, either because of some update or something else. I have realised that I have not had the problem for at lest 3 weeks now. I cannot say what solved it.
Comment 15 Aurelien Oudelet 2021-06-30 05:49:45 CEST
(In reply to w unruh from comment #14)
> Jus to report, the problem seems to have resolved itself, either because of
> some update or something else. I have realised that I have not had the
> problem for at lest 3 weeks now. I cannot say what solved it.

Perhaps a kernel update?

Thanks for reporting.
Closing.

Status: NEEDINFO => RESOLVED
Resolution: (none) => WORKSFORME