public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/
Date: Wed,  3 Aug 2022 03:04:27 +0000 (UTC)	[thread overview]
Message-ID: <1659495839.6f193859d252b4d7f8cd1ccf5ae875a6049aeed8.sam@gentoo> (raw)

commit:     6f193859d252b4d7f8cd1ccf5ae875a6049aeed8
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Wed Aug  3 03:03:59 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Wed Aug  3 03:03:59 2022 +0000
URL:        https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=6f193859

2022-07-29-pipewire-sound-server: mention systemd --global

Closes: https://bugs.gentoo.org/862867
Signed-off-by: Sam James <sam <AT> gentoo.org>

 .../2022-07-29-pipewire-sound-server.en.txt             | 17 ++++++++++++++++-
 1 file changed, 16 insertions(+), 1 deletion(-)

diff --git a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt
index 31283c0..d41cca1 100644
--- a/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt
+++ b/2022-07-29-pipewire-sound-server/2022-07-29-pipewire-sound-server.en.txt
@@ -116,6 +116,14 @@ There are several options available:
   $ systemctl --user --now enable pulseaudio.service pulseaudio.socket
   $ systemctl --user --now disable pipewire.socket pipewire-pulse.socket
 
+  Alternatively, systemd users can run the following commands as root to change
+  the default for all users:
+  # systemctl --user --global --enable pulseaudio.service pulseaudio.socket
+  # systemctl --user --global --force enable pipewire.socket pipewire-pulse.socket
+
+  (If taking this option, the services must be started manually as a one-off as
+  a user.)
+
 3. For users without sound on their system, those using JACK without
    PipeWire, or those using pure ALSA without PipeWire, the following steps
    are recommended:
@@ -139,11 +147,18 @@ There are several options available:
    files will need to run `gentoo-pipewire-launcher &` in e.g.
    `~/.xprofile`.
 
-   systemd users will also likely want to run the following commands, again
+   systemd users will also likely want to run the following commands as a user, again
    for the purposes of non-audio PipeWire use:
    $ systemctl --user --now enable pipewire.socket
    $ systemctl --user --now --force enable wireplumber.service
 
+   Alternatively, systemd users can run the following commands as root to change
+   the default for all users,  again for the purposes of non-audio PipeWire use:
+   # systemctl --user --global --enable pipewire.socket
+   # systemctl --user --global --force enable wireplumber.service
+
+   (If taking this option, the services must be started manually as a one-off as
+   a user.)
 
 Further resources:
 * https://wiki.gentoo.org/wiki/PipeWire


             reply	other threads:[~2022-08-03  3:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  3:04 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-08-05 10:55 [gentoo-commits] data/gentoo-news:master commit in: 2022-07-29-pipewire-sound-server/ Pacho Ramos
2022-07-31  3:24 Sam James
2022-07-31  3:24 Sam James
2022-07-29  1:44 Sam James

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

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

  git send-email \
    --in-reply-to=1659495839.6f193859d252b4d7f8cd1ccf5ae875a6049aeed8.sam@gentoo \
    --to=sam@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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