unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Robby Zambito <contact@robbyzambito.me>
To: help-guix <help-guix@gnu.org>
Subject: Eradicating PulseAudio
Date: Sun, 20 Aug 2023 12:28:06 -0400	[thread overview]
Message-ID: <878ra4jcli.fsf@robbyzambito.me> (raw)

Hi,

Please help me eradicate PulseAudio from my system. It causes me nothing
but pain. My most commonly run commands according to my bash history are
pulsemixer followed by pgrep pulseaudio, which I use to debug my audio
issues, and pkill pulseaudio followed by herd restart pipewire which I
use to resolve my audio issues caused by pulseaudio being started by
Shepherd.

I don't need or want PulseAudio. The only reference I have to PulseAudio
in my system or home config is the following: 

(service alsa-service-type
         (alsa-configuration (pulseaudio? #f)))

In my system service configuration, with hopes to disable it
(unsuccessfully). I use %base-services rather than %desktop-services to
avoid the pulseaudio service that the latter includes.

How can I transform every package on my system to remove PulseAudio from
being an input? How can I stop Shepherd from starting PulseAudio against
my will, when there is no pulseaudio service in my home or system
configuration?

FWIW every package on my system is either installed through my system
config.scm or my home config.scm, so I can apply Scheme transformations
to every package easily.

I also see that there is an issue open to add a PipeWire Home
service[1]. I have a very similar service for my own setup that I wrote
myself. I skimmed through it, but I cannot see anything that actually
stops PulseAudio from loading. Does anyone know if this patch will just
resolve my issue?

Many thanks,
Robby

Footnotes:
[1]  https://issues.guix.gnu.org/63863



             reply	other threads:[~2023-08-21 21:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-20 16:28 Robby Zambito [this message]
2023-08-22  9:41 ` Eradicating PulseAudio 宋文武
2023-08-23 22:29   ` Robby Zambito

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=878ra4jcli.fsf@robbyzambito.me \
    --to=contact@robbyzambito.me \
    --cc=help-guix@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).