From: chris <chris@bumblehead.com>
To: Sergey Trofimov <sarg@sarg.org.ru>, chris@bumblehead.com
Cc: 68512@debbugs.gnu.org
Subject: bug#68512: Qutebrowser 3, no sound from pipewire-only system
Date: Thu, 25 Jan 2024 01:09:47 -0800 [thread overview]
Message-ID: <ZbIlW-jFgKAb51-q@guix-xps> (raw)
In-Reply-To: <Zaeipi3ZiR-lNtWr@guix-xps>
Sergey, your configuration file is working and audio is heard from qutebrowser on this system.
Internet searches surfaced commands like these,
`pw-cli`
`strace -e connect pw-dump >/dev/null`
Error messages were seen relating to socket files not found,
`$XDG_RUNTIME_DIR/pipewire-0`
`$XDG_RUNTIME_DIR/pipewire-0-manager`
Various things attempted, but the socket files missing every time sway started
Finally, tried removing the pipewire-starting parts of the sway config
```
# exec_always killall -wqr "(pipewire|wireplumber)" \
# || sleep 1 && ((pipewire &); sleep 2 && (wireplumber &))
```
Then separately started pipewire and wireplumber "manually" from the shell. The socket files were created and when qutebrowser sound could be heard.
Thank you Sergey,
Chris
next prev parent reply other threads:[~2024-01-25 9:12 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZbIlW-jFgKAb51-q@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.