unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Diego Nicola Barbato <dnbarbato@posteo.de>
Cc: pkill9 <pkill9@runbox.com>, 40544@debbugs.gnu.org
Subject: bug#40544: Pulseaudio is not looking for user configuration
Date: Wed, 22 Apr 2020 22:00:37 +0200	[thread overview]
Message-ID: <87h7xbthne.fsf@gnu.org> (raw)
In-Reply-To: <877dyfik0x.fsf@GlaDOS.home> (Diego Nicola Barbato's message of "Thu, 16 Apr 2020 16:26:38 +0200")

Hi Diego,

Diego Nicola Barbato <dnbarbato@posteo.de> skribis:

> pkill9 <pkill9@runbox.com> writes:
>
>> Pulseaudio doesn't read my user configuration files according to strace.
>>
>> Attached is the output of `strace -o /tmp/log.log pulseaudio` - It only
>> looks for /etc/pulse/daemon.conf.
>
> That's a known [0] (but AFAIK undocumented) side effect of the
> PulseAudio service, which was added to %desktop-services in January [1].
> If you want PulseAudio to read your user configuration files you'll have
> to remove that service from your system services or unset PULSE_CONFIG
> and PULSE_CLIENT_CONFIG in ~/.profile [2].

It would be good to document that, right below
‘pulseaudio-service-type’.  Would you like to give it a try, Diego?

Or alternately, is there a way we can arrange so that the user’s config
takes precedence over /etc/pulse?

Thanks,
Ludo’.

  parent reply	other threads:[~2020-04-22 20:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10 17:20 bug#40544: Pulseaudio is not looking for user configuration pkill9
2020-04-11 20:26 ` raingloom
2020-04-15 23:09   ` pkill9
2020-04-16 14:26 ` Diego Nicola Barbato
2020-04-17  1:27   ` pkill9
2020-04-22 20:00   ` Ludovic Courtès [this message]
2020-04-28  9:58     ` Diego Nicola Barbato
2020-04-28 20:49       ` Ludovic Courtès

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=87h7xbthne.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40544@debbugs.gnu.org \
    --cc=dnbarbato@posteo.de \
    --cc=pkill9@runbox.com \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).