Archlinux Speakup problems after alsa package upgrade

Archlinux Speakup problems after alsa package upgrade

[Kelly Prescott]

I just upgraded my archlinux system and alsalibs, alsa-utils, and other 
alsa packages were upgraded.
The end result is that speakup would no longer speak properly.
I could tell that it was trying to speak but for example on a line that 
said systemd: I just heard the s
Also when trying to read full lines of text, you just hear the hint of the 
first character then nothing.
I am using software speech.
I have 6 different systems here that all use archlinux and I get the same 
behavior on all of them.
I downgraded the alsa-libs, alsa-utils, alsa-plugins, pulseaudio-alsa 
alsa-card-profiles, alsa-topology-conf, and alsa-ucm-conf packages, and 
now all my systems work.
I have not had time to dig into this further, I am just letting people 
know so if you have archlinux, you might want to hold off on updating 
until this gets fixed.
If you upgrade your archlinux system, and your alsa updates, it will make 
your system unusable with speech.

-- Kelly Prescott

Re: Archlinux Speakup problems after alsa package upgrade

[Kelly Prescott]

The working versions of alsa stuff is:
alsa-card-profiles 1:0.3.28-1
alsa-lib 1.2.4-3
alsa-plugins 1:1.2.2-2
alsa-topology-conf 1.2.4-2
alsa-ucm-conf 1.2.4-2
alsa-utils 1.2.4-2
pulseaudio-alsa 1:1.2.2-2



On Wed, 9 Jun 2021, Samuel Thibault wrote:

> Hello,
>
> Kelly Prescott wrote:
>> I downgraded the alsa-libs [...] and now all my systems work.
>
> Which version did you need to downgrade from and to?
>
> Samuel
>

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Hi, Kelly:

Thanks for the heads up.

Unfortunately, I'm unable to verify.

I usually update all my machines early Saturdays, and I did so this
week. This week, for a reason unrelated to sound and Speakup, I also ran
an update on one of my machines on Sunday 6 June.

The machine updated Saturday has the alsa versions you list. However,
the machine I upgraded on Sunday 6 June is running 1.2.5-2 and doing so
without difficulty.


I should note I don't have pulseaudio. I am running pipewire, including
pipewire-alsa Version         : 1:0.3.29-1


Best,

Janina

Kelly Prescott writes:
> The working versions of alsa stuff is:
> alsa-card-profiles 1:0.3.28-1
> alsa-lib 1.2.4-3
> alsa-plugins 1:1.2.2-2
> alsa-topology-conf 1.2.4-2
> alsa-ucm-conf 1.2.4-2
> alsa-utils 1.2.4-2
> pulseaudio-alsa 1:1.2.2-2
> 
> 
> 
> On Wed, 9 Jun 2021, Samuel Thibault wrote:
> 
> > Hello,
> > 
> > Kelly Prescott wrote:
> > > I downgraded the alsa-libs [...] and now all my systems work.
> > 
> > Which version did you need to downgrade from and to?
> > 
> > Samuel
> > 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Chris Brannon]

Kelly Prescott <kprescott@coolip.net> writes:

> I just upgraded my archlinux system and alsalibs, alsa-utils, and
> other alsa packages were upgraded.
> The end result is that speakup would no longer speak properly.

Kelly,
Are you using espeak-ng or the original espeak?

-- Chris

Re: Archlinux Speakup problems after alsa package upgrade

[Kelly Prescott]

They were
alsa-lib-1.2.5-2
alsa-topology-conf-1.2.5-1
alsa-ucm-conf-1.2.5-1
alsa-utils-1.2.5-3
alsa-card-profiles-1:0.3.30-1
alsa-plugins-1:1.2.5-2
pulseaudio-alsa-1:1.2.5-2


On Wed, 9 Jun 2021, Samuel Thibault wrote:

> Kelly Prescott wrote:
>> The working versions of alsa stuff
>
> And which were the non-working versions?
>
> Samuel
>

Re: Archlinux Speakup problems after alsa package upgrade

[Kelly Prescott]

Chris, I did some experimenting and here is what I found.
espeak is installed and it is what I am using.
espeak-ng is also installed.
Commands and results:

espeak "Hello Linux Speakup"
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM 
cards.pcm.center_lfe
ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel 
map
connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file 
or directory)
attempt to connect to server failed
connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file 
or directory)
attempt to connect to server failed
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: 
Connection refused

ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: 
Connection refused

ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 
'card'
ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 
'card'
connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file 
or directory)
attempt to connect to server failed
Expression 'framesAvail' failed in 'src/hostapi/alsa/pa_linux_alsa.c', 
line: 3629
Expression 'PaAlsaStreamComponent_GetAvailableFrames( self, &framesAvail, 
xrun )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3989
Expression 'PaAlsaStreamComponent_RegisterChannels( &self->playback, 
&self->bufferProcessor, &playbackFrames, &xrun )' failed in 
'src/hostapi/alsa/pa_linux_alsa.c', line: 4118
Expression 'PaAlsaStream_SetUpBuffers( stream, &framesGot, &xrun )' failed 
in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4359

espeak-ng "Hello Linux Speakup"
Hello Linux Speakup was spoken.


On Wed, 9 Jun 2021, Chris Brannon wrote:

> Kelly Prescott <kprescott@coolip.net> writes:
>
>> I just upgraded my archlinux system and alsalibs, alsa-utils, and
>> other alsa packages were upgraded.
>> The end result is that speakup would no longer speak properly.
>
> Kelly,
> Are you using espeak-ng or the original espeak?
>
> -- Chris
>

Re: Archlinux Speakup problems after alsa package upgrade

[Jude DaShiell]

dsp doesn't work so far as I know unless alsa-oss is installed and a
/dev/dsp device actually exists.


On Wed, 9 Jun 2021, Kelly Prescott wrote:

> Chris, I did some experimenting and here is what I found.
> espeak is installed and it is what I am using.
> espeak-ng is also installed.
> Commands and results:
>
> espeak "Hello Linux Speakup"
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
> ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
> connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or
> directory)
> attempt to connect to server failed
> connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or
> directory)
> attempt to connect to server failed
> ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
> ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
> ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection
> refused
>
> ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection
> refused
>
> ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
> ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
> ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
> ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
> connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or
> directory)
> attempt to connect to server failed
> Expression 'framesAvail' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line:
> 3629
> Expression 'PaAlsaStreamComponent_GetAvailableFrames( self, &framesAvail, xrun
> )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3989
> Expression 'PaAlsaStreamComponent_RegisterChannels( &self->playback,
> &self->bufferProcessor, &playbackFrames, &xrun )' failed in
> 'src/hostapi/alsa/pa_linux_alsa.c', line: 4118
> Expression 'PaAlsaStream_SetUpBuffers( stream, &framesGot, &xrun )' failed in
> 'src/hostapi/alsa/pa_linux_alsa.c', line: 4359
>
> espeak-ng "Hello Linux Speakup"
> Hello Linux Speakup was spoken.
>
>
> On Wed, 9 Jun 2021, Chris Brannon wrote:
>
> > Kelly Prescott <kprescott@coolip.net> writes:
> >
> >> I just upgraded my archlinux system and alsalibs, alsa-utils, and
> >> other alsa packages were upgraded.
> >> The end result is that speakup would no longer speak properly.
> >
> > Kelly,
> > Are you using espeak-ng or the original espeak?
> >
> > -- Chris
> >
>
>

Re: Archlinux Speakup problems after alsa package upgrade

[Jude DaShiell]

What are espeakup-ng's dependencies?  The archwiki only has italian
articles on this package and the only italian I do sometimes is pizza ande
pasta.


On Wed, 9 Jun 2021, Jude DaShiell wrote:

> dsp doesn't work so far as I know unless alsa-oss is installed and a
> /dev/dsp device actually exists.
>
>
> On Wed, 9 Jun 2021, Kelly Prescott wrote:
>
> > Chris, I did some experimenting and here is what I found.
> > espeak is installed and it is what I am using.
> > espeak-ng is also installed.
> > Commands and results:
> >
> > espeak "Hello Linux Speakup"
> > ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
> > ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
> > ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
> > ALSA lib pcm_route.c:877:(find_matching_chmap) Found no matching channel map
> > connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or
> > directory)
> > attempt to connect to server failed
> > connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or
> > directory)
> > attempt to connect to server failed
> > ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
> > ALSA lib pcm_oss.c:397:(_snd_pcm_oss_open) Cannot open device /dev/dsp
> > ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection
> > refused
> >
> > ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect: Connection
> > refused
> >
> > ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
> > ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
> > ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
> > ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card 'card'
> > connect(2) call to /dev/shm/jack-0/default/jack_0 failed (err=No such file or
> > directory)
> > attempt to connect to server failed
> > Expression 'framesAvail' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line:
> > 3629
> > Expression 'PaAlsaStreamComponent_GetAvailableFrames( self, &framesAvail, xrun
> > )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 3989
> > Expression 'PaAlsaStreamComponent_RegisterChannels( &self->playback,
> > &self->bufferProcessor, &playbackFrames, &xrun )' failed in
> > 'src/hostapi/alsa/pa_linux_alsa.c', line: 4118
> > Expression 'PaAlsaStream_SetUpBuffers( stream, &framesGot, &xrun )' failed in
> > 'src/hostapi/alsa/pa_linux_alsa.c', line: 4359
> >
> > espeak-ng "Hello Linux Speakup"
> > Hello Linux Speakup was spoken.
> >
> >
> > On Wed, 9 Jun 2021, Chris Brannon wrote:
> >
> > > Kelly Prescott <kprescott@coolip.net> writes:
> > >
> > >> I just upgraded my archlinux system and alsalibs, alsa-utils, and
> > >> other alsa packages were upgraded.
> > >> The end result is that speakup would no longer speak properly.
> > >
> > > Kelly,
> > > Are you using espeak-ng or the original espeak?
> > >
> > > -- Chris
> > >
> >
> >
>
>

Re: Archlinux Speakup problems after alsa package upgrade

[Chris Brannon]

Kelly Prescott <kprescott@coolip.net> writes:

> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
> ALSA lib pcm.c:2660:(snd_pcm_open_noupdate) Unknown PCM
> cards.pcm.center_lfe
*SNIP*

Some of these messages have been there for years, and I expect them.

> ALSA lib pulse.c:242:(pulse_connect) PulseAudio: Unable to connect:
> Connection refused

If you aren't using pulseaudio, and evidently you aren't, I'd remove
the pulseaudio-alsa package.

> ALSA lib confmisc.c:160:(snd_config_get_card) Invalid field card
> ALSA lib pcm_usb_stream.c:482:(_snd_pcm_usb_stream_open) Invalid card
> 'card'

That is unexpected and it might be the smoking gun.

I'd be interested to know how that batch of messages compares with
messages from the previous version.  Which are missing?

I'd try compiling one of the portaudio test programs.  My guess is that
it will run under the alsa 1.2.4 libraries, but not under the alsa 1.2.5
libraries.  If that is indeed the case, you should file a bug with Arch,
telling them their most recent ALSA update broke portaudio.

I myself would have a difficult time helping you to debug.
I'm not on Arch, and all of my systems are using pulseaudio and espeak-ng
rather than alsa and espeak nowadays.

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Hi, All:

Just returning to this topic to add my own experience on updating my
Arch Linux installation on two machines over the weekend.

I also ran into problems that rendered Speakup unusable with espeakup.
Reverting alsa-lib fixed the Speakup issue. As we don't know how long
the problem may persist, I've added the following to my
/etc/pacman.conf:

IgnorePkg   =alsa-lib


I also discovered problems with alsa-util packages. A command as
straight forward as:

amixer controls

returned meaningless results. Further, several of my audio devices were
silent with volumes set to 0, and the switch set to "false." So, I also
added a line like the above for alsa-utils.

Not sure how to be helpful to anyone interested in debugging, but I do
have two machines and am willing to try. Please advise.

Best,

Janina

Kelly Prescott writes:
> They were
> alsa-lib-1.2.5-2
> alsa-topology-conf-1.2.5-1
> alsa-ucm-conf-1.2.5-1
> alsa-utils-1.2.5-3
> alsa-card-profiles-1:0.3.30-1
> alsa-plugins-1:1.2.5-2
> pulseaudio-alsa-1:1.2.5-2
> 
> 
> On Wed, 9 Jun 2021, Samuel Thibault wrote:
> 
> > Kelly Prescott wrote:
> > > The working versions of alsa stuff
> > 
> > And which were the non-working versions?
> > 
> > Samuel
> > 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Alexander Epaneshnikov]

14.06.2021 16:26, Janina Sajka пишет:
> Hi, All:
>
> Just returning to this topic to add my own experience on updating my
> Arch Linux installation on two machines over the weekend.
>
> I also ran into problems that rendered Speakup unusable with espeakup.
> Reverting alsa-lib fixed the Speakup issue. As we don't know how long
> the problem may persist, I've added the following to my
> /etc/pacman.conf:
>
> IgnorePkg   =alsa-lib
>
>
> I also discovered problems with alsa-util packages. A command as
> straight forward as:
>
> amixer controls
>
> returned meaningless results. Further, several of my audio devices were
> silent with volumes set to 0, and the switch set to "false." So, I also
> added a line like the above for alsa-utils.
>
> Not sure how to be helpful to anyone interested in debugging, but I do
> have two machines and am willing to try. Please advise.
>
> Best,
>
> Janina
>
Hello everyone. please test espeakup 0.90 with laytest alsa-lib on Arch Linux.
I will be happy to hear the results.

-- 
Sincerely, Alexander.

captcha revisited, just a little.

[Karen Lewellen]

Janina
Can you share the link to your excellent  w3c research on captcha issues?
Patreon has now added cloudflare, after recently claiming, with ACB help, 
that they were working on wACG  compliance.
while I realize your article is not official w3c policy, it is both 
detailed, and informative, with my wanting to direct their accessibility 
team to the information.
Thanks,
Karen

Re: Archlinux Speakup problems after alsa package upgrade

[Alexander Epaneshnikov]

On Thu, Aug 19, 2021 at 10:56:17PM +0200, Samuel Thibault wrote:
> Hello,
>
> As an additional datapoint: in Debian the upgrade of alsa-lib to 1.2.5.1
> disturbs the espeakup output. Not completely broken, but distorted
> enough that you'll rather reboot to get back normal speech. I could
> capture some warnings, reported on
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992537
> Hopefully they will have ideas.

don't know if it's helpful info. but on arch linux espeakup 0.90 works fine
with: alsa-lib 1.2.5.1-3, pcaudiolib 1.2-2  and espeak-ng 1.50-4

maybe espeakup or espeak-ng should be rebuilt?

> Samuel

--
Sincerely, Alexander

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

I'll give it another try over the weekend and report.

I do see I'm missing espeak-ng-espeak, so maybe I'm missing a symlink or
two. Didn't see that one before.

Janina

Alexander Epaneshnikov writes:
> On Thu, Aug 19, 2021 at 10:56:17PM +0200, Samuel Thibault wrote:
> > Hello,
> >
> > As an additional datapoint: in Debian the upgrade of alsa-lib to 1.2.5.1
> > disturbs the espeakup output. Not completely broken, but distorted
> > enough that you'll rather reboot to get back normal speech. I could
> > capture some warnings, reported on
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992537
> > Hopefully they will have ideas.
> 
> don't know if it's helpful info. but on arch linux espeakup 0.90 works fine
> with: alsa-lib 1.2.5.1-3, pcaudiolib 1.2-2  and espeak-ng 1.50-4
> 
> maybe espeakup or espeak-ng should be rebuilt?
> 
> > Samuel
> 
> --
> Sincerely, Alexander

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Alex:

I regret to advise it's NOT working on my newest hardware running Arch
fully updated via Syu today, 21 August.

janina@minuet 07:58:59 ~$yay -Q alsa-lib pcaudiolib espeak-ng
espeak-ng-espeak espeakup
alsa-lib 1.2.5.1-3
pcaudiolib 1.2-2
espeak-ng 1.50-4
espeak-ng-espeak 1.50-4
espeakup 0.90-1

I have confirmed my audio devices can aplay without problems, but no joy
from espeakup.

I will leave the above as reported just in case you'd like more info or in
case you'd like me to try something specific. However, I will need to
return this system to a working state by Sunday evening.

Best,

Janina

Samuel Thibault writes:
> Alexander Epaneshnikov, le ven. 20 août 2021 18:26:06 +0300, a ecrit:
> > On Thu, Aug 19, 2021 at 10:56:17PM +0200, Samuel Thibault wrote:
> > > As an additional datapoint: in Debian the upgrade of alsa-lib to 1.2.5.1
> > > disturbs the espeakup output. Not completely broken, but distorted
> > > enough that you'll rather reboot to get back normal speech. I could
> > > capture some warnings, reported on
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992537
> > > Hopefully they will have ideas.
> > 
> > don't know if it's helpful info. but on arch linux espeakup 0.90 works fine
> > with: alsa-lib 1.2.5.1-3, pcaudiolib 1.2-2  and espeak-ng 1.50-4
> 
> On Debian it works fine, yes, but only after restarting espeakup.
> 
> Samuel

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Hi, Samuel:

espeakup -d gives me:

Unable to open the softsynth device: Permission denied

Best,

Janina

Samuel Thibault writes:
> Janina Sajka, le sam. 21 août 2021 08:11:42 -0400, a ecrit:
> > I have confirmed my audio devices can aplay without problems, but no joy
> > from espeakup.
> 
> Would you be able to run espeakup by hand with the -d flag? That'll dump
> the alsa errors and whatnot.
> 
> Samuel

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Didier Spaier]

Hi Janina,

You are not running this command as regular user, are you?

Best,

Didier

[fist sent privately my mistake, sorry]

Le 21/08/2021 à 14:49, Janina Sajka a écrit :
> Hi, Samuel:
> 
> espeakup -d gives me:
> 
> Unable to open the softsynth device: Permission denied
> 
> Best,
> 
> Janina
> 
> Samuel Thibault writes:
>> Janina Sajka, le sam. 21 août 2021 08:11:42 -0400, a ecrit:
>>> I have confirmed my audio devices can aplay without problems, but no joy
>>> from espeakup.
>>
>> Would you be able to run espeakup by hand with the -d flag? That'll dump
>> the alsa errors and whatnot.
>>
>> Samuel
> 

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Running as root outputs nothing, but the permissions on /dev/softsynth
are the same as with older versions of espeakup, alsa-lib, etc:

crw------- 1 root root 10, 122 Aug 21 08:29 /dev/softsynth


That's the same as on my other Linux box where the following works just
fine:

janina@concerto 09:11:08 ~$yay -Q alsa-lib pcaudiolib espeak-ng espeakup
alsa-lib 1.2.4-3
pcaudiolib 1.2-2
espeak-ng 1.50-4
espeakup 0.80-3


I believe I have the same permissions:

root@concerto 09:12:26 dev#ls -l /dev/softsynth
crw------- 1 root root 10, 122 Aug 21 08:29 /dev/softsynth

Samuel Thibault writes:
> Janina Sajka, le sam. 21 août 2021 08:49:12 -0400, a ecrit:
> > espeakup -d gives me:
> > 
> > Unable to open the softsynth device: Permission denied
> 
> It needs to be run as root, or change the permissions on /dev/softsynth
> to be able to run it as non-root.
> 
> Samuel

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Hmmm, now it's working. I never did reboot. I switched to the minuet
machine with my kvm and found espeakup working. I still see no error
neither on the root console, which has not returned after the by hand
start with -d, nor via the ssh from the concerto machine.

So, it seems it will work after some amount of time?


Didier Spaier writes:
> Hi Janina,
> 
> You are not running this command as regular user, are you?
> 
> Best,
> 
> Didier
> 
> [fist sent privately my mistake, sorry]
> 
> Le 21/08/2021 à 14:49, Janina Sajka a écrit :
> > Hi, Samuel:
> > 
> > espeakup -d gives me:
> > 
> > Unable to open the softsynth device: Permission denied
> > 
> > Best,
> > 
> > Janina
> > 
> > Samuel Thibault writes:
> > > Janina Sajka, le sam. 21 août 2021 08:11:42 -0400, a ecrit:
> > > > I have confirmed my audio devices can aplay without problems, but no joy
> > > > from espeakup.
> > > 
> > > Would you be able to run espeakup by hand with the -d flag? That'll dump
> > > the alsa errors and whatnot.
> > > 
> > > Samuel
> > 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Archlinux Speakup problems after alsa package upgrade

[Didier Spaier]

I don't know. Why it work only after some amount of time is beyond me.

Didier

Le 21/08/2021 à 15:34, Janina Sajka a écrit :
> Hmmm, now it's working. I never did reboot. I switched to the minuet
> machine with my kvm and found espeakup working. I still see no error
> neither on the root console, which has not returned after the by hand
> start with -d, nor via the ssh from the concerto machine.
> 
> So, it seems it will work after some amount of time?
> 
> 
> Didier Spaier writes:
>> Hi Janina,
>>
>> You are not running this command as regular user, are you?
>>
>> Best,
>>
>> Didier
>>
>> [fist sent privately my mistake, sorry]
>>
>> Le 21/08/2021 à 14:49, Janina Sajka a écrit :
>>> Hi, Samuel:
>>>
>>> espeakup -d gives me:
>>>
>>> Unable to open the softsynth device: Permission denied
>>>
>>> Best,
>>>
>>> Janina
>>>
>>> Samuel Thibault writes:
>>>> Janina Sajka, le sam. 21 août 2021 08:11:42 -0400, a ecrit:
>>>>> I have confirmed my audio devices can aplay without problems, but no joy
>>>>> from espeakup.
>>>>
>>>> Would you be able to run espeakup by hand with the -d flag? That'll dump
>>>> the alsa errors and whatnot.
>>>>
>>>> Samuel
>>>
> 

Re: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

My bad about the time delay. I may simply have confused myself over what
machine I was talking to. I have a 4 port KVM and I'm forever giving
NVDA commands to my Mac, VoiceOver commands to my Linux, Orca commands
to my Windws, etc ... Sorry.

If the espeakup service is stopped, the by hand start via -d does start
it, and it's fine across all consoles. But, there are also no errors in
the root console.

Any other suggestions much appreciated. And, I'll promise to be extra
careful what machine I'm talking to!

Janina

Didier Spaier writes:
> I don't know. Why it work only after some amount of time is beyond me.
> 
> Didier
> 
> Le 21/08/2021 à 15:34, Janina Sajka a écrit :
> > Hmmm, now it's working. I never did reboot. I switched to the minuet
> > machine with my kvm and found espeakup working. I still see no error
> > neither on the root console, which has not returned after the by hand
> > start with -d, nor via the ssh from the concerto machine.
> > 
> > So, it seems it will work after some amount of time?
> > 
> > 
> > Didier Spaier writes:
> > > Hi Janina,
> > > 
> > > You are not running this command as regular user, are you?
> > > 
> > > Best,
> > > 
> > > Didier
> > > 
> > > [fist sent privately my mistake, sorry]
> > > 
> > > Le 21/08/2021 à 14:49, Janina Sajka a écrit :
> > > > Hi, Samuel:
> > > > 
> > > > espeakup -d gives me:
> > > > 
> > > > Unable to open the softsynth device: Permission denied
> > > > 
> > > > Best,
> > > > 
> > > > Janina
> > > > 
> > > > Samuel Thibault writes:
> > > > > Janina Sajka, le sam. 21 août 2021 08:11:42 -0400, a ecrit:
> > > > > > I have confirmed my audio devices can aplay without problems, but no joy
> > > > > > from espeakup.
> > > > > 
> > > > > Would you be able to run espeakup by hand with the -d flag? That'll dump
> > > > > the alsa errors and whatnot.
> > > > > 
> > > > > Samuel
> > > > 
> > 

-- 

Janina Sajka
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Hi,

I have spent sometime today trying to get espeakup working on one of my
two Linux systems. I now have it working with alsa-lib-1.2.6.1-1 and
Espeakup-0.90 on Arch, using standard Arch packaging.

What was the fix?

I introduced a file:

/etc/asound.conf

<begin file contents>
ctl.!default {
        type hw
	        card 0
		}

		<end file contents>

		Why that should matter is beyond me. Seems like this
		should be the default behavior, no?

		Best,

		Janina

Janina Sajka writes:
> Hi, Alexander:
> 
> I ram an -Syu upgrade on one of my two machines and rebooted. I can
> confirm espeakup 0.9.0 and also:
> 
> alsa-lib 1.2.5.1-3
> alsa-utils 1.2.5.1-1
> 
> Unfortunately, I do not get Speakup speech. Doing "espeak hello" works,
> as do aplay commands.
> 
> I would also note the amixer command environment seems OK now, but
> that's a separate issue.
> 
> I will leave things as they are for now, rather than downversioning
> alsa-lib, in case I can give you some other
> debugging output. Let me know, and thanks for your efforts.
> 
> Janina
> 
> 
> Alexander Epaneshnikov writes:
> > 14.06.2021 16:26, Janina Sajka пишет:
> > > Hi, All:
> > > 
> > > Just returning to this topic to add my own experience on updating my
> > > Arch Linux installation on two machines over the weekend.
> > > 
> > > I also ran into problems that rendered Speakup unusable with espeakup.
> > > Reverting alsa-lib fixed the Speakup issue. As we don't know how long
> > > the problem may persist, I've added the following to my
> > > /etc/pacman.conf:
> > > 
> > > IgnorePkg   =alsa-lib
> > > 
> > > 
> > > I also discovered problems with alsa-util packages. A command as
> > > straight forward as:
> > > 
> > > amixer controls
> > > 
> > > returned meaningless results. Further, several of my audio devices were
> > > silent with volumes set to 0, and the switch set to "false." So, I also
> > > added a line like the above for alsa-utils.
> > > 
> > > Not sure how to be helpful to anyone interested in debugging, but I do
> > > have two machines and am willing to try. Please advise.
> > > 
> > > Best,
> > > 
> > > Janina
> > > 
> > Hello everyone. please test espeakup 0.90 with laytest alsa-lib on Arch Linux.
> > I will be happy to hear the results.
> > 
> > -- 
> > Sincerely, Alexander.
> 
> -- 
> 
> Janina Sajka
> https://linkedin.com/in/jsajka
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:	http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> 

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Jason White]

On 22/12/21 11:38, Janina Sajka wrote:
> What was the fix?
>
> I introduced a file:
>
> /etc/asound.conf

Interestingly, I don't have that file on my Arch Linux system, but there 
are various configuration files under /etc/alsa/conf.d, apparently 
placed there by Pipewire packages.

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Very relevant observation, Jason.
Indeed, that file I refer to seems to have been deleted by one upgrade
or another over the past week--I've run several.

So, not sure what's going on under the hood. All I can say is that
creating that file, for whatever reason, caused Espeakup to work on the
System76 Meerkat system.

On my older, 2012 era custom built Linux board, Espeakup-0.80 is still
required, but it now works with the latest alsa. No matter what I try,
Espeakup-0.90 won't work, even though the espeak command speaks using
espeak-ng. So, I downgraded to the latest Espeak, dated on Arch from mid
December, and downgraded Espeakup accordingly.

Apparently there must be some kind of reason why Espeakup can't be
agnostic between espeak and espeak-ng?

Best,

Janina

Jason White writes:
> 
> On 22/12/21 11:38, Janina Sajka wrote:
> > What was the fix?
> > 
> > I introduced a file:
> > 
> > /etc/asound.conf
> 
> Interestingly, I don't have that file on my Arch Linux system, but there are
> various configuration files under /etc/alsa/conf.d, apparently placed there
> by Pipewire packages.
> 
> 

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Oops, one important correction to my last post ...

I just ran another Syu upgrade on said machine, which gave me a new
kernel and, therefore, a reboot.

Espeakup was silent on reboot, so I again created the /etc/asound.conf
file and rebooted again. Bingo. Speech.

Best,

Janina

Janina Sajka writes:
> Very relevant observation, Jason.
> Indeed, that file I refer to seems to have been deleted by one upgrade
> or another over the past week--I've run several.
> 
> So, not sure what's going on under the hood. All I can say is that
> creating that file, for whatever reason, caused Espeakup to work on the
> System76 Meerkat system.
> 
> On my older, 2012 era custom built Linux board, Espeakup-0.80 is still
> required, but it now works with the latest alsa. No matter what I try,
> Espeakup-0.90 won't work, even though the espeak command speaks using
> espeak-ng. So, I downgraded to the latest Espeak, dated on Arch from mid
> December, and downgraded Espeakup accordingly.
> 
> Apparently there must be some kind of reason why Espeakup can't be
> agnostic between espeak and espeak-ng?
> 
> Best,
> 
> Janina
> 
> Jason White writes:
> > 
> > On 22/12/21 11:38, Janina Sajka wrote:
> > > What was the fix?
> > > 
> > > I introduced a file:
> > > 
> > > /etc/asound.conf
> > 
> > Interestingly, I don't have that file on my Arch Linux system, but there are
> > various configuration files under /etc/alsa/conf.d, apparently placed there
> > by Pipewire packages.
> > 
> > 
> 
> -- 
> 
> Janina Sajka
> (she/her/hers)
> https://linkedin.com/in/jsajka
> 
> Linux Foundation Fellow
> Executive Chair, Accessibility Workgroup:	http://a11y.org
> 
> The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa
> 

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Didier Spaier]

Hi Janina and all,

On 28/12/2021 17:26, Janina Sajka wrote:
> Very relevant observation, Jason.
> Indeed, that file I refer to seems to have been deleted by one upgrade
> or another over the past week--I've run several.
> 
> So, not sure what's going on under the hood. All I can say is that
> creating that file, for whatever reason, caused Espeakup to work on the
> System76 Meerkat system.
> 
> On my older, 2012 era custom built Linux board, Espeakup-0.80 is still
> required, but it now works with the latest alsa. No matter what I try,
> Espeakup-0.90 won't work, even though the espeak command speaks using
> espeak-ng. So, I downgraded to the latest Espeak, dated on Arch from mid
> December, and downgraded Espeakup accordingly.
> 
> Apparently there must be some kind of reason why Espeakup can't be
> agnostic between espeak and espeak-ng?

espeakup is linked against the shared library installed at time of building it.

Here:
dance[~]$ ldd /usr/bin/espeakup | grep libespeak
	libespeak-ng.so.1 => /usr/lib64/libespeak-ng.so.1 (0x00007f290df83000)

My guess is you will find libespeak.so.1 instead running the same command.

So you need to rebuild espeakup-0.90 after having removed espeak and installed
espeak-ng only.

It could be possible to just make a symlink instead, but that would ugly. Better
just get read of espeak.

Cheers,
Didier

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Didier Spaier writes:
> Hi Janina and all,
> 
> On 28/12/2021 17:26, Janina Sajka wrote:
> > ...
> > 
> > Apparently there must be some kind of reason why Espeakup can't be
> > agnostic between espeak and espeak-ng?
> 
> espeakup is linked against the shared library installed at time of building it.
> 
> Here:
> dance[~]$ ldd /usr/bin/espeakup | grep libespeak
> 	libespeak-ng.so.1 => /usr/lib64/libespeak-ng.so.1 (0x00007f290df83000)
> 
Thanks, Didier. This does make sense.

> My guess is you will find libespeak.so.1 instead running the same command.
> 
> So you need to rebuild espeakup-0.90 after having removed espeak and installed
> espeak-ng only.
> 
Are you saying I need to run ldd by hand? I thought the installation
process upgrading from 80 to 90 would take care of the ldd?

It's true I did not run an ldd when I tried to upgrade my older machine
to espeak-ng and espeakup-0.90.


Best,

Janina

> It could be possible to just make a symlink instead, but that would ugly. Better
> just get read of espeak.
> 
> Cheers,
> Didier
> 
> 

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Didier Spaier]

On 28/12/2021 20:50, Janina Sajka wrote:
> Didier Spaier writes:
>> Hi Janina and all,
>>
>> On 28/12/2021 17:26, Janina Sajka wrote:
>>> ...
>>>
>>> Apparently there must be some kind of reason why Espeakup can't be
>>> agnostic between espeak and espeak-ng?
>>
>> espeakup is linked against the shared library installed at time of building it.
>>
>> Here:
>> dance[~]$ ldd /usr/bin/espeakup | grep libespeak
>> 	libespeak-ng.so.1 => /usr/lib64/libespeak-ng.so.1 (0x00007f290df83000)
>>
> Thanks, Didier. This does make sense.
> 
>> My guess is you will find libespeak.so.1 instead running the same command.
>>
>> So you need to rebuild espeakup-0.90 after having removed espeak and installed
>> espeak-ng only.
>>
> Are you saying I need to run ldd by hand? I thought the installation
> process upgrading from 80 to 90 would take care of the ldd?

ldd just gives an information about the dependencies. As its man page says:

ldd  prints the shared objects (shared libraries) required by each program or
shared object specified on the command line.

During the installation process maybe the program in Arch that performs the
installation checks the presence of the required dependency (probably not using
ldd but rather according to the information recorded in some file by the packager).

If so and if my assumption is correct:
1) When the packager built espeakup, espeak (not espeak-ng) was installed.
2) you can check this running the above ldd command
3) therefore espeakup can't use easpeak-ng, only easpeak.

> It's true I did not run an ldd when I tried to upgrade my older machine
> to espeak-ng and espeakup-0.90.

In any case you need to rebuild espeakup-0.90 against espeak-ng. How to do that
in Arch properly is beyond my knowledge. Here "properly" means "in such a way
that the package can be handled by Arch's packages management system". Abyway
the generic steps are:
1) make sure espeak be not installed.
2) make sure espeak-ng is installed.
3) build and install espaekup.

Oh, and computer programs are not agnostic, in the sense that their dependencies
need to meet some specifications so they can run.

Human beings can be agnostics, as Didier, but I digress...

Cheers,
Didier

> 
> Best,
> 
> Janina
> 
>> It could be possible to just make a symlink instead, but that would ugly. Better
>> just get read of espeak.
>>
>> Cheers,
>> Didier
>>
>>
> 

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Didier Spaier]

I jut checked to be sure, actually espeakup-0.90 needs espeak-ng not espeak, so
building fails if it is not installed. In previous version instead it needed a
patch to be built against espeak-ng. This does not chnage the procedure if you
build espeakup-0.90.

On 28/12/2021 21:15, Didier Spaier wrote:
> On 28/12/2021 20:50, Janina Sajka wrote:
>> Didier Spaier writes:
>>> Hi Janina and all,
>>>
>>> On 28/12/2021 17:26, Janina Sajka wrote:
>>>> ...
>>>>
>>>> Apparently there must be some kind of reason why Espeakup can't be
>>>> agnostic between espeak and espeak-ng?
>>>
>>> espeakup is linked against the shared library installed at time of building it.
>>>
>>> Here:
>>> dance[~]$ ldd /usr/bin/espeakup | grep libespeak
>>> 	libespeak-ng.so.1 => /usr/lib64/libespeak-ng.so.1 (0x00007f290df83000)
>>>
>> Thanks, Didier. This does make sense.
>>
>>> My guess is you will find libespeak.so.1 instead running the same command.
>>>
>>> So you need to rebuild espeakup-0.90 after having removed espeak and installed
>>> espeak-ng only.
>>>
>> Are you saying I need to run ldd by hand? I thought the installation
>> process upgrading from 80 to 90 would take care of the ldd?
> 
> ldd just gives an information about the dependencies. As its man page says:
> 
> ldd  prints the shared objects (shared libraries) required by each program or
> shared object specified on the command line.
> 
> During the installation process maybe the program in Arch that performs the
> installation checks the presence of the required dependency (probably not using
> ldd but rather according to the information recorded in some file by the packager).
> 
> If so and if my assumption is correct:
> 1) When the packager built espeakup, espeak (not espeak-ng) was installed.
> 2) you can check this running the above ldd command
> 3) therefore espeakup can't use easpeak-ng, only easpeak.
> 
>> It's true I did not run an ldd when I tried to upgrade my older machine
>> to espeak-ng and espeakup-0.90.
> 
> In any case you need to rebuild espeakup-0.90 against espeak-ng. How to do that
> in Arch properly is beyond my knowledge. Here "properly" means "in such a way
> that the package can be handled by Arch's packages management system". Abyway
> the generic steps are:
> 1) make sure espeak be not installed.
> 2) make sure espeak-ng is installed.
> 3) build and install espaekup.
> 
> Oh, and computer programs are not agnostic, in the sense that their dependencies
> need to meet some specifications so they can run.
> 
> Human beings can be agnostics, as Didier, but I digress...
> 
> Cheers,
> Didier
> 
>>
>> Best,
>>
>> Janina
>>
>>> It could be possible to just make a symlink instead, but that would ugly. Better
>>> just get read of espeak.
>>>
>>> Cheers,
>>> Didier
>>>
>>>
>>
> 

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Alexander Epaneshnikov]

On Tue, Dec 28, 2021 at 09:15:07PM +0100, Didier Spaier wrote:
> On 28/12/2021 20:50, Janina Sajka wrote:
> > Didier Spaier writes:
> >> Hi Janina and all,
> >>
> >> On 28/12/2021 17:26, Janina Sajka wrote:
> >>> ...
> >>>
> >>> Apparently there must be some kind of reason why Espeakup can't be
> >>> agnostic between espeak and espeak-ng?
> >>
> >> espeakup is linked against the shared library installed at time of building it.
> >>
> >> Here:
> >> dance[~]$ ldd /usr/bin/espeakup | grep libespeak
> >> 	libespeak-ng.so.1 => /usr/lib64/libespeak-ng.so.1 (0x00007f290df83000)
> >>
> > Thanks, Didier. This does make sense.
> >
> >> My guess is you will find libespeak.so.1 instead running the same command.
> >>
> >> So you need to rebuild espeakup-0.90 after having removed espeak and installed
> >> espeak-ng only.
> >>
> > Are you saying I need to run ldd by hand? I thought the installation
> > process upgrading from 80 to 90 would take care of the ldd?
>
> ldd just gives an information about the dependencies. As its man page says:
>
> ldd  prints the shared objects (shared libraries) required by each program or
> shared object specified on the command line.
>
> During the installation process maybe the program in Arch that performs the
> installation checks the presence of the required dependency (probably not using
> ldd but rather according to the information recorded in some file by the packager).
>
> If so and if my assumption is correct:
> 1) When the packager built espeakup, espeak (not espeak-ng) was installed.
> 2) you can check this running the above ldd command
> 3) therefore espeakup can't use easpeak-ng, only easpeak.

espeakup 0.90 linked with espeak-ng in arch.

> > It's true I did not run an ldd when I tried to upgrade my older machine
> > to espeak-ng and espeakup-0.90.
>
> In any case you need to rebuild espeakup-0.90 against espeak-ng. How to do that

no need to do that.
Janina are you using pipewire on box with not working espeakup?
currently espeakup hasn't work with pw. I haven't found time to debug this yet.
sorry.

--
Sincerely, Alexander

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Hi, Alexander:

Alexander Epaneshnikov writes:
> On Tue, Dec 28, 2021 at 09:15:07PM +0100, Didier Spaier wrote:
> > On 28/12/2021 20:50, Janina Sajka wrote:
> ...
> > In any case you need to rebuild espeakup-0.90 against espeak-ng. How to do that
> 
> no need to do that.
> Janina are you using pipewire on box with not working espeakup?
> currently espeakup hasn't work with pw. I haven't found time to debug this yet.
> sorry.
> 
OK, Alexander. I understand time is a precious thing! <smile> Since
Espeakup is behaving on both my machines, I'm a happy customer, i.e. I
don't mind that I'm using old espeak on one machine, and espeak-ng on
the other. That really doesn't bother me at all. I'm glad I'm now able
to keep the remainder of the audio infrastructure updating.

Yes, I seem to have a full compliment of pw on the older machine, and
the same set of pw on the newer machine.

Interestingly, the files in /etc/alsa/conf.d/ are different. The new
machine shows only two files there:

50-pipewire.conf
99-pipewire-default.conf

On the older machine, earlier today, I tried renumber my alsa devices
via /etc/modprobe.d/alsa.conf. I ended up putting things back the way
they were, because the builtin Intel HDA device doesn't work as card 0
for some reason--very strange, but I adjusted some time ago to start
numbering my three devices as 1, 2 and 3.  So, after I put things back,
a see much more pw in that directory:

10-samplerate.conf
10-speexrate.conf
50-arcam-av-ctl.conf
50-jack.conf
50-oss.conf
50-pipewire.conf
50-pulseaudio.conf
60-speex.conf
60-upmix.conf
60-vdownmix.conf
98-usb-stream.conf
99-pipewire-default.conf


This suggests to me that the conversion to pw is still a work in
progress!

I've no idea why the above is the situation, though, or what packages
handle what aspect.

Best,

Janina

> --
> Sincerely, Alexander

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Alexander Epaneshnikov]

On Tue, Dec 28, 2021 at 05:40:21PM -0500, Janina Sajka wrote:
> Yes, I seem to have a full compliment of pw on the older machine, and
> the same set of pw on the newer machine.

strange. I think espeakup will not work if pw is inuse.

> Interestingly, the files in /etc/alsa/conf.d/ are different. The new
> machine shows only two files there:
>
> 50-pipewire.conf
> 99-pipewire-default.conf
>
> On the older machine, earlier today, I tried renumber my alsa devices
> via /etc/modprobe.d/alsa.conf. I ended up putting things back the way
> they were, because the builtin Intel HDA device doesn't work as card 0
> for some reason--very strange, but I adjusted some time ago to start
> numbering my three devices as 1, 2 and 3.  So, after I put things back,
> a see much more pw in that directory:
>
> 10-samplerate.conf
> 10-speexrate.conf
> 50-arcam-av-ctl.conf
> 50-jack.conf
> 50-oss.conf
> 50-pipewire.conf
> 50-pulseaudio.conf
> 60-speex.conf
> 60-upmix.conf
> 60-vdownmix.conf
> 98-usb-stream.conf
> 99-pipewire-default.conf
>
>
> This suggests to me that the conversion to pw is still a work in
> progress!
>
> I've no idea why the above is the situation, though, or what packages
> handle what aspect.

you can use pacman -Qo /path/to/file to check which package owns this file.

> Best,
>
> Janina

--
Sincerely, Alexander

Re: Now Fixed: Archlinux Speakup problems after alsa package upgrade

[Janina Sajka]

Alexander Epaneshnikov writes:
> On Tue, Dec 28, 2021 at 05:40:21PM -0500, Janina Sajka wrote:
> > Yes, I seem to have a full compliment of pw on the older machine, and
> > the same set of pw on the newer machine.
> 
> strange. I think espeakup will not work if pw is inuse.
> 

I have 0.90 on the newer machine and 0.80 on the older machine, both
working perfectly well. Perhaps pipewire is just piping alsa calls?

> > Interestingly, the files in /etc/alsa/conf.d/ are different. The new
> > machine shows only two files there:
> >
> > 50-pipewire.conf
> > 99-pipewire-default.conf
> >
> > On the older machine, earlier today, I tried renumber my alsa devices
> > via /etc/modprobe.d/alsa.conf. I ended up putting things back the way
> > they were, because the builtin Intel HDA device doesn't work as card 0
> > for some reason--very strange, but I adjusted some time ago to start
> > numbering my three devices as 1, 2 and 3.  So, after I put things back,
> > a see much more pw in that directory:
> >
> > 10-samplerate.conf
> > 10-speexrate.conf
> > 50-arcam-av-ctl.conf
> > 50-jack.conf
> > 50-oss.conf
> > 50-pipewire.conf
> > 50-pulseaudio.conf
> > 60-speex.conf
> > 60-upmix.conf
> > 60-vdownmix.conf
> > 98-usb-stream.conf
> > 99-pipewire-default.conf
> >
> >
> > This suggests to me that the conversion to pw is still a work in
> > progress!
> >
> > I've no idea why the above is the situation, though, or what packages
> > handle what aspect.
> 
> you can use pacman -Qo /path/to/file to check which package owns this file.
oThanks! Just did that and reinstalled alsa-plugins as well as pipewire.
I now have the full compliment of scripts in that directory.

Janina

> 
> > Best,
> >
> > Janina
> 
> --
> Sincerely, Alexander

-- 

Janina Sajka
(she/her/hers)
https://linkedin.com/in/jsajka

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Co-Chair, Accessible Platform Architectures	http://www.w3.org/wai/apa