From: Sergey Trofimov <sarg@sarg.org.ru>
To: chris <chris@bumblehead.com>
Cc: 68512@debbugs.gnu.org
Subject: bug#68512: Qutebrowser 3, no sound from pipewire-only system
Date: Tue, 16 Jan 2024 20:25:44 +0100 [thread overview]
Message-ID: <87v87tt5tk.fsf@sarg.org.ru> (raw)
In-Reply-To: <ZaayK6WLGZQffi2f@guix-xps>
chris <chris@bumblehead.com> writes:
> Hello,
>
> The latest qutebrowser v3 from this pipewire-only system has no
> sound. Related
> messages from the shell process pasted below include CJK
> characters which
> debbugs renders as "??", all CJK messages translate as "file or
> directory not
> found"
>
yeah, debbugs doesn't support unicode on the web fully. But when
checking your messages in emacs debbugs interface, I see the CJK
characters just fine.
> ```
> ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open
> slave
> [3003:3003:0116/083803.232761:ERROR:alsa_util.cc(204)] PcmOpen:
> default,そのようなファイルやディレクトリはありません
> ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open
> slave
> [3003:3003:0116/083803.233758:ERROR:alsa_util.cc(204)] PcmOpen:
> plug:default,そのようなファイルやディレクトリはありません
> ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open
> slave
> [3003:3003:0116/083808.743619:ERROR:alsa_util.cc(204)] PcmOpen:
> default,そのようなファイルやディレクトリはありません
> ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open
> slave
> [3003:3003:0116/083808.744661:ERROR:alsa_util.cc(204)] PcmOpen:
> plug:default,そのようなファイルやディレクトリはありません
> ```
>
> About a year ago, user @iyzsong enabled pipewire support at
> qutebrowser v2 for
> me and sound has been good here until today when qutebrowser v3
> was installed.
> iirc, a flag was enabled in qutebrowser or one of its
> dependencies.
>
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.
next prev parent reply other threads:[~2024-01-16 19:52 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 [this message]
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
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=87v87tt5tk.fsf@sarg.org.ru \
--to=sarg@sarg.org.ru \
--cc=68512@debbugs.gnu.org \
--cc=chris@bumblehead.com \
/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).