From: Josselin Poiret <dev@jpoiret.xyz>
To: Brendan Tildesley <mail@brendan.scot>,
"ludo@gnu.org" <ludo@gnu.org>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: PipeWire as a PulseAudio replacement (was Re: The Shepherd on Fibers)
Date: Sat, 26 Mar 2022 16:24:42 +0100 [thread overview]
Message-ID: <87a6dchh39.fsf@jpoiret.xyz> (raw)
In-Reply-To: <780223431.610773.1648104505746@office.mailbox.org>
Hello Brendan,
Brendan Tildesley <mail@brendan.scot> writes:
> I would like to replace pulseaudio with pipewire as the default in
> %desktop-services, the only hurdle is how to launch the user daemons in all the
> different desktop configurations one might use. Other distros use systemd's
> socket activation to magically launch pipewire.
>
> Otherwise XDG autostarts or some kind of guix home service could
> launch it?
The main issue for PipeWire is that it really doesn't support running a
single system-wide daemon as we're doing with PulseAudio, so you would
need to launch it through XDG autostart, guix home or something similar
like you said!
One thing that I think is blocking right now is that PipeWire (or
actually WirePlumber, I don't remember) would need to see some
environment variables set by other user services eg. session D-Bus or
even the compositor, which isn't possible yet with Shepherd.
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-03-26 15:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 6:48 The Shepherd on Fibers Brendan Tildesley
2022-03-26 15:24 ` Josselin Poiret [this message]
2022-03-27 11:55 ` PipeWire as a PulseAudio replacement (was Re: The Shepherd on Fibers) Brendan Tildesley
2022-03-27 21:25 ` raingloom
2022-03-29 13:22 ` Josselin Poiret
2022-04-28 9:27 ` Tanguy LE CARROUR
2022-04-28 12:48 ` Josselin Poiret
2022-04-29 7:28 ` Tanguy LE CARROUR
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=87a6dchh39.fsf@jpoiret.xyz \
--to=dev@jpoiret.xyz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=mail@brendan.scot \
/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).