From: Brian Cully via Guix-patches via <guix-patches@gnu.org>
To: Andrew Tropin <andrew@trop.in>
Cc: 63863@debbugs.gnu.org
Subject: [bug#63863] [PATCH] gnu: home: Add support for home-pipewire-service
Date: Tue, 13 Jun 2023 08:20:47 -0400 [thread overview]
Message-ID: <87wn07o40w.fsf@psyduck.jhoto.kublai.com> (raw)
In-Reply-To: <87pm602cy3.fsf@trop.in>
Andrew Tropin <andrew@trop.in> writes:
>> Or would something like "PipeWire media processing" seem to
>> suit it
>> better for you?
>
> Yep.
Works for me.
> Anyway, without the config above alsamixer doesn't work on my
> system,
> probably with some configuration it's possible to make it work,
> but
> bypassing pipewire, however I think it would be nice to go full
> pipewire.
I've just tried using ‘alsamixer’ from the ‘alsa-utils’ package
this morning, and it works for me without any additional
configuration. It shows both ‘Card’ and ‘Chip’ to be ‘PulseAudio’,
and volume control works. Although, that is with PulseAudio
emulation enabled. Should the ALSA configuration always be added?
Or just if it's enabled in configuration (possibly defaulting #t)?
-bjc
next prev parent reply other threads:[~2023-06-13 19:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 23:04 [bug#63863] [PATCH] gnu: home: Add support for home-pipewire-service Brian Cully via Guix-patches via
2023-06-09 20:22 ` Ludovic Courtès
2023-06-12 5:50 ` Andrew Tropin
2023-06-12 15:56 ` Brian Cully via Guix-patches via
2023-06-13 4:39 ` Andrew Tropin
2023-06-13 12:20 ` Brian Cully via Guix-patches via [this message]
2023-06-14 9:08 ` Andrew Tropin
2023-06-15 13:16 ` [bug#63863] [PATCH v2] " Brian Cully via Guix-patches via
2023-06-15 13:19 ` Brian Cully via Guix-patches via
2023-06-15 13:26 ` [bug#63863] [PATCH v3] " Brian Cully via Guix-patches via
2023-06-15 13:27 ` Brian Cully via Guix-patches via
2023-06-20 12:41 ` [bug#63863] [PATCH v4 0/1] " Brian Cully via Guix-patches via
2023-06-20 12:41 ` [bug#63863] [PATCH v4 1/1] " Brian Cully via Guix-patches via
2023-07-02 12:39 ` [bug#63863] [PATCH v5 0/1] " Brian Cully via Guix-patches via
2023-07-02 12:39 ` [bug#63863] [PATCH v5 1/1] " Brian Cully via Guix-patches via
2023-11-12 14:14 ` Hilton Chain via Guix-patches via
2023-08-23 8:25 ` Tanguy LE CARROUR
2023-08-23 18:44 ` brian via Guix-patches via
2023-08-25 6:44 ` Tanguy LE CARROUR
2023-10-11 11:34 ` taosabella
2023-11-05 15:09 ` [bug#63863] (no subject) Jakob Honal
2023-12-16 15:17 ` [bug#63863] [PATCH v5 1/1] gnu: home: Add support for home-pipewire-service Brian Cully via Guix-patches via
2023-12-16 15:23 ` [bug#63863] [PATCH v6] " Brian Cully via Guix-patches via
2023-12-20 8:46 ` bug#63863: " Oleg Pykhalov
2023-12-22 15:22 ` [bug#63863] [PATCH v7] " Brian Cully via Guix-patches via
[not found] ` <handler.63863.D63863.17030619999937.notifdone@debbugs.gnu.org>
2023-12-22 15:22 ` [bug#63863] closed (Re: [bug#63863] [PATCH v6] gnu: home: Add support for home-pipewire-service) Brian Cully via Guix-patches via
2023-12-26 12:57 ` bug#63863: " Oleg Pykhalov
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=87wn07o40w.fsf@psyduck.jhoto.kublai.com \
--to=guix-patches@gnu.org \
--cc=63863@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=bjc@spork.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).