unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: chris <chris@bumblehead.com>
To: Sergey Trofimov <sarg@sarg.org.ru>
Cc: chris@bumblehead.com, 68512@debbugs.gnu.org
Subject: bug#68512: Qutebrowser 3, no sound from pipewire-only system
Date: Tue, 16 Jan 2024 12:49:26 -0800	[thread overview]
Message-ID: <Zabr1n5y2rkyk6il@guix-xps> (raw)
In-Reply-To: <87v87tt5tk.fsf@sarg.org.ru>

On  1月16日 火, Sergey Trofimov wrote:

> How is pipewire configured on your system? The thing is that qtwebengine@5
> is linked with PulseAudio and ALSA libraries, but @6 is linked only with
> alsa. You probably miss pipewire-alsa compatibility configuration. Do you
> use home-pipewire-service-type? It sets both pulse/alsa shims and it works
> for me this way.

This system does not use dbus and pipewire was configured about a year ago when there were few options for using pipewire out of the box in any sort of way.

Guix home is configured to write a 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

With with those files in place, pipewire and wireplumber are started 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:[~2024-01-16 20:51 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 16:43 bug#68512: Qutebrowser 3, no sound from pipewire-only system chris
2024-01-16 17:30 ` chris
2024-01-16 17:39 ` chris
2024-01-16 18:12   ` chris
2024-01-16 19:25 ` Sergey Trofimov
2024-01-16 20:49   ` chris [this message]
2024-01-17  6:58     ` Sergey Trofimov
2024-01-17  9:49       ` chris
2024-01-17  9:56         ` chris
2024-01-25  9:09         ` chris
2024-01-25 18:37           ` Sergey Trofimov
2024-01-25 23:26             ` chris
2024-01-26  5:56               ` Sergey Trofimov
2024-01-26  8:18                 ` chris
2024-01-26 12:46                   ` Sergey Trofimov
2024-01-26 23:35                     ` chris
2024-01-26  0:00             ` chris
2024-01-26  6:10               ` Sergey Trofimov
2024-01-26  8:19                 ` chris
2024-01-26  9:45                 ` Clément Lassieur
2024-01-26 23:32                   ` chris
2024-01-26  9:10 ` bug#68512: done chris

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=Zabr1n5y2rkyk6il@guix-xps \
    --to=chris@bumblehead.com \
    --cc=68512@debbugs.gnu.org \
    --cc=sarg@sarg.org.ru \
    /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).