From mboxrd@z Thu Jan  1 00:00:00 1970
From: Leo Famulari <leo@famulari.name>
Subject: Re: How to temporarily disable Pulseaudio?
Date: Sun, 19 Apr 2020 12:50:12 -0400
Message-ID: <20200419165012.GA10763@jasmine.lan>
References: <87sggzmtsz.fsf@ambrevar.xyz>
 <1156ABB5-2818-46F3-BEFC-761A3FAE839A@lepiller.eu>
 <87ftczmosu.fsf@ambrevar.xyz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:45842 helo=eggs1p.gnu.org)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <leo@famulari.name>) id 1jQD9G-00013i-Fj
 for help-guix@gnu.org; Sun, 19 Apr 2020 12:50:26 -0400
Received: from Debian-exim by eggs1p.gnu.org with spam-scanned (Exim 4.90_1)
 (envelope-from <leo@famulari.name>) id 1jQD9F-0005aj-Lu
 for help-guix@gnu.org; Sun, 19 Apr 2020 12:50:26 -0400
Received: from out1-smtp.messagingengine.com ([66.111.4.25]:56319)
 by eggs1p.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <leo@famulari.name>) id 1jQD9E-0005WE-Ve
 for help-guix@gnu.org; Sun, 19 Apr 2020 12:50:25 -0400
Content-Disposition: inline
In-Reply-To: <87ftczmosu.fsf@ambrevar.xyz>
List-Id: <help-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-guix>,
 <mailto:help-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/help-guix>
List-Post: <mailto:help-guix@gnu.org>
List-Help: <mailto:help-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-guix>,
 <mailto:help-guix-request@gnu.org?subject=subscribe>
Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org
Sender: "Help-Guix" <help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org

On Sun, Apr 19, 2020 at 06:18:57PM +0200, Pierre Neidhardt wrote:
> In my case the daemon gets restarted directly, no need to start an audio program.

You'll have to look closely at your running programs. It's likely that
one of them is starting it. Probably your desktop manager if you can't
think of anything else.