From: "Bonface M. K." <bonfacemunyoki@gmail.com>
To: Alexandru-Sergiu Marton <brown121407@posteo.ro>
Cc: help-guix@gnu.org
Subject: Re: qutebrowser has no sound
Date: Sat, 12 Sep 2020 19:21:27 +0300 [thread overview]
Message-ID: <86sgbn9da0.fsf@gmail.com> (raw)
In-Reply-To: <87ft7nnsbo.fsf@posteo.ro> (Alexandru-Sergiu Marton's message of "Sat, 12 Sep 2020 14:32:43 +0300")
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Alexandru-Sergiu Marton <brown121407@posteo.ro> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Pulseaudio should be started automatically (via dbus?) by applications
>> with pulseaudio support. Perhaps qutebrowser doesn’t do the right thing
>> here. Will it attempt to connect to ALSA?
>
> I don't know how to check if it attempts to connect to ALSA. I couldn't
> find anything on the Internet about checking this either, but that might
> be because I don't know anything about sound systems to start with.
>
> If anyone could provide some pointers I can try to look into this.
>
I don't know if this will help you in troubleshooting this particular
case but you could try:
https://bbs.archlinux.org/viewtopic.php?id=246733. I hope that thread
provides some pointers.
> Sergiu
>
>
--
Bonface M. K. (https://www.bonfacemunyoki.com)
One Divine Emacs To Rule Them All
GPG key = D4F09EB110177E03C28E2FE1F5BBAE1E0392253F
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next prev parent reply other threads:[~2020-09-12 16:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 6:29 qutebrowser has no sound bdju
2020-09-09 8:36 ` Pierre Neidhardt
2020-09-09 22:17 ` raingloom
2020-09-10 10:02 ` Pierre Neidhardt
2020-09-11 10:43 ` Alexandru-Sergiu Marton
2020-09-11 8:20 ` Ricardo Wurmus
2020-09-12 11:32 ` Alexandru-Sergiu Marton
2020-09-12 16:21 ` Bonface M. K. [this message]
2020-09-12 21:16 ` bdju
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=86sgbn9da0.fsf@gmail.com \
--to=bonfacemunyoki@gmail.com \
--cc=brown121407@posteo.ro \
--cc=help-guix@gnu.org \
/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.
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).