From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6995C158094 for ; Fri, 15 Jul 2022 20:56:37 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 262262BC059; Fri, 15 Jul 2022 20:56:32 +0000 (UTC) Received: from ciao.gmane.io (ciao.gmane.io [116.202.254.214]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 78F9B2BC002 for ; Fri, 15 Jul 2022 20:56:31 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oCSMP-0007BE-Co for gentoo-user@lists.gentoo.org; Fri, 15 Jul 2022 22:56:29 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-user@lists.gentoo.org From: Grant Edwards Subject: [gentoo-user] Re: Google Chrome now requires wayland and jack audio? Date: Fri, 15 Jul 2022 20:56:25 -0000 (UTC) Message-ID: References: User-Agent: slrn/1.0.3 (Linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: ede31577-c90a-4f30-8e02-bf05cea5dc40 X-Archives-Hash: b3a1783f9dace3be0245cf92fb9a5725 On 2022-07-15, Mark Knecht wrote: > On Fri, Jul 15, 2022 at 12:28 PM Grant Edwards > wrote: >> >> It looks like www-client/google-chrome just added wayland and jack >> audio to the dependancies. So now I have to have Pulse _and_ Jack? > Is that truly a Chrome requirement, like the company Google wrote > the ebuild, or is this something a Gentoo dev did for some reason? Google doesn't provide an ebuild. The ebuild is written maintained by the kind volunteers of the Chromium in Gentoo Project. For the binary distribution from Google, those devs have no control over what libraries the Chrome executables are built to use. All they can do is try to figure out which libraries Chrome needs, and reflect that in the ebuild so that after the binary from Google gets installed, it works. That said, there was no jack audio requirement for Chrome. I misread the emerge output. The two new requirements that google-chrome was pulling in were dev-libs/wayland dev-util/wayland-scanner You don't have to be running Wayland, but you now need the above wayland pieces. There isn't actually a pulse audio requirement in the google-chrome ebuild either, but if I don't have pulse installed, some audio stuff in Chrome doesn't work. In web apps like Google Voice * I can select my headset mic as audio in, but it won't work. * I can't select headset as audio out. Installing pulse audio fixed those problems. > I'm curious as the USB disconnect problem seems somehow to be > related to using Chrome on the host machine for sites that do a lot > of audio, like YouTube. A clean boot of the host machine, followed > by a clean boot of the VM and I've run for at least an hour with no > disconnection problems. I can use Chrome for email, messaging and > reading newspapers with no problem, but I run YouTube and twice I've > had USB problems in the VM. Yep, it sounds like doing audio via Chrome is disrupting the the USB audio device that's in-use by the VM. Are there Linux audio drivers for that hardware that you could uninstall to keep Chrome from seeing it? -- Grant