From: ng0 <contact.ng0@cryptolab.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: mumble issues with pulseaudio
Date: Sun, 2 Apr 2017 10:59:02 +0000 [thread overview]
Message-ID: <20170402105902.hx2y55dejuftxooh@abyayala> (raw)
In-Reply-To: <8737drcgym.fsf@gnu.org>
Ludovic Courtès transcribed 0.8K bytes:
> Hello,
>
> ng0 <contact.ng0@cryptolab.net> skribis:
>
> > Ludovic Courtès transcribed 0.9K bytes:
>
> [...]
>
> >> PulseAudio works best when all the applications on the system use it.
> >> :-) You can check with ‘pavucontrol’ the list of applications currently
> >> doing audio with PulseAudio.
> >
> > The problem is that mumble sometimes appears in Applications of
> > pavucontrol and sometimes it doesn't.
>
> This is weird: I would expect it to always appear under “Applications”
> or to never appear, but not something in between. Anyway, that suggests
> Mumble is indeed using PulseAudio.
>
> When it shows up under “Applications”, can you hear its audio output?
> (Assuming the sliders and mute buttons in pavucontrol are all properly
> set.)
Yes, in this case I can. I'll start it via console now every time I use
it to see if I can catch the error output next time I get the error.
> HTH,
> Ludo’.
>
prev parent reply other threads:[~2017-04-02 10:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-31 18:23 mumble issues with pulseaudio ng0
2017-04-01 13:15 ` Ludovic Courtès
2017-04-01 15:43 ` ng0
2017-04-01 15:46 ` ng0
2017-04-02 9:33 ` Florian Paul Schmidt
2017-04-02 9:38 ` Florian Paul Schmidt
2017-04-03 10:08 ` Ludovic Courtès
2017-04-03 15:41 ` Alex Kost
2017-04-03 15:52 ` ng0
2017-04-03 21:18 ` Ludovic Courtès
2017-04-05 9:45 ` Alex Kost
2017-04-05 9:57 ` ng0
2017-04-05 12:47 ` Florian Paul Schmidt
2017-04-08 20:32 ` Ludovic Courtès
2017-04-02 9:10 ` Ludovic Courtès
2017-04-02 10:59 ` ng0 [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170402105902.hx2y55dejuftxooh@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=help-guix@gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.