qutebrowser has no audio

  • Done
  • quality assurance status badge
Details
3 participants
  • bdju
  • jcguu95
  • Leo Famulari
Owner
unassigned
Submitted by
bdju
Severity
normal
B
B
bdju wrote on 16 Dec 2020 22:29
(address . bug-guix@gnu.org)
C7UJ2WOLE9EN.ORS0X0GW9Y07@masaki
guix (GNU Guix) 91e35e32a4938e0e37499c64fa8ed3e7cf51dce3
qutebrowser v1.14.0
full :version output of qutebrowser:
Has been going on for months now, but I don't think I filed a bug.
Does not show up at all in pavucontrol.
L
L
Leo Famulari wrote on 17 Dec 2020 00:25
(name . bdju via Bug reports for GNU Guix)(address . bug-guix@gnu.org)(address . 45280@debbugs.gnu.org)
X9qXfzPsdlfUosIg@jasmine.lan
On Wed, Dec 16, 2020 at 03:29:42PM -0600, bdju via Bug reports for GNU Guix wrote:
Toggle quote (7 lines)
> guix (GNU Guix) 91e35e32a4938e0e37499c64fa8ed3e7cf51dce3
> qutebrowser v1.14.0
> full :version output of qutebrowser:
> https://paste.the-compiler.org/view/ea2d3602
> Has been going on for months now, but I don't think I filed a bug.
> Does not show up at all in pavucontrol.

Is this on Guix System or another distro?

Could it be #40832 (alsa-lib cannot find its plugins)?

That bug breaks audio of Guix applications on foreign distros in many
cases.
L
L
Leo Famulari wrote on 1 Feb 2021 21:49
(name . bdju via Bug reports for GNU Guix)(address . bug-guix@gnu.org)(address . 45280-done@debbugs.gnu.org)
YBhpab2ekYIGEJYv@jasmine.lan
On Wed, Dec 16, 2020 at 06:25:51PM -0500, Leo Famulari wrote:
Toggle quote (16 lines)
> On Wed, Dec 16, 2020 at 03:29:42PM -0600, bdju via Bug reports for GNU Guix wrote:
> > guix (GNU Guix) 91e35e32a4938e0e37499c64fa8ed3e7cf51dce3
> > qutebrowser v1.14.0
> > full :version output of qutebrowser:
> > https://paste.the-compiler.org/view/ea2d3602
> > Has been going on for months now, but I don't think I filed a bug.
> > Does not show up at all in pavucontrol.
>
> Is this on Guix System or another distro?
>
> Could it be #40832 (alsa-lib cannot find its plugins)?
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=40832
>
> That bug breaks audio of Guix applications on foreign distros in many
> cases.

Closing due to lack of info. Please feel free to re-open if the bug
still occurs :)
B
B
bdju wrote on 2 Feb 2021 02:28
qutebrowser has no audio
(address . 45280@debbugs.gnu.org)
C8YNLKB6KMD8.1EKXRV8ZNF9DQ@masaki
Sorry I don't think I saw the previous reply. Absolutely still a
problem. I am on Guix System. It is not at all a system-wide issue. Most
things have sound working fine.
B
B
bdju wrote on 22 Apr 2021 01:44
CATSURNY5GTH.3ICRU3ICCRB6V@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
```
J
J
jcguu95 wrote on 22 Apr 2021 15:12
Qutebrowser doesn't display embedded mp4.
(address . 45280@debbugs.gnu.org)
874kfyzcib.fsf@gmail.com
Hello,

I'm on guix system with the latest `qutebrowser' from the official
channel. While reading this [site] I realize that embedded mp4 files do
not play well. Turning on qb again from the terminal allowed me to see
the complaints. I believe this could be related issues to OP, so decided
to post it here.

,----
| [5173:12:0421/182550.069329:ERROR:batching_media_log.cc(38)]
| MediaEvent: {"error":"FFmpegDemuxer: no supported streams"}
| [5173:1:0421/182550.373463:ERROR:batching_media_log.cc(35)]
| MediaEvent: {"pipeline_error":14}
| [5173:12:0421/182550.514768:ERROR:batching_media_log.cc(38)]
| MediaEvent: {"error":"FFmpegDemuxer: no supported streams"}
| [5173:12:0421/182550.516035:ERROR:batching_media_log.cc(38)]
| MediaEvent: {"error":"FFmpegDemuxer: no supported streams"}
| [5173:1:0421/182550.520021:ERROR:batching_media_log.cc(35)]
| MediaEvent: {"pipeline_error":14}
| [5173:1:0421/182550.528375:ERROR:batching_media_log.cc(35)]
| MediaEvent: {"pipeline_error":14}
| [5173:12:0421/182550.553097:ERROR:batching_media_log.cc(38)]
| MediaEvent: {"error":"FFmpegDemuxer: no supported streams"}
| [5173:1:0421/182550.553613:ERROR:batching_media_log.cc(35)]
| MediaEvent: {"pipeline_error":14}
| [5173:12:0421/182550.591314:ERROR:batching_media_log.cc(38)]
| MediaEvent: {"error":"FFmpegDemuxer: no supported streams"}
| [5173:1:0421/182550.591727:ERROR:batching_media_log.cc(35)]
| MediaEvent: {"pipeline_error":14}
| [5141:5156:0421/182557.327374:ERROR:ssl_client_socket_impl.cc(959)]
| handshake failed; returned -1, SSL error code 1, net_error -113
`----

-- Best, Jin


B
B
bdju wrote on 15 Jun 2022 01:50
Re: bug#45280: qutebrowser has no audio
CKQ9DCTU50C2.297WBG08EYSA6@masaki
I have finally gotten sound working. I needed to enable an alsa service
(which also required the sound and possibly audio use-service-modules)
aplay and speaker-test were failing, which seemed to possibly be due to
a lack of /etc/asound.conf, and I found in the manual that the alsa
service creates this file. After enabling that service, I just had to
restart qutebrowser.
As an aside, I think if our qutebrowser package were built with the
optional pulseaudio support enabled, I would never have hit this issue.
Although you could argue that having broken alsa was probably not good
anyway.

I will finally close this issue.
Closed
?