public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Puchmayr <alexander.puchmayr@linznet.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Selective news?
Date: Sun, 31 Jul 2022 14:33:39 +0200	[thread overview]
Message-ID: <3024138.1BCLMh4Saa@zeus> (raw)
In-Reply-To: <4431633.LvFx2qVVIh@wstn>

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.








  reply	other threads:[~2022-07-31 12:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 14:27 [gentoo-user] Selective news? Peter Humphrey
2022-07-30 14:36 ` Rich Freeman
2022-07-30 22:12   ` Peter Humphrey
2022-07-31 12:33     ` Alexander Puchmayr [this message]
2022-08-01 23:04       ` Ramon Fischer
2022-08-06  6:19         ` Alexander Puchmayr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3024138.1BCLMh4Saa@zeus \
    --to=alexander.puchmayr@linznet.at \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox