unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: chris <chris@bumblehead.com>
To: 66877@debbugs.gnu.org
Cc: chris@bumblehead.com
Subject: [bug#66877] [WIP PATCH 1/1] gnu: home: services: Add home-pipewire.
Date: Wed, 1 Nov 2023 11:33:46 -0700	[thread overview]
Message-ID: <ZUKaCkFIb-E6SGCC@guix-xps> (raw)
In-Reply-To: <d2c4964c80599cc20fd981dc76827e52d45d40ea.1698833388.git.sughosha@disroot.org>

Hello, I would like to share my experience that using pipewire without dbus on guix is practical: and so, it would be great if the home-pipewire-service could be used without dbus. Having said that, only a minority of people use dbus-free systems so feel free to ignore me and I do not want to block this patch.

In case it is useful, here is pipewire is used sans dbus. Guix home is configured to write the pipewire and three wireplumber config files, as described at this link https://wiki.alpinelinux.org/wiki/PipeWire#Configuration 

.config/pipewire/pipewire.conf
.config/wireplumber/wireplumber.conf
.config/wireplumber/main.lua.d/80-disable-dbus.lua
.config/wireplumber/bluetooth.lua.d/80-disable-logind.lua

When pipewire and wireplumber are installed with those files in place, start pipewire and wireplumber sequentially to get working sound. I use this in my .config/sway/config (possibly this is copy-pasted from unmatched-paren)
```
exec_always killall -wqr "(pipewire|wireplumber)" \
  || sleep 1 && ((pipewire &); sleep 2 && (wireplumber &))
```




      reply	other threads:[~2023-11-01 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 10:14 [bug#66876] [WIP PATCH 0/1] gnu: home: services: Add home-pipewire Sughosha via Guix-patches via
2023-11-01 10:14 ` [bug#66877] [WIP PATCH 1/1] " Sughosha via Guix-patches via
2023-11-01 18:33   ` chris [this message]

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=ZUKaCkFIb-E6SGCC@guix-xps \
    --to=chris@bumblehead.com \
    --cc=66877@debbugs.gnu.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.
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).