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 16A8C158094 for ; Sun, 31 Jul 2022 12:33:53 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 83141E0D97; Sun, 31 Jul 2022 12:33:46 +0000 (UTC) Received: from mail2.netcon.at (mail2.netcon.at [109.70.238.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4C19AE0C0B for ; Sun, 31 Jul 2022 12:33:44 +0000 (UTC) Received: from localhost ([127.0.0.1]) by mail2.netcon.at with ESMTPS (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) for gentoo-user@lists.gentoo.org; Sun, 31 Jul 2022 14:33:41 +0200 Received: from localhost (localhost [127.0.0.1]) by isp1.netcon.at (Postfix) with ESMTP id 5FAC618E1C52 for ; Sun, 31 Jul 2022 14:33:41 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at isp1.netcon.intern Received: from isp1.netcon.at ([127.0.0.1]) by localhost (isp1.netcon.at [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id oQO0nUz00nGi for ; Sun, 31 Jul 2022 14:33:40 +0200 (CEST) Received: from puchmayr.linznet.at (unknown [91.142.26.35]) by isp1.netcon.at (Postfix) with ESMTPS id B572F18E1ADE for ; Sun, 31 Jul 2022 14:33:40 +0200 (CEST) Received: (qmail 2829 invoked from network); 31 Jul 2022 12:32:46 -0000 Received: from zeus.local (HELO zeus.localnet) (192.168.1.2) by mail.local with SMTP; 31 Jul 2022 12:32:46 -0000 From: Alexander Puchmayr To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Selective news? Date: Sun, 31 Jul 2022 14:33:39 +0200 Message-ID: <3024138.1BCLMh4Saa@zeus> In-Reply-To: <4431633.LvFx2qVVIh@wstn> References: <5603487.DvuYhMxLoT@wstn> <4431633.LvFx2qVVIh@wstn> 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 MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 759a41f9-0c68-47f1-8b7b-5cc35628c0c6 X-Archives-Hash: abfe8ea65ab57f08397a2389c8d1749a Same here, pulseaudio daemon is no longer started automatically. Starting it from a shell (simply call pulseaudio ) and audio works fine again. Not sure which start script to add it to; .login or .profile are unsuitable because it would then start it at every login even with ssh). Alex Am Sonntag, 31. Juli 2022, 00:12:49 CEST schrieb Peter Humphrey: > On Saturday, 30 July 2022 15:36:35 BST Rich Freeman wrote: > > From: > > https://gitweb.gentoo.org/data/gentoo-news.git/tree/2022-07-29-pipewire-so > > un d-server/2022-07-29-pipewire-sound-server.en.txt > > > > Display-If-Installed: media-video/pipewire > > Display-If-Installed: media-sound/pulseaudio > > Display-If-Installed: media-sound/pulseaudio-daemon > > Display-If-Installed: media-libs/libpulse > > > > If you have any of those packages installed, the news will display. > > But pulseaudio is installed, having been pulled in by plasma-meta; that's > why I was puzzled. > > $ eix -Ic pulse > [I] media-libs/libpulse (16.1{xpak:2}@30/06/22): Libraries for PulseAudio > clients > [I] media-sound/pulseaudio (16.1{xpak}@10/07/22): A meta package for > PulseAudio (networked sound server) > [I] media-sound/pulseaudio-daemon (16.1{xpak:2}@30/06/22): Daemon component > of PulseAudio (networked sound server) > Found 3 matches > > The only pertinent difference between the machines is that one is amd64, the > other ~amd64. Well, the ~amd64 box has no sound hardware, but apart from > that... > > > We try to filter news so that users aren't bombarded by things that > > aren't relevant to them. > > And it has worked well for me too until now. > > > For example, a few weeks ago there was apparently a corruption in the mu > > MUA (which I'd never heard of), which would be really important to know > > about if you were one of the 0.001% of Gentoo users who rely on it. > > Yes, I saw that, and no, I hadn't heard of it either.