From: "bdju" via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "bdju" <bdju@tilde.team>, <45280@debbugs.gnu.org>
Subject: bug#45280: qutebrowser has no audio
Date: Wed, 21 Apr 2021 18:44:31 -0500 [thread overview]
Message-ID: <CATSURNY5GTH.3ICRU3ICCRB6V@masaki> (raw)
In-Reply-To: <C8YNLKB6KMD8.1EKXRV8ZNF9DQ@masaki>
Here's some output when I launch qutebrowser from a terminal. It seems
like it may be using ALSA instead of pulse for some reason.
```
ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
[14812:14812:0421/184051.727290:ERROR:alsa_util.cc(204)] PcmOpen:
default,No such file or directory
ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
[14812:14812:0421/184051.728902:ERROR:alsa_util.cc(204)] PcmOpen:
plug:default,No such file or directory
[14656:13:0421/184058.289956:ERROR:batching_media_log.cc(38)]
MediaEvent: {"error":"FFmpegDemuxer: no supported streams"}
[14656:1:0421/184058.290464:ERROR:batching_media_log.cc(35)] MediaEvent:
{"pipeline_error":14}
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile
ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
[14812:14812:0421/184144.908489:ERROR:alsa_util.cc(204)] PcmOpen:
default,No such file or directory
ALSA lib pcm_dmix.c:1075:(snd_pcm_dmix_open) unable to open slave
[14812:14812:0421/184144.911093:ERROR:alsa_util.cc(204)] PcmOpen:
plug:default,No such file or directory
```
next prev parent reply other threads:[~2021-04-21 23:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 21:29 bug#45280: qutebrowser has no audio bdju via Bug reports for GNU Guix
2020-12-16 23:25 ` Leo Famulari
2021-02-01 20:49 ` Leo Famulari
2021-02-02 1:28 ` bdju--- via Bug reports for GNU Guix
2021-04-21 23:44 ` bdju via Bug reports for GNU Guix [this message]
2022-06-14 23:50 ` bdju via Bug reports for GNU Guix
2021-04-22 13:12 ` bug#45280: Qutebrowser doesn't display embedded mp4 jcguu95
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=CATSURNY5GTH.3ICRU3ICCRB6V@masaki \
--to=bug-guix@gnu.org \
--cc=45280@debbugs.gnu.org \
--cc=bdju@tilde.team \
/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).