Getting speakup to run on debian

[Brandon Keith Biggs]

Hello,
I just installed debian and can't figure out how to get speakup to work.
I type ctrl+meta+f1 to open the terminal, then I type espeakup. I get
the message that espeakup is already running. But I can't get any output
from typing or moving around. I know speakup is running because I have
it in a VM and sometimes speakup and Orca like to say random words and
speakup just said something to me, but I can't hear anything. I also
don't get speech on any log-in screen.
Thanks,

[John G Heim]

It is probably a conflict with pulseaudio and alsa. Right now I am a
little fuzzy on the details but I believe that orca and gnome load pulse
drivers and espeak needs alsa. You can test whether this is the problem
by not logging into the GUI before running espeak. So at the gnome login
screen, press control+alt+f1 to get to the console, log in and start
espeakup. Then go back to the login screen by pressing control+alt+f7
and log into the gui. Make sure orca is running. Then go back once again
to the console by pressing control+alt+f1. At this point, I will bet
that software speech is not working for you.

I think you can fix this by recompiling espeakup to default to using
pulseaudio. Instructions for that are somewhere on google. If you can't
find them, I can probably dig them out again.

Post by Brandon Keith Biggs
Hello,
I just installed debian and can't figure out how to get speakup to work.
I type ctrl+meta+f1 to open the terminal, then I type espeakup. I get
the message that espeakup is already running. But I can't get any output
from typing or moving around. I know speakup is running because I have
it in a VM and sometimes speakup and Orca like to say random words and
speakup just said something to me, but I can't hear anything. I also
don't get speech on any log-in screen.
Thanks,

[a***@icsmail.net]

Hi. The Debian live cd for Jessie can run both espeak and orca at the
same time, so I suspect they've recompiled espeak to work with pulse
audio. However, when I tried an apt-get dist-upgrade, the problem
persists. I'm having problems getting the debian-installer-launcher to
run from the cd. It keeps trying to activate the framebuffer, and
hanging. An interesting catch 22.

Gene

SXQgaXMgcHJvYmFibHkgYSBjb25mbGljdCB3aXRoIHB1bHNlYXVkaW8gYW5kIGFsc2EuIFJpZ2h0
IG5vdyBJIGFtIGEgCmxpdHRsZSBmdXp6eSBvbiB0aGUgZGV0YWlscyBidXQgSSBiZWxpZXZlIHRo
YXQgb3JjYSBhbmQgZ25vbWUgbG9hZCBwdWxzZSAKZHJpdmVycyBhbmQgZXNwZWFrIG5lZWRzIGFs
c2EuIFlvdSBjYW4gdGVzdCB3aGV0aGVyIHRoaXMgaXMgdGhlIHByb2JsZW0gCmJ5IG5vdCBsb2dn
aW5nIGludG8gdGhlIEdVSSBiZWZvcmUgcnVubmluZyBlc3BlYWsuIFNvIGF0IHRoZSBnbm9tZSBs
b2dpbiAKc2NyZWVuLCBwcmVzcyBjb250cm9sK2FsdCtmMSB0byBnZXQgdG8gdGhlIGNvbnNvbGUs
IGxvZyBpbiBhbmQgc3RhcnQgCmVzcGVha3VwLiBUaGVuIGdvIGJhY2sgdG8gdGhlIGxvZ2luIHNj
cmVlbiBieSBwcmVzc2luZyBjb250cm9sK2FsdCtmNyAKYW5kIGxvZyBpbnRvIHRoZSBndWkuIE1h
a2Ugc3VyZSBvcmNhIGlzIHJ1bm5pbmcuIFRoZW4gZ28gYmFjayBvbmNlIGFnYWluIAp0byB0aGUg
Y29uc29sZSBieSBwcmVzc2luZyBjb250cm9sK2FsdCtmMS4gQXQgdGhpcyBwb2ludCwgSSB3aWxs
IGJldCAKdGhhdCBzb2Z0d2FyZSBzcGVlY2ggaXMgbm90IHdvcmtpbmcgZm9yIHlvdS4KCkkgdGhp
bmsgeW91IGNhbiBmaXggdGhpcyBieSByZWNvbXBpbGluZyBlc3BlYWt1cCB0byBkZWZhdWx0IHRv
IHVzaW5nIApwdWxzZWF1ZGlvLiBJbnN0cnVjdGlvbnMgZm9yIHRoYXQgYXJlIHNvbWV3aGVyZSBv
biBnb29nbGUuIElmIHlvdSBjYW4ndCAKZmluZCB0aGVtLCBJIGNhbiBwcm9iYWJseSBkaWcgdGhl
bSBvdXQgYWdhaW4uCgoKCk9uIDA2LzI0LzIwMTUgMDI6MzQgQU0sIEJyYW5kb24gS2VpdGggQmln
Z3Mgd3JvdGU6Cj4gSGVsbG8sCj4gSSBqdXN0IGluc3RhbGxlZCBkZWJpYW4gYW5kIGNhbid0IGZp
Z3VyZSBvdXQgaG93IHRvIGdldCBzcGVha3VwIHRvIHdvcmsuCj4gSSB0eXBlIGN0cmwrbWV0YStm
MSB0byBvcGVuIHRoZSB0ZXJtaW5hbCwgdGhlbiBJIHR5cGUgZXNwZWFrdXAuIEkgZ2V0Cj4gdGhl
IG1lc3NhZ2UgdGhhdCBlc3BlYWt1cCBpcyBhbHJlYWR5IHJ1bm5pbmcuIEJ1dCBJIGNhbid0IGdl
dCBhbnkgb3V0cHV0Cj4gZnJvbSB0eXBpbmcgb3IgbW92aW5nIGFyb3VuZC4gSSBrbm93IHNwZWFr
dXAgaXMgcnVubmluZyBiZWNhdXNlIEkgaGF2ZQo+IGl0IGluIGEgVk0gYW5kIHNvbWV0aW1lcyBz
cGVha3VwIGFuZCBPcmNhIGxpa2UgdG8gc2F5IHJhbmRvbSB3b3JkcyBhbmQKPiBzcGVha3VwIGp1
c3Qgc2FpZCBzb21ldGhpbmcgdG8gbWUsIGJ1dCBJIGNhbid0IGhlYXIgYW55dGhpbmcuIEkgYWxz
bwo+IGRvbid0IGdldCBzcGVlY2ggb24gYW55IGxvZy1pbiBzY3JlZW4uCj4gVGhhbmtzLAo+Cgot
LSAKSm9obiBIZWltLCBqaGVpbUBtYXRoLndpc2MuZWR1LCBza3lwZTpqb2huLmcuaGVpbQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTcGVha3VwIG1haWxp
bmcgbGlzdApTcGVha3VwQGxpbnV4LXNwZWFrdXAub3JnCmh0dHA6Ly9saW51eC1zcGVha3VwLm9y
Zy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vc3BlYWt1cAo=

[Jude DaShiell]

We use the s at the boot prompt to activate software speech for that
installation of speakup. The problem is no other options with that s
will be accepted and that's a debian decision which is something I
complained about earlier. I'm pretty sure debian has an initialization
file installers can modify to put extra boot parameters into so the
installer starts up with those extra boot parameters automatically. It
means burning yourslef your own custom debian iso to do it once the file
is modified though.

Date: Wed, 24 Jun 2015 10:49:27
Reply-To: Speakup is a screen review system for Linux.
Subject: Re: Getting speakup to run on debian
Hi. The Debian live cd for Jessie can run both espeak and orca at the
same time, so I suspect they've recompiled espeak to work with pulse
audio. However, when I tried an apt-get dist-upgrade, the problem
persists. I'm having problems getting the debian-installer-launcher to
run from the cd. It keeps trying to activate the framebuffer, and
hanging. An interesting catch 22.
Gene

SXQgaXMgcHJvYmFibHkgYSBjb25mbGljdCB3aXRoIHB1bHNlYXVkaW8gYW5kIGFsc2EuIFJpZ2h0
IG5vdyBJIGFtIGEgCmxpdHRsZSBmdXp6eSBvbiB0aGUgZGV0YWlscyBidXQgSSBiZWxpZXZlIHRo
YXQgb3JjYSBhbmQgZ25vbWUgbG9hZCBwdWxzZSAKZHJpdmVycyBhbmQgZXNwZWFrIG5lZWRzIGFs
c2EuIFlvdSBjYW4gdGVzdCB3aGV0aGVyIHRoaXMgaXMgdGhlIHByb2JsZW0gCmJ5IG5vdCBsb2dn
aW5nIGludG8gdGhlIEdVSSBiZWZvcmUgcnVubmluZyBlc3BlYWsuIFNvIGF0IHRoZSBnbm9tZSBs
b2dpbiAKc2NyZWVuLCBwcmVzcyBjb250cm9sK2FsdCtmMSB0byBnZXQgdG8gdGhlIGNvbnNvbGUs
IGxvZyBpbiBhbmQgc3RhcnQgCmVzcGVha3VwLiBUaGVuIGdvIGJhY2sgdG8gdGhlIGxvZ2luIHNj
cmVlbiBieSBwcmVzc2luZyBjb250cm9sK2FsdCtmNyAKYW5kIGxvZyBpbnRvIHRoZSBndWkuIE1h
a2Ugc3VyZSBvcmNhIGlzIHJ1bm5pbmcuIFRoZW4gZ28gYmFjayBvbmNlIGFnYWluIAp0byB0aGUg
Y29uc29sZSBieSBwcmVzc2luZyBjb250cm9sK2FsdCtmMS4gQXQgdGhpcyBwb2ludCwgSSB3aWxs
IGJldCAKdGhhdCBzb2Z0d2FyZSBzcGVlY2ggaXMgbm90IHdvcmtpbmcgZm9yIHlvdS4KCkkgdGhp
bmsgeW91IGNhbiBmaXggdGhpcyBieSByZWNvbXBpbGluZyBlc3BlYWt1cCB0byBkZWZhdWx0IHRv
IHVzaW5nIApwdWxzZWF1ZGlvLiBJbnN0cnVjdGlvbnMgZm9yIHRoYXQgYXJlIHNvbWV3aGVyZSBv
biBnb29nbGUuIElmIHlvdSBjYW4ndCAKZmluZCB0aGVtLCBJIGNhbiBwcm9iYWJseSBkaWcgdGhl
bSBvdXQgYWdhaW4uCgoKCk9uIDA2LzI0LzIwMTUgMDI6MzQgQU0sIEJyYW5kb24gS2VpdGggQmln
Z3Mgd3JvdGU6Cj4gSGVsbG8sCj4gSSBqdXN0IGluc3RhbGxlZCBkZWJpYW4gYW5kIGNhbid0IGZp
Z3VyZSBvdXQgaG93IHRvIGdldCBzcGVha3VwIHRvIHdvcmsuCj4gSSB0eXBlIGN0cmwrbWV0YStm
MSB0byBvcGVuIHRoZSB0ZXJtaW5hbCwgdGhlbiBJIHR5cGUgZXNwZWFrdXAuIEkgZ2V0Cj4gdGhl
IG1lc3NhZ2UgdGhhdCBlc3BlYWt1cCBpcyBhbHJlYWR5IHJ1bm5pbmcuIEJ1dCBJIGNhbid0IGdl
dCBhbnkgb3V0cHV0Cj4gZnJvbSB0eXBpbmcgb3IgbW92aW5nIGFyb3VuZC4gSSBrbm93IHNwZWFr
dXAgaXMgcnVubmluZyBiZWNhdXNlIEkgaGF2ZQo+IGl0IGluIGEgVk0gYW5kIHNvbWV0aW1lcyBz
cGVha3VwIGFuZCBPcmNhIGxpa2UgdG8gc2F5IHJhbmRvbSB3b3JkcyBhbmQKPiBzcGVha3VwIGp1
c3Qgc2FpZCBzb21ldGhpbmcgdG8gbWUsIGJ1dCBJIGNhbid0IGhlYXIgYW55dGhpbmcuIEkgYWxz
bwo+IGRvbid0IGdldCBzcGVlY2ggb24gYW55IGxvZy1pbiBzY3JlZW4uCj4gVGhhbmtzLAo+Cgot
LSAKSm9obiBIZWltLCBqaGVpbUBtYXRoLndpc2MuZWR1LCBza3lwZTpqb2huLmcuaGVpbQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwpTcGVha3VwIG1haWxp
bmcgbGlzdApTcGVha3VwQGxpbnV4LXNwZWFrdXAub3JnCmh0dHA6Ly9saW51eC1zcGVha3VwLm9y
Zy9jZ2ktYmluL21haWxtYW4vbGlzdGluZm8vc3BlYWt1cAo=

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--

[Gregory Nowak]

No, this is incorrect. Press s, press tab, press space, and type in
whatever boot options you want followed by enter.

Greg

Post by Jude DaShiell
We use the s at the boot prompt to activate software speech for that
installation of speakup. The problem is no other options with that
s will be accepted and that's a debian decision which is something I
complained about earlier. I'm pretty sure debian has an
initialization file installers can modify to put extra boot
parameters into so the installer starts up with those extra boot
parameters automatically. It means burning yourslef your own custom
debian iso to do it once the file is modified though.

[Jude DaShiell]

Thanks much, I'll make a note of it and use it the next time I install

Date: Wed, 24 Jun 2015 20:05:41
Reply-To: Speakup is a screen review system for Linux.
Subject: Re: Getting speakup to run on debian
No, this is incorrect. Press s, press tab, press space, and type in
whatever boot options you want followed by enter.
Greg

Post by Jude DaShiell
We use the s at the boot prompt to activate software speech for that
installation of speakup. The problem is no other options with that
s will be accepted and that's a debian decision which is something I
complained about earlier. I'm pretty sure debian has an
initialization file installers can modify to put extra boot
parameters into so the installer starts up with those extra boot
parameters automatically. It means burning yourslef your own custom
debian iso to do it once the file is modified though.

--
web site: http://www.gregn.net
gpg public key: http://www.gregn.net/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
If we haven't been in touch before, e-mail me before adding me to your contacts.
--
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--

[Gregory Nowak]

Try passing:
vga=normal fb=false
at the boot prompt.

Greg

Post by a***@icsmail.net
Hi. The Debian live cd for Jessie can run both espeak and orca at the
same time, so I suspect they've recompiled espeak to work with pulse
audio. However, when I tried an apt-get dist-upgrade, the problem
persists. I'm having problems getting the debian-installer-launcher to
run from the cd. It keeps trying to activate the framebuffer, and
hanging. An interesting catch 22.
Gene

[Steve Matzura]

I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.

Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.

Thanks in advance for any and all assistance and advice.

[Samuel Thibault]

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup,

Ah, you didn't say that in your previous report.

Post by Steve Matzura
And why would I even need to be doing this since obviously Speakup is
included in the install, you'd think,

And that's supposed to happen, yes. Which image did you use exactly?
There's something to fix here, espeakup is definitely supposed to have
been installed.

Samuel

[c***@ccs.covici.com]

You need a speech synthesizer, and that is not part of speakup. You
either need espeakup, or speechd-up and speech dispatcher, which has
worked great for me, although I mostly use hardware speech.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Steve Matzura]

Right. I tried installing the espeakup package and apt-get couldn't
find it. I suspect I have a source problem in /etc/apt/sources.list. I
suspect I should have been able to get it from the DVD distro, but
darned if I know how to do that! I also made what apparently turned
out to be an invalid assumption that, if the install talked, the
system should, or could be made to easily.

Post by c***@ccs.covici.com
You need a speech synthesizer, and that is not part of speakup. You
either need espeakup, or speechd-up and speech dispatcher, which has
worked great for me, although I mostly use hardware speech.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

I also made what apparently turned out to be an invalid assumption
that, if the install talked, the system should, or could be made to
easily.

Again, this assumption is completely right.

Except that bugs happen. And need to be reported. And then they can be
fixed. But only if they are reported.

Samuel

[Steve Matzura]

OK then, what's the right way to do that, and while I await the bug to
be properly documented and fixed, how do I work around it?

Post by Samuel Thibault

I also made what apparently turned out to be an invalid assumption
that, if the install talked, the system should, or could be made to
easily.

Again, this assumption is completely right.
Except that bugs happen. And need to be reported. And then they can be
fixed. But only if they are reported.
Samuel
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by Steve Matzura
OK then, what's the right way to do that,

Googling "bug debian" brings https://www.debian.org/Bugs/ which explains
everything.

Post by Steve Matzura
and while I await the bug to be properly documented and fixed, how do
I work around it?

Depends on the bug. Thus discussion is needed. Probably the better place
in this case is the debian-***@lists.debian.org mailing list.

Samuel

[Steve Matzura]

I found that, too, but thought it prudent to confirm. See previous
messages. If an update is forthcoming, I'll just learn how for the
future.

Post by Samuel Thibault

Post by Steve Matzura
OK then, what's the right way to do that,

Googling "bug debian" brings https://www.debian.org/Bugs/ which explains
everything.

Post by Steve Matzura
and while I await the bug to be properly documented and fixed, how do
I work around it?

Depends on the bug. Thus discussion is needed. Probably the better place
Samuel
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by Steve Matzura
I found that, too, but thought it prudent to confirm. See previous
messages. If an update is forthcoming, I'll just learn how for the
future.

Again, normally there is *nothing* to do. Just reboot after installation
finished, and it should be speaking up. Any divergence from this
scenario is a bug.

Samuel

[Hart Larry]

Well Steve, at least in Debian, you type, or actually first install
reportbug
I am at 6.6.5
Hope that helps
Hart

[Doug Smith]

Ok, I have never heard of this one before. I am running kali 2.0 which is based on jessie and the install talked as soon as it was done. I just had
to install the espeakup package to get speech on the cli and I am happy with what I see here.

I guess that the installer used by kali is the same one used in the stock debian install with a few modifications, bue I am not sure.

I have installed both debian and kali several times before in different versions back to the one before wheezy and I have never heard of this problem.
Do you think it would help if you reinstall or check the validity of your iso and make sure that it didn't get corrupted in downloading it.



Hope this helps.



Doug Smith

[Jude DaShiell]

Please type modprobe speakup_soft and then type espeakup and let us know
what happens after that gets done.

Date: Thu, 31 Dec 2015 08:09:19
Reply-To: Speakup is a screen review system for Linux.
Subject: Re: Getting speakup to run on debian
Right. I tried installing the espeakup package and apt-get couldn't
find it. I suspect I have a source problem in /etc/apt/sources.list. I
suspect I should have been able to get it from the DVD distro, but
darned if I know how to do that! I also made what apparently turned
out to be an invalid assumption that, if the install talked, the
system should, or could be made to easily.

Post by c***@ccs.covici.com
You need a speech synthesizer, and that is not part of speakup. You
either need espeakup, or speechd-up and speech dispatcher, which has
worked great for me, although I mostly use hardware speech.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--

[Steve Matzura]

Actually, I didn't need to do any of that. The problem was that
somehow my onboard sound card had gotten all its levels pushed down to
0. Using amixer (thanks to Samuel's recommendation) fixed it. I now
get full-on speech right from boot, which I haven't had 'round here
since I installed my first Fedora back in about 2003.

Post by Jude DaShiell
Please type modprobe speakup_soft and then type espeakup and let us know
what happens after that gets done.

Date: Thu, 31 Dec 2015 08:09:19
Reply-To: Speakup is a screen review system for Linux.
Subject: Re: Getting speakup to run on debian
Right. I tried installing the espeakup package and apt-get couldn't
find it. I suspect I have a source problem in /etc/apt/sources.list. I
suspect I should have been able to get it from the DVD distro, but
darned if I know how to do that! I also made what apparently turned
out to be an invalid assumption that, if the install talked, the
system should, or could be made to easily.

Post by c***@ccs.covici.com
You need a speech synthesizer, and that is not part of speakup. You
either need espeakup, or speechd-up and speech dispatcher, which has
worked great for me, although I mostly use hardware speech.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[mike]

Hi,

Speakup in Jessie installs seams to be a bit broken. I ownly ben able to get it working buy installing wheezy and upgrading to Jessie.

-----Original Message-----
From: Speakup [mailto:speakup-***@linux-speakup.org] On Behalf Of Steve Matzura
Sent: Thursday, December 31, 2015 7:09 AM
To: Speakup is a screen review system for Linux. <***@linux-speakup.org>
Subject: Re: Getting speakup to run on debian

I just installed a fresh Jessie yesterday. The install was assisted by Speakup, which I started at the install screen main menu by pressing s<ENTER>. I was quite impressed with the way it all worked, with one silly exception: There was a screen with 78 choices, one per line, and I couldn't figure out how to scroll the screen backward to read the first and second screens of choices, so I just went with the default choice, which turned out to be the correct one for me for the question being asked. Very impressive. No Orca, no forms, just straight CLI. I love CLI.

Now then, the system is up and running, there's no desktop, I boot directly to the login prompt, and now I want to get Speakup working on the console terminals. Someone named Samuel from Debian accessibility told me I should install the espeakup package, but apt-get can't find it. What'd I do wrong? And why would I even need to be doing this since obviously Speakup is included in the install, you'd think, or at least I did, that it would already exist on the system and be able to be run.

Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
***@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by mike
Speakup in Jessie installs seams to be a bit broken.

Please report bugs.
Please report bugs.
Please report bugs.
Please report bugs.
Please report bugs.

If you don't report bugs, developers don't even know they exist, and
thus for sure they can't get fixed...

Samuel

[Steve Matzura]

Oh that's bizarre. And the Debian accessibility department says it
should be good. Since my installation is just for testing, should I
start again with 7 and try upgrading to 8? And if so, what's the
recommended procedure for doing that without breaking espeakup or
Speakup itself?

Post by mike
Hi,
Speakup in Jessie installs seams to be a bit broken. I ownly ben able to get it working buy installing wheezy and upgrading to Jessie.
-----Original Message-----
Sent: Thursday, December 31, 2015 7:09 AM
Subject: Re: Getting speakup to run on debian
I just installed a fresh Jessie yesterday. The install was assisted by Speakup, which I started at the install screen main menu by pressing s<ENTER>. I was quite impressed with the way it all worked, with one silly exception: There was a screen with 78 choices, one per line, and I couldn't figure out how to scroll the screen backward to read the first and second screens of choices, so I just went with the default choice, which turned out to be the correct one for me for the question being asked. Very impressive. No Orca, no forms, just straight CLI. I love CLI.
Now then, the system is up and running, there's no desktop, I boot directly to the login prompt, and now I want to get Speakup working on the console terminals. Someone named Samuel from Debian accessibility told me I should install the espeakup package, but apt-get can't find it. What'd I do wrong? And why would I even need to be doing this since obviously Speakup is included in the install, you'd think, or at least I did, that it would already exist on the system and be able to be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by Steve Matzura
Oh that's bizarre. And the Debian accessibility department says it
should be good.

"should" means "that's what we implemented". It does not mean that there
aren't potential bugs. And there *are*. So please report them.

I'm sorry I keep writing the same, but it's really killing me that a
dozen months after the Jessie release nobody reported the issue. I have
already sent a patch to the debian-cd package, and it'll probably be a
matter of days before it's fixed. If only the issue had been reported
before, we'd have had a fixed Jessie way earlier.

Post by Steve Matzura
Since my installation is just for testing, should I
start again with 7 and try upgrading to 8?

No need to. As I told you privately, just add the network mirror in your
sources.list, and espeakup should become available.

Samuel

[Steve Matzura]

Samuel, I fully understand your feelings regarding bug-reporting. But
you know, we often think we're the ones doing something wrong and
hesitate to report anything unless and until we can verify that it's
really really a bug.

Another issue, of course, is, maybe nobody installed from scratch with
the expectation of using Speakup at the console immediately after
installation, which is why nobody thought there was anything wrong.

OK, if it's been reported and fixed, I'm not going to worry about
doing it, I just need to know what I need to do to work around it or
how/when to apply the proper update when it comes out. I can wait. ssh
is my friend until then.\

Post by Samuel Thibault

Post by Steve Matzura
Oh that's bizarre. And the Debian accessibility department says it
should be good.

"should" means "that's what we implemented". It does not mean that there
aren't potential bugs. And there *are*. So please report them.
I'm sorry I keep writing the same, but it's really killing me that a
dozen months after the Jessie release nobody reported the issue. I have
already sent a patch to the debian-cd package, and it'll probably be a
matter of days before it's fixed. If only the issue had been reported
before, we'd have had a fixed Jessie way earlier.

Post by Steve Matzura
Since my installation is just for testing, should I
start again with 7 and try upgrading to 8?

No need to. As I told you privately, just add the network mirror in your
sources.list, and espeakup should become available.
Samuel
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by Steve Matzura
Samuel, I fully understand your feelings regarding bug-reporting. But
you know, we often think we're the ones doing something wrong and
hesitate to report anything unless and until we can verify that it's
really really a bug.

Bug reports are what precisely allows the user to check with developers
whether it is a bug or not.

Samuel

[Samuel Thibault]

Post by Samuel Thibault

Post by Steve Matzura
Samuel, I fully understand your feelings regarding bug-reporting. But
you know, we often think we're the ones doing something wrong and
hesitate to report anything unless and until we can verify that it's
really really a bug.

Bug reports are what precisely allows the user to check with developers
whether it is a bug or not.

And even if it's not a bug, if the user didn't work how to do it by
himself, it means it's not documented properly, and thus still a bug to
fix.

Samuel

[Steve Matzura]

OK, you convinced me. LOL. Still doesn't work, so I'm off to do the
right thing.

Post by Samuel Thibault

Post by Samuel Thibault

Post by Steve Matzura
Samuel, I fully understand your feelings regarding bug-reporting. But
you know, we often think we're the ones doing something wrong and
hesitate to report anything unless and until we can verify that it's
really really a bug.

Bug reports are what precisely allows the user to check with developers
whether it is a bug or not.

And even if it's not a bug, if the user didn't work how to do it by
himself, it means it's not documented properly, and thus still a bug to
fix.
Samuel
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Steve Matzura]

OK, I had a couple things set up incorrectly in sources.list, but
there's a whole 'nuther story behind why, which I'll not bore you all
with, but suffice it to say my system is set up correctly but still
not talking, probably because I don't know the proper way to make
that happen.

Re bug reporting, I'm exhausting all possibilities first before
putting down what's not working to a bug because with me, it usually
isn't. I've found a few in my time, but am always hesitant to report
something as such in case I'm the one having done something wrong.
However, this one's apparently a valid Debian bug, so after I get it
solved, I will put it in.

Post by Steve Matzura
Oh that's bizarre. And the Debian accessibility department says it
should be good. Since my installation is just for testing, should I
start again with 7 and try upgrading to 8? And if so, what's the
recommended procedure for doing that without breaking espeakup or
Speakup itself?

Post by mike
Hi,
Speakup in Jessie installs seams to be a bit broken. I ownly ben able to get it working buy installing wheezy and upgrading to Jessie.
-----Original Message-----
Sent: Thursday, December 31, 2015 7:09 AM
Subject: Re: Getting speakup to run on debian
I just installed a fresh Jessie yesterday. The install was assisted by Speakup, which I started at the install screen main menu by pressing s<ENTER>. I was quite impressed with the way it all worked, with one silly exception: There was a screen with 78 choices, one per line, and I couldn't figure out how to scroll the screen backward to read the first and second screens of choices, so I just went with the default choice, which turned out to be the correct one for me for the question being asked. Very impressive. No Orca, no forms, just straight CLI. I love CLI.
Now then, the system is up and running, there's no desktop, I boot directly to the login prompt, and now I want to get Speakup working on the console terminals. Someone named Samuel from Debian accessibility told me I should install the espeakup package, but apt-get can't find it. What'd I do wrong? And why would I even need to be doing this since obviously Speakup is included in the install, you'd think, or at least I did, that it would already exist on the system and be able to be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Hello,

Post by Steve Matzura
There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices,

Yes, that's the issue with CLIs, I don't see good solutions beyond
switching to non-CLI to get better browsing facilities.

Apparently speakup does not know how to access to the backscroll of the
console. I'm surprised nobody apparently raised the issue, it should be
possible to fix it.

Samuel

[c***@ccs.covici.com]

That would be nice. I wonder if you can do this from kernel space,
though?

Post by Brandon Keith Biggs
Hello,

Post by Steve Matzura
There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices,

Yes, that's the issue with CLIs, I don't see good solutions beyond
switching to non-CLI to get better browsing facilities.
Apparently speakup does not know how to access to the backscroll of the
console. I'm surprised nobody apparently raised the issue, it should be
possible to fix it.
Samuel
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by c***@ccs.covici.com
That would be nice. I wonder if you can do this from kernel space,
though?

It's the kernel which does have the backlog. So for sure it should be
feasible to do it from the kernel space.

Samuel

[Steve Matzura]

Or, until that changes, display one screen at a time, with an option
to show previous/next screen or enter the requested prompt?

Post by Brandon Keith Biggs
Hello,

Post by Steve Matzura
There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices,

Yes, that's the issue with CLIs, I don't see good solutions beyond
switching to non-CLI to get better browsing facilities.
Apparently speakup does not know how to access to the backscroll of the
console. I'm surprised nobody apparently raised the issue, it should be
possible to fix it.
Samuel
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Samuel Thibault]

Post by Steve Matzura
Or, until that changes, display one screen at a time, with an option
to show previous/next screen or enter the requested prompt?

At first I was thinking it wouldn't be so simple, but it seems so
actually.

I have prepared a patched version:

https://people.debian.org/~sthibault/tmp/mini-cdebconf-text-choices.iso

'(' and ')' can be used to display next and previous choices. Probably
better shortcuts could be found ('<' is already taken), any ideas?

Samuel

[Gregory Nowak]

Post by Samuel Thibault
'(' and ')' can be used to display next and previous choices. Probably
better shortcuts could be found ('<' is already taken), any ideas?

Might I suggest '-' and '+' for prev/next respectively? That seems
more intuitive to me.

Greg

[Samuel Thibault]

Post by Gregory Nowak

Post by Samuel Thibault
'(' and ')' can be used to display next and previous choices. Probably
better shortcuts could be found ('<' is already taken), any ideas?

Might I suggest '-' and '+' for prev/next respectively? That seems
more intuitive to me.

Indeed, good idea.

Samuel

[Keith Barrett]

Just a thought,

Do you have sound working?

running "speaker-test" should give you white noise if sound is working.

You may have some of the sound controls muted.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Steve Matzura]

Yes, I absolutely did have *EVERYTHING* muted and didn't know it until
I learned (a little) how to use amixer. I'm still a little confused
about one thing: amixer thinks the main sound card's output is a
headphone jack, so when I set the volume for 'Front' to 100%, I got no
results, but when I set pvolume to 100% for Headphone, on it came. Now
that I think about it a little, I've seen something similar to this in
Windows. These Realtek sound chips have an annoying property where
they show two devices with the same name, something like "Realtek
High-Definition Speakers". One is the jack on the back of the machine,
one is the internal speaker of that machine. However, when you set the
default device to one of those two high-definition devices and plug a
headphone into the headphone jack, with the internal speaker setting,
it doesn't switch over, but with the other one, it does, and the
default device now changes to "Realtek High-Definition Headphones". so
I think what's going on in the Linux interpretation of all of this is
that Linux calls the main output jack "Headphone" because it can be
switched to a front-panel connection simply by plugging something into
it. I have tried the other jacks on the back panel, of which there are
four others (not including the SPDIF/optical connector, which looks
and feels nothing like an eighth-inch audio jack), and gotten no
response, so I'm 99% sure I'm plugged in to the right thing and have
the right control volume set in amixer.

Post by Keith Barrett
Just a thought,
Do you have sound working?
running "speaker-test" should give you white noise if sound is working.
You may have some of the sound controls muted.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Keith Barrett]

Glad you got it going.

Probably would be better if nothing was muted by default so that it
should come up with sound enabelled.

I got caught with the same issue a few years ago but probably best to
report it as a bug.

Post by Steve Matzura
Yes, I absolutely did have *EVERYTHING* muted and didn't know it until
I learned (a little) how to use amixer. I'm still a little confused
about one thing: amixer thinks the main sound card's output is a
headphone jack, so when I set the volume for 'Front' to 100%, I got no
results, but when I set pvolume to 100% for Headphone, on it came. Now
that I think about it a little, I've seen something similar to this in
Windows. These Realtek sound chips have an annoying property where
they show two devices with the same name, something like "Realtek
High-Definition Speakers". One is the jack on the back of the machine,
one is the internal speaker of that machine. However, when you set the
default device to one of those two high-definition devices and plug a
headphone into the headphone jack, with the internal speaker setting,
it doesn't switch over, but with the other one, it does, and the
default device now changes to "Realtek High-Definition Headphones". so
I think what's going on in the Linux interpretation of all of this is
that Linux calls the main output jack "Headphone" because it can be
switched to a front-panel connection simply by plugging something into
it. I have tried the other jacks on the back panel, of which there are
four others (not including the SPDIF/optical connector, which looks
and feels nothing like an eighth-inch audio jack), and gotten no
response, so I'm 99% sure I'm plugged in to the right thing and have
the right control volume set in amixer.

Post by Keith Barrett
Just a thought,
Do you have sound working?
running "speaker-test" should give you white noise if sound is working.
You may have some of the sound controls muted.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

[Steve Matzura]

Yes, and I just got beat up (LOLP in two places for not reporting
something as a bug, but I'm very conservative on bug reporting until I
am absolutely positively sure I'm not the one with the bug. Debuggers'
time is more valuable than mine will ever be, so I am wont to waste
their time on what's really a user problem, and the computer gods know
I've certainly been at the root of more than a few of those.

Post by Keith Barrett
Glad you got it going.
Probably would be better if nothing was muted by default so that it
should come up with sound enabelled.
I got caught with the same issue a few years ago but probably best to
report it as a bug.

Post by Steve Matzura
Yes, I absolutely did have *EVERYTHING* muted and didn't know it until
I learned (a little) how to use amixer. I'm still a little confused
about one thing: amixer thinks the main sound card's output is a
headphone jack, so when I set the volume for 'Front' to 100%, I got no
results, but when I set pvolume to 100% for Headphone, on it came. Now
that I think about it a little, I've seen something similar to this in
Windows. These Realtek sound chips have an annoying property where
they show two devices with the same name, something like "Realtek
High-Definition Speakers". One is the jack on the back of the machine,
one is the internal speaker of that machine. However, when you set the
default device to one of those two high-definition devices and plug a
headphone into the headphone jack, with the internal speaker setting,
it doesn't switch over, but with the other one, it does, and the
default device now changes to "Realtek High-Definition Headphones". so
I think what's going on in the Linux interpretation of all of this is
that Linux calls the main output jack "Headphone" because it can be
switched to a front-panel connection simply by plugging something into
it. I have tried the other jacks on the back panel, of which there are
four others (not including the SPDIF/optical connector, which looks
and feels nothing like an eighth-inch audio jack), and gotten no
response, so I'm 99% sure I'm plugged in to the right thing and have
the right control volume set in amixer.

Post by Keith Barrett
Just a thought,
Do you have sound working?
running "speaker-test" should give you white noise if sound is working.
You may have some of the sound controls muted.

Post by Steve Matzura
I just installed a fresh Jessie yesterday. The install was assisted by
Speakup, which I started at the install screen main menu by pressing
s<ENTER>. I was quite impressed with the way it all worked, with one
silly exception: There was a screen with 78 choices, one per line, and
I couldn't figure out how to scroll the screen backward to read the
first and second screens of choices, so I just went with the default
choice, which turned out to be the correct one for me for the question
being asked. Very impressive. No Orca, no forms, just straight CLI. I
love CLI.
Now then, the system is up and running, there's no desktop, I boot
directly to the login prompt, and now I want to get Speakup working on
the console terminals. Someone named Samuel from Debian accessibility
told me I should install the espeakup package, but apt-get can't find
it. What'd I do wrong? And why would I even need to be doing this
since obviously Speakup is included in the install, you'd think, or at
least I did, that it would already exist on the system and be able to
be run.
Thanks in advance for any and all assistance and advice.
_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

_______________________________________________
Speakup mailing list
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup