Ubuntu-accessibility Digest, Vol 129, Issue 7

B. Henry burt1iband at gmail.com
Sat Nov 19 19:59:12 UTC 2016


Bad move responding to a digest, at least with subject as a digest number.
As a friendly reminder I am sending this msg, but usually just delete such messages.

-- 
     B.H.
   Registerd Linux User 521886


  Glenn / Lenny wrote:
Fri, Nov 18, 2016 at 01:18:30PM -0600

> Since the wired speakers did not work in the speaker test, but the bluetooth 
> one did, I ran:
> alsactl store
> as suggested, but after rebooting, Orca sounded like another language and 
> English mixed, like part of words were Swedish or something, so I went in 
> and tweaked the Orca settings to American English and rebooted, but now, I 
> have no speech at all, but I hear the speakers pop as usual on startup and a 
> slight speaker hiss, but I just cannot get any audio from Orca.
> I don't know if it is running or not.
> I ran orca, and that did not help.
> I ran as root:
> espeak "hello"
> which usually works, but does not now.
> Speaker-test -c 2
> does not do anything either.
> The bluetooth speaker acts like it is paired, as it beeps after powering up, 
> indicating it paired.
> The speaker pops and hiss come from the wired speaker.
> Is there something I can do to get Orca talking again?
> Thanks.
> 
> Glenn
> ----- Original Message ----- 
> From: <ubuntu-accessibility-request at lists.ubuntu.com>
> 
> > Date: Fri, 18 Nov 2016 10:44:27
> > From: Jude DaShiell <jdashiel at panix.com>
> > To: Glenn / Lenny <gervin at cableone.net>, 
> > ubuntu-accessibility at lists.ubuntu.com
> > Subject: Re: making a bluetooth speaker work
> >
> > That's a pulseaudio/alsa problem depending on what you have on your 
> > system.
> > So pactl or alsamixer will be an intermediate tool for you to use to 
> > adjust
> > output.  A primary command to run for output is aplay -l since that will 
> > tell
> > you about all available devices.  What I would do is first shut the 
> > bluetooth
> > speaker off and run aplay -l and check output.  Then turn on bluetooth
> > speaker and make sure bluetooth speaker is paired and run aplay -l again.
> > See if the output is any different. If so, you probably know which speaker 
> > to
> > set as the default.  Next, study pactl (good luck figuring out their
> > terminology) and learn how to use that if you have pulseaudio installed on
> > your system.  If not, you don't have to deal with pactl or pacmd.  Next 
> > study
> > alsamixer and if you don't have pulseaudio installed, adjust your speaker
> > with alsamixer and test with speakertest once adjusted with connected
> > speakers attached and on.  If the connected speakers are silent but your
> > bluetooth speaker runs then run alsactl store as root and then reboot and 
> > if
> > all works well, your problem is solved.
> >
> > On Thu, 17 Nov 2016, Glenn / Lenny wrote:
> >
> >> Date: Fri, 18 Nov 2016 00:42:12
> >> From: Glenn / Lenny <gervin at cableone.net>
> >> To: ubuntu-accessibility at lists.ubuntu.com
> >> Subject: making a bluetooth speaker work
> >>
> >> Hi,
> >> I am running Ubuntu 16.04 on an Intel NUC PPYH.
> >> I have been using a regular speaker on it, but I want to use an Anker
> >> pocket Bluetooth Speaker.
> >> I got it found and configured from the Bluetooth manager, and in sound in
> >> control center, I can test it fine.
> >> But I cannot get system sounds or Orca to speak from it, the audio only
> >> comes through connected speaker.
> >> So how does one get it to default to the bluetooth speaker?
> >> As mentioned, it works, as the left and right test sounds come from it, 
> >> but
> >> that is the only thing I can get it to do so far.
> >> Thanks for any assistance.
> >> Glenn
> >
> >
> 
> -- 
> -------------- next part --------------
> -- 
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
> -------------- next part --------------
> -- 
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
> 
> ------------------------------
> 
> Message: 4
> Date: Fri, 18 Nov 2016 11:13:09 -0600
> From: "Glenn / Lenny" <gervin at cableone.net>
> To: "Jude DaShiell" <jdashiel at panix.com>,
> <ubuntu-accessibility at lists.ubuntu.com>
> Subject: Re: making a bluetooth speaker work
> Message-ID: <9DF22249A7C54017A710350F8CB86F0F at LennyAcer5720>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi,
> For Juan, I did not have pacucontrol installed, so I installed it.
> It was easy enough to get around with Orca, but I could only read the name
> of the bluetooth speaker with the review controls, the actual cursor would
> never let me navigate to it to control it.
> Jude, I ran alsamixer, and it seemed unusable with Orca.
> When I do aplay -l
> I get a list, but bluetooth speaker on or off, there is no change, and it
> does not show up in the list.
> 
> On another note, I did:
> speaker-test -c 2
> and the bluetooth speaker did the speaker test, but not the wired speaker
> that Orca runs through.
> Glenn
> ----- Original Message ----- 
> From: "Jude DaShiell" <jdashiel at panix.com>
> To: "Glenn / Lenny" <gervin at cableone.net>;
> <ubuntu-accessibility at lists.ubuntu.com>
> Sent: Friday, November 18, 2016 9:44 AM
> Subject: Re: making a bluetooth speaker work
> 
> 
> That's a pulseaudio/alsa problem depending on what you have on your
> system.  So pactl or alsamixer will be an intermediate tool for you to
> use to adjust output.  A primary command to run for output is aplay -l
> since that will tell you about all available devices.  What I would do
> is first shut the bluetooth speaker off and run aplay -l and check
> output.  Then turn on bluetooth speaker and make sure bluetooth speaker
> is paired and run aplay -l again.  See if the output is any different.
> If so, you probably know which speaker to set as the default.  Next,
> study pactl (good luck figuring out their terminology) and learn how to
> use that if you have pulseaudio installed on your system.  If not, you
> don't have to deal with pactl or pacmd.  Next study alsamixer and if you
> don't have pulseaudio installed, adjust your speaker with alsamixer and
> test with speakertest once adjusted with connected speakers attached and
> on.  If the connected speakers are silent but your bluetooth speaker
> runs then run alsactl store as root and then reboot and if all works
> well, your problem is solved.
> 
> On Thu, 17 Nov 2016, Glenn / Lenny wrote:
> 
> > Date: Fri, 18 Nov 2016 00:42:12
> > From: Glenn / Lenny <gervin at cableone.net>
> > To: ubuntu-accessibility at lists.ubuntu.com
> > Subject: making a bluetooth speaker work
> >
> > Hi,
> > I am running Ubuntu 16.04 on an Intel NUC PPYH.
> > I have been using a regular speaker on it, but I want to use an Anker
> > pocket Bluetooth Speaker.
> > I got it found and configured from the Bluetooth manager, and in sound in
> > control center, I can test it fine.
> > But I cannot get system sounds or Orca to speak from it, the audio only
> > comes through connected speaker.
> > So how does one get it to default to the bluetooth speaker?
> > As mentioned, it works, as the left and right test sounds come from it,
> > but that is the only thing I can get it to do so far.
> > Thanks for any assistance.
> > Glenn
> 
> -- 
> 
> 
> 
> --------------------------------------------------------------------------------
> 
> 
> -- 
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
> 
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Fri, 18 Nov 2016 12:42:48 -0500 (EST)
> From: Jude DaShiell <jdashiel at panix.com>
> To: Glenn / Lenny <gervin at cableone.net>,
> ubuntu-accessibility at lists.ubuntu.com
> Subject: Re: making a bluetooth speaker work
> Message-ID: <alpine.NEB.2.20.1611181240450.23525 at panix1.panix.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
> 
> My suggestion then would be to install pacmd and run that in a console
> once you learn how to use it and see if you can change to c2 using pacmd
> as root, then run alsactl store as root and see if that works.
> 
> On Fri, 18 Nov 2016, Glenn / Lenny wrote:
> 
> > Date: Fri, 18 Nov 2016 12:13:09
> > From: Glenn / Lenny <gervin at cableone.net>
> > To: Jude DaShiell <jdashiel at panix.com>, 
> > ubuntu-accessibility at lists.ubuntu.com
> > Subject: Re: making a bluetooth speaker work
> >
> > Hi,
> > For Juan, I did not have pacucontrol installed, so I installed it.
> > It was easy enough to get around with Orca, but I could only read the name
> > of the bluetooth speaker with the review controls, the actual cursor would
> > never let me navigate to it to control it.
> > Jude, I ran alsamixer, and it seemed unusable with Orca.
> > When I do aplay -l
> > I get a list, but bluetooth speaker on or off, there is no change, and it
> > does not show up in the list.
> >
> > On another note, I did:
> > speaker-test -c 2
> > and the bluetooth speaker did the speaker test, but not the wired speaker
> > that Orca runs through.
> > Glenn
> > ----- Original Message -----
> > From: "Jude DaShiell" <jdashiel at panix.com>
> > To: "Glenn / Lenny" <gervin at cableone.net>;
> > <ubuntu-accessibility at lists.ubuntu.com>
> > Sent: Friday, November 18, 2016 9:44 AM
> > Subject: Re: making a bluetooth speaker work
> >
> >
> > That's a pulseaudio/alsa problem depending on what you have on your
> > system.  So pactl or alsamixer will be an intermediate tool for you to
> > use to adjust output.  A primary command to run for output is aplay -l
> > since that will tell you about all available devices.  What I would do
> > is first shut the bluetooth speaker off and run aplay -l and check
> > output.  Then turn on bluetooth speaker and make sure bluetooth speaker
> > is paired and run aplay -l again.  See if the output is any different.
> > If so, you probably know which speaker to set as the default.  Next,
> > study pactl (good luck figuring out their terminology) and learn how to
> > use that if you have pulseaudio installed on your system.  If not, you
> > don't have to deal with pactl or pacmd.  Next study alsamixer and if you
> > don't have pulseaudio installed, adjust your speaker with alsamixer and
> > test with speakertest once adjusted with connected speakers attached and
> > on.  If the connected speakers are silent but your bluetooth speaker
> > runs then run alsactl store as root and then reboot and if all works
> > well, your problem is solved.
> >
> > On Thu, 17 Nov 2016, Glenn / Lenny wrote:
> >
> >> Date: Fri, 18 Nov 2016 00:42:12
> >> From: Glenn / Lenny <gervin at cableone.net>
> >> To: ubuntu-accessibility at lists.ubuntu.com
> >> Subject: making a bluetooth speaker work
> >>
> >> Hi,
> >> I am running Ubuntu 16.04 on an Intel NUC PPYH.
> >> I have been using a regular speaker on it, but I want to use an Anker
> >> pocket Bluetooth Speaker.
> >> I got it found and configured from the Bluetooth manager, and in sound in
> >> control center, I can test it fine.
> >> But I cannot get system sounds or Orca to speak from it, the audio only
> >> comes through connected speaker.
> >> So how does one get it to default to the bluetooth speaker?
> >> As mentioned, it works, as the left and right test sounds come from it,
> >> but that is the only thing I can get it to do so far.
> >> Thanks for any assistance.
> >> Glenn
> >
> >
> 
> -- 
> 
> 
> 
> 
> ------------------------------
> 
> Message: 6
> Date: Fri, 18 Nov 2016 12:37:00 -0600
> From: "Glenn / Lenny" <gervin at cableone.net>
> To: "Jude DaShiell" <jdashiel at panix.com>,
> <ubuntu-accessibility at lists.ubuntu.com>
> Subject: Re: making a bluetooth speaker work
> Message-ID: <84E06DF8A2EB4FBBB9A75EF346FB8D03 at LennyAcer5720>
> Content-Type: text/plain; charset="iso-8859-1"
> 
> I ran
> pacmd
> as root and it came back with:
> home directory not accessible, permission denied
> no pulseaudio deamon running or not running a session deamon.
> 
> 
> Glenn
> ----- Original Message ----- 
> From: "Jude DaShiell" <jdashiel at panix.com>
> To: "Glenn / Lenny" <gervin at cableone.net>;
> <ubuntu-accessibility at lists.ubuntu.com>
> Sent: Friday, November 18, 2016 11:42 AM
> Subject: Re: making a bluetooth speaker work
> 
> 
> My suggestion then would be to install pacmd and run that in a console
> once you learn how to use it and see if you can change to c2 using pacmd
> as root, then run alsactl store as root and see if that works.
> 
> On Fri, 18 Nov 2016, Glenn / Lenny wrote:
> 
> > Date: Fri, 18 Nov 2016 12:13:09
> > From: Glenn / Lenny <gervin at cableone.net>
> > To: Jude DaShiell <jdashiel at panix.com>,
> > ubuntu-accessibility at lists.ubuntu.com
> > Subject: Re: making a bluetooth speaker work
> >
> > Hi,
> > For Juan, I did not have pacucontrol installed, so I installed it.
> > It was easy enough to get around with Orca, but I could only read the name
> > of the bluetooth speaker with the review controls, the actual cursor would
> > never let me navigate to it to control it.
> > Jude, I ran alsamixer, and it seemed unusable with Orca.
> > When I do aplay -l
> > I get a list, but bluetooth speaker on or off, there is no change, and it
> > does not show up in the list.
> >
> > On another note, I did:
> > speaker-test -c 2
> > and the bluetooth speaker did the speaker test, but not the wired speaker
> > that Orca runs through.
> > Glenn
> > ----- Original Message -----
> > From: "Jude DaShiell" <jdashiel at panix.com>
> > To: "Glenn / Lenny" <gervin at cableone.net>;
> > <ubuntu-accessibility at lists.ubuntu.com>
> > Sent: Friday, November 18, 2016 9:44 AM
> > Subject: Re: making a bluetooth speaker work
> >
> >
> > That's a pulseaudio/alsa problem depending on what you have on your
> > system.  So pactl or alsamixer will be an intermediate tool for you to
> > use to adjust output.  A primary command to run for output is aplay -l
> > since that will tell you about all available devices.  What I would do
> > is first shut the bluetooth speaker off and run aplay -l and check
> > output.  Then turn on bluetooth speaker and make sure bluetooth speaker
> > is paired and run aplay -l again.  See if the output is any different.
> > If so, you probably know which speaker to set as the default.  Next,
> > study pactl (good luck figuring out their terminology) and learn how to
> > use that if you have pulseaudio installed on your system.  If not, you
> > don't have to deal with pactl or pacmd.  Next study alsamixer and if you
> > don't have pulseaudio installed, adjust your speaker with alsamixer and
> > test with speakertest once adjusted with connected speakers attached and
> > on.  If the connected speakers are silent but your bluetooth speaker
> > runs then run alsactl store as root and then reboot and if all works
> > well, your problem is solved.
> >
> > On Thu, 17 Nov 2016, Glenn / Lenny wrote:
> >
> >> Date: Fri, 18 Nov 2016 00:42:12
> >> From: Glenn / Lenny <gervin at cableone.net>
> >> To: ubuntu-accessibility at lists.ubuntu.com
> >> Subject: making a bluetooth speaker work
> >>
> >> Hi,
> >> I am running Ubuntu 16.04 on an Intel NUC PPYH.
> >> I have been using a regular speaker on it, but I want to use an Anker
> >> pocket Bluetooth Speaker.
> >> I got it found and configured from the Bluetooth manager, and in sound in
> >> control center, I can test it fine.
> >> But I cannot get system sounds or Orca to speak from it, the audio only
> >> comes through connected speaker.
> >> So how does one get it to default to the bluetooth speaker?
> >> As mentioned, it works, as the left and right test sounds come from it,
> >> but that is the only thing I can get it to do so far.
> >> Thanks for any assistance.
> >> Glenn
> >
> >
> 
> -- 
> 
> 
> 
> 
> ------------------------------
> 
> -- 
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
> 
> 
> End of Ubuntu-accessibility Digest, Vol 129, Issue 7
> **************************************************** 
> 
> 
> -- 
> Ubuntu-accessibility mailing list
> Ubuntu-accessibility at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility




More information about the Ubuntu-accessibility mailing list