Hi, Didier: Once again you're providing some very helpful guidance. Thank you so very much for that. Yes, I'm using arch, but I'm the other way around from what you're saying. I'm using speech-dispatcher-git, but only the espeakup release at the moment. The reason is that the current speech-dispatcher relase isn't correctly accepting an alsa card designation, i.e. it won't honor these two directives in speechd.conf: AudioOutputMethod "libao" AudioALSADevice "plughw:1" I am now going to put your espeakup script in place on my machine and try a reboot. I will report. Thank you for this script. I wasn't aware all these directives could be included. This should solve my problem, I hope! <grin> Janina Didier Spaier writes: > Hi Janina, > > IIRC you are running Arch. Right? > > If yes, looking at the PKGBUILD I see that it grabs a snapshot from > git at the commit d25ed10d dated 22 nov. 2018: > https://github.com/brailcom/speechd/commit/d25ed10d5ede8c0f747211928fbd5f742d753556 > > So I am puzzled that you just get it, knowing the PKGBUILD was last updated > on 24. Nov. 2018... > > So, I can't see a reason for speech-dispatcher be in concern for an issue > occurring this week. > > And espeakup-git (if that's what you use) was last updated on > 2019-01-03 18:14. > > So I am puzzled. I don't know what happened recently, but this issue should be > reported to your distribution rather than to upstream IMHO. > > Also, a tip: you can set ALSA_CARD before starting espeakup, it will > honor this setting. This how we now do in Slint, cf. attached file > /etc/espeakup.conf. > > To know which files are involved in Arch, have a look at the bottom > of https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=espeakup-git > > Sorry I can't provide further guidance, not running Arch. > > Best, > > Didier > > > On 22/03/2019 15:43, Janina Sajka wrote: > > I tend to update globally about once a week, usually on Fridays. With > > today's update of Speech-Dispatcher-git Espeakup is broken. > > > > 1.) I boot to a console login. Works as expected. Speakup speaks > > with Espeak on hw:0. Yes, I'm using alsa, not pulse. > > > > 2.) I launch the graphical desktop with startx and Orca comes up > > over Speech-Dispatcher using libao on hw:1 as specified in speechd.conf. > > > > 3.) Switching back to any console, speech is gone. Doing a systemctl > > restart espeakup puts speech on hw:2. > > > > This is bonkers. > > > > PS: Isn't it time we could control what device the soft synth driver > > speaks to with a configuration option? Perhaps an additional parameter > > in /etc/conf.d/espeakup? > > > > Or is it supposed to be in /etc/speakup/espeakup? > > > > Both those configs say basically the same thing, but they're not > > symlinked. Why? > > -- Janina Sajka Linux Foundation Fellow Executive Chair, Accessibility Workgroup: http://a11y.org The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI) Chair, Accessible Platform Architectures http://www.w3.org/wai/apa _______________________________________________ Speakup mailing list Speakup@xxxxxxxxxxxxxxxxx http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
