public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Chris Brannon <chris@the-brannons.com>
To: speakup@linux-speakup.org
Subject: Re: WARNING: Latest Linphone on Arch breaks device access
Date: Wed, 07 Sep 2016 07:31:47 -0700	[thread overview]
Message-ID: <871t0vok6k.fsf@mushroom.localdomain> (raw)
In-Reply-To: <20160907135053.GE1834@opera.rednote.net> (Janina Sajka's message of "Wed, 7 Sep 2016 09:50:53 -0400")

Janina Sajka <janina@rednote.net> writes:

> Hi, All:
>
> If you use Linphone on Arch, beware. The latest release built 31 August
> introduced what for me is a showstopper bug. I'm referring to
> Linphone-3.10.2-1.

Hi Janina,
I think I might have a solution for you.
The only reason this will work is that you are using the headset for all
three functions: ringer, playback, and capture.  If you needed something
fancier, this falls flat.
You can set a specific default card for a given application using the
ALSA_CARD environment variable.
For instance,
ALSA_CARD=Headset espeak 'Hello there.'
should cause espeak to speak the string through your headset.
So try setting ALSA_CARD when starting linphone.

Now there's another problem in that Linphone seems to want to use
pulseaudio for the default sound output.  Can't help you with that one.
Maybe the config file would at least let you specify alsa rather than
pulse?

-- Chris

  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Janina Sajka
 ` Chris Brannon [this message]
   ` Janina Sajka
     ` John Covici
       ` Janina Sajka
     ` Chris Brannon
       ` Janina Sajka
       ` Janina Sajka
         ` Janina Sajka
           ` Chris Brannon
             ` Janina Sajka

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=871t0vok6k.fsf@mushroom.localdomain \
    --to=chris@the-brannons.com \
    --cc=speakup@linux-speakup.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).