From: Christopher Lemmer Webber <cwebber@dustycloud.org>
To: Quiliro Ordonez Baca <quiliro@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: mumble unable to recognize mic and speakers
Date: Tue, 02 Jan 2018 11:17:02 -0600 [thread overview]
Message-ID: <87h8s4yycx.fsf@dustycloud.org> (raw)
In-Reply-To: <87a7y59onn.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me>
You may need to do one of the following:
- go to audio input / audio output and select the right device
- maybe use the "pavucontrol" pulseaudio configuration tool to
configure things
Quiliro Ordonez Baca writes:
> I am using a macbook air from 2009 where the speakers are correctly
> configured. But mumble will not recognize them.
>
> Please give me a tip to get it configured. Thank you.
>
> Quiliro
next prev parent reply other threads:[~2018-01-02 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 21:15 mumble unable to recognize mic and speakers Quiliro Ordonez Baca
2018-01-02 17:17 ` Christopher Lemmer Webber [this message]
2018-01-02 20:06 ` ng0
2018-01-11 3:06 ` Quiliro Ordonez Baca
2018-01-11 2:32 ` Quiliro Ordonez Baca
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=87h8s4yycx.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=help-guix@gnu.org \
--cc=quiliro@riseup.net \
/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).