From: Marius Bakke <mbakke@fastmail.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>, help-guix@gnu.org
Subject: Re: How to temporarily disable Pulseaudio?
Date: Sun, 19 Apr 2020 17:41:29 +0200 [thread overview]
Message-ID: <87blnnh49i.fsf@devup.no> (raw)
In-Reply-To: <87sggzmtsz.fsf@ambrevar.xyz>
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
Pierre Neidhardt <mail@ambrevar.xyz> writes:
> Hi!
>
> I've got a couple of sound issues which I suspect might be linked to
> Pulseaudio.
>
> I'd like to temporarily disable Pulseaudio and see if I experience those
> issues with ALSA alone.
>
> It seems that Pulseaudio is part of the %desktop-services.
> However it's not listed in
>
> --8<---------------cut here---------------start------------->8---
> sudo herd status
> --8<---------------cut here---------------end--------------->8---
>
> for me. Any idea why?
>
> Killing the pulseaudio process manually results in it being
> automatically started. I suspect that's expected from shepherd.
>
> Any clue how to kill it for real?
Pulseaudio is designed to be started on demand by any application
attempting to use it, so it cannot really be disabled AFAIK...
You could try to build the application you want to test without
Pulseaudio support, and run it after killing the pulseaudio daemon.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-04-19 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 14:30 How to temporarily disable Pulseaudio? Pierre Neidhardt
2020-04-19 15:18 ` Julien Lepiller
2020-04-19 16:18 ` Pierre Neidhardt
2020-04-19 16:50 ` Leo Famulari
2020-04-20 9:42 ` Pierre Neidhardt
2020-04-19 15:41 ` Marius Bakke [this message]
2020-04-19 16:18 ` Pierre Neidhardt
2020-04-20 11:20 ` Ricardo Wurmus
2020-04-21 21:17 ` Pierre Neidhardt
2020-04-19 16:51 ` Leo Famulari
2020-04-20 9:47 ` Pierre Neidhardt
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=87blnnh49i.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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).