unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "bdju" <bdju@tilde.team>
To: "Alexandru-Sergiu Marton" <brown121407@posteo.ro>
Cc: <help-guix@gnu.org>
Subject: Re: qutebrowser has no sound
Date: Sat, 12 Sep 2020 16:16:08 -0500	[thread overview]
Message-ID: <C5LPARKQGAAQ.282W1VGEVOSBC@masaki> (raw)
In-Reply-To: <87mu1wiog2.fsf@posteo.ro>

On Fri Sep 11, 2020 at 8:43 AM CDT, Alexandru-Sergiu Marton wrote:
> Hi,
>
> I've been occasionally experiencing the same problem. While I don't
> know the permanent fix for this, I found that if I open pavucontrol and
> also play a bit of music with mpv and _only after_ this ritual open
> qutebrowser, I don't have problems with missing sound anymore.
>
> I suspect that it's got something to do with spawning some kind of
> processes for pulseaudio.
>
> Cheers,
> Sergiu

Thank you for the suggestion.
I played some stuff in mpv and restarted qutebrowser, but no dice. Same
when I pkill'd pulseaudio, opened something in mpv, then tried
qutebrowser again. I had qutebrowser open during part of this, so I
tried again, closing qutebrowser, killing pulseaudio, opening mpv, then
finally launching qutebrowser again. I don't get any different results,
so perhaps my issue is not quite the same.
I agree that it's probably something to do with spawning pulseaudio
processes since nothing even shows up for it.


      parent reply	other threads:[~2020-09-12 22:03 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.
2020-09-12 21:16   ` bdju [this message]

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=C5LPARKQGAAQ.282W1VGEVOSBC@masaki \
    --to=bdju@tilde.team \
    --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).