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 D11E0158094 for ; Fri, 15 Jul 2022 20:42:55 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7BF84E0FAA; Fri, 15 Jul 2022 20:42:48 +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 E1315E0DEB for ; Fri, 15 Jul 2022 20:42:47 +0000 (UTC) Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1oCS98-0009pJ-Pw for gentoo-user@lists.gentoo.org; Fri, 15 Jul 2022 22:42:46 +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:42:40 -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: 03df4d50-07e2-4ae0-9090-df40c8719d97 X-Archives-Hash: 9a2ed0ace57fdd1ec050924c428792b7 On 2022-07-15, Julien Roy wrote: > One of the side effects of using proprietary software : you can't > control with which flags it gets built. Yep. I didn't used to have the chrome binary package installed, but there are a couple things that I've never gotten to work in Chromium (e.g. Webex). > With chromium-bin, there is a wayland USE flag, but nothing for > jack. I looked into that more, and I had misread the emerge output. It wasn't google-chrome that depended on jack, and now I can't figure out why it was installed. I did # emerge -C virtual/jack media-sound/jack-audio-connection-kit # emerge -auvND world It didn't get reinstalled. And then a subsequenct # emerge --depclean --ask removed another half-dozen audio-related packagets (zita-* and realtime-*, whatever they are). I'm sure the next time I try to use audio on that machine it won't work. I used to think that someday Linux sound support would get straightened out, but it just keeps getting worse... -- Grant