* speech-dispatcher 0.6.4 issue @ Chuck Hallenbeck ` Hynek Hanke 0 siblings, 1 reply; 10+ messages in thread From: Chuck Hallenbeck @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I know this is not the right list, but my mail to the speech-dispatcher list is being rejected as spam due to an issue with my mail service. This is not a good day all around. I installed my speech-dispatcher 0.6.4 this morning and am having some unexpected issues with it. I have most of them clarified, but one remains. I hope Hynek is reading the list, or someone else might have a suggestion. I have speech-dispatcher configured to add only one module, flite. It works fine, and I have software speech with flite. But it blocks the /dev/dsp device so that other applications cannot use it. Stopping the speech-dispatcher program frees up the device, starting it again blocks it, even before flite is used to speak anything. Any clues or pointers as to where to look for this one would be appreciated. I have been tinkering a lot lately, and cannot say for sure what is running and what is not. But the launching of speech-dispatcher ties up /dev/dsp, and killing it frees the device, that much seems clear. Chuck - -- The Moon is Waning Gibbous (86% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2DsI0maTgpPXM9cRAjkYAKCJnbVUdROmjiUSec+87EnR0e1iqwCfbeLW RTaHXFGu2dV63RcY1FfFIGM= =bh7W -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue speech-dispatcher 0.6.4 issue Chuck Hallenbeck @ ` Hynek Hanke ` Chuck Hallenbeck 0 siblings, 1 reply; 10+ messages in thread From: Hynek Hanke @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. > I installed my speech-dispatcher 0.6.4 this morning > I have speech-dispatcher configured to add only one > module, flite. It> works fine, and I have software speech > with flite. But it blocks the /dev/dsp device so that other > applications cannot use it. Hi Chuck, this shouldn't be. I think the cause is very likely one of three things. You might have flite configured to use OSS instead of ALSA. Please look at /usr/local/etc/speech-dispatcher/modules/flite.conf for FliteAudioOutputMethod . It should be set to "alsa". In case you are using "alsa", then the reason can be that you are loading either another output module which uses OSS. Be sure to keep only the AddModule line for flite in speechd.conf, others comment out with hash. If neither of these is true, you are using ALSA, but it blocks itself, and cannot emulate /dev/dsp properly. This was long a bug of ALSA, that a system user playing sound through ALSA will block all other system users from connecting to ALSA. Since Speech Dispatcher is running as root and you want to play sounds as a regular user, this might be a problem. Upgrade to more recent versions of ALSA should solve the problem (to test whether this is the reason, try running speechd as root and aplay some sound as root -- if it works, ALSA blocks other users than root, as described...) I hope it helps, otherwise please write more. Have a nice day, Hynek Hanke ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Hynek Hanke @ ` Chuck Hallenbeck ` Chuck Hallenbeck ` Chuck Hallenbeck 0 siblings, 2 replies; 10+ messages in thread From: Chuck Hallenbeck @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hynek, thanks for the response. On Fri, Aug 31, 2007 at 10:50:28AM -0700, Hynek Hanke wrote: > > You might have flite configured to use OSS instead of ALSA. > Please look at /usr/local/etc/speech-dispatcher/modules/flite.conf > for FliteAudioOutputMethod . It should be set to "alsa". My speech-dispatcher was installed as a Debian package, so the configuration is in /etc/speech-dispatcher. Here is the line from flite.conf: FliteAudioOutputMethod "alsa" > > In case you are using "alsa", then the reason can be that you > are loading either another output module which uses OSS. > Be sure to keep only the AddModule line for flite in speechd.conf, > others comment out with hash. Here are my AddModule lines from speechd.conf: AddModule "flite" "sd_flite" "flite.conf" "/var/log/speech-dispatcher/flite.log" #AddModule "festival" "sd_festival" "festival.conf" "/var/log/speech-dispatcher/festival.log" #AddModule "espeak-generic" "sd_generic" "espeak-generic.conf" "/var/log/speech-dispatcher/espeak-generic.log" #AddModule "espeak" "sd_espeak" "espeak.conf" "/var/log/speech-dispatcher/espeak.log" #AddModule "epos-generic" "sd_generic" "epos-generic.conf" "/var/log/speech-dispatcher/epos.log" #AddModule "dtk-generic" "sd_generic" "dtk-generic.conf" "/var/log/speech-dispatcher/dtk-generic.log" #AddModule "ibmtts" "sd_ibmtts" "ibmtts.conf" "/var/log/speech-dispatcher/ibmtts.log" #AddModule "cicero" "sd_cicero" "cicero.conf" "/var/log/speech-dispatcher/cicero.log" > > If neither of these is true, you are using ALSA, but it blocks > itself, and cannot emulate /dev/dsp properly. This was long > a bug of ALSA, that a system user playing sound through ALSA > will block all other system users from connecting to ALSA. > Since Speech Dispatcher is running as root and you want to > play sounds as a regular user, this might be a problem. Upgrade > to more recent versions of ALSA should solve the problem My kernel is 2.6.21, and cat /proc/asound/version shows this: Advanced Linux Sound Architecture Driver Version 1.0.14rc3 (Wed Mar 14 07:25:50 2007 UTC). > (to test whether this is the reason, try running speechd as root > and aplay some sound as root -- if it works, ALSA blocks other > users than root, as described...) > Speech-dispatcher is started during system startup in /etc/init.d/speech-dispatcher, and if it is running, then the madplay program finds /dev/dsp blocked, but the play command has no problem. Stopping speech-dispatcher allows madplay to use the /dev/dsp device, and of course play can do so as well. Other applications that find /dev/dsp blocked include festival and swift. I have been using speech-dispatcher 0.6.2 from the Debian package along with espeak 1.26, also from the Debian package, for quite some time without these problems. Any more information I can offer, please let me know. Chuck - -- The Moon is Waning Gibbous (85% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2GKU0maTgpPXM9cRAq+wAKCbxNRiZlQ7iAJ66Fl1y/4x4Tl8lgCfQ6PS NC/49+PLRArQsHzfiS+oLEk= =/ppS -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Chuck Hallenbeck @ ` Chuck Hallenbeck ` Jan Buchal ` Chuck Hallenbeck 1 sibling, 1 reply; 10+ messages in thread From: Chuck Hallenbeck @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hynek, I neglected to include a demo of the failure. Here it is: cq:~# madplay /pub/mp3misc/townclock.mp3 MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al. audio: /dev/dsp: Device or resource busy cq:~# play /usr/local/share/mywaves/hello.wav Input File : '/usr/local/share/mywaves/hello.wav' Sample Size : 16-bit (2 bytes) Sample Encoding: signed (2's complement) Channels : 1 Sample Rate : 22050 Time: 00:01.07 [00:00.00] of 00:01.07 ( 100.0%) Output Buffer: 51.26K Done. cq:~# invoke-rc.d speech-dispatcher stop Stopping Speech Dispatcher: speech-dispatcher. cq:~# madplay /pub/mp3misc/townclock.mp3 MPEG Audio Decoder 0.15.2 (beta) - Copyright (C) 2000-2004 Robert Leslie et al. 334 frames decoded (0:00:17.4), -11.4 dB peak amplitude, 0 clipped samples cq:~# Hope that helps illustrate the problem, but it also happens with swift and festival, which are using /dev/dsp as well. Chuck - -- The Moon is Waning Gibbous (85% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2GQQ0maTgpPXM9cRAlN4AJ9jEFsVlN3AjJskEEvtW3Vb159YPwCfd/DV lvS+fh0xRNHCzNHanOWwu4k= =UJYY -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Chuck Hallenbeck @ ` Jan Buchal ` Chuck Hallenbeck 0 siblings, 1 reply; 10+ messages in thread From: Jan Buchal @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Hello, if you use alsa then all application which have play must use native alsa or an emulation. For example in Debian you can use alsa-oss package and then command: aoss SOMEPLAYPROGRAMM. p.s. Can you please send me more information about the Spam problem with your email and our speechd mailing list? Thanks. -- Jan Buchal Tel: (00420) 24 24 86 008 Mob: (00420) 608023021 ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Jan Buchal @ ` Chuck Hallenbeck ` Kerry Hoath ` Lukas Loehrer 0 siblings, 2 replies; 10+ messages in thread From: Chuck Hallenbeck @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jan and Willem, thanks for your suggestions. And Jan, thanks for helping fix the speechd mailing list issue. The aoss solution does not work for me. At least not completely. The test Willem made using the play command was not conclusive, since as I think I reported earlier, the play command continues to work when other oss applications, such as swift, madplay, and flite, all fail. I used aoss followed by examples of swift, madplay, and flite, with and without speech-dispatcher running. Here is what I find: 1. madplay works as well with or without speech-dispatcher, so that seems to solve the issue for that application. 2. swift and flite sound unacceptably distorted when used with aoss, with or without speech-dispatcher running. So while aoss seems to solve the speech-dispatcher issue, it cannot be used due to this serious distortion. 3. Play works with or without aoss, with or without speech-dispatcher, and so is not a helpful application with which to test the problem. Finally, I have found that if I add only one module to speech-dispatcher, the espeak-generic module, all my applications work correctly and none of them require aoss. This behavior is new behavior for recent upgrades of speech-dispatcher on my system, but at the same time I have made so many other upgrades that I cannot say for sure where the problem lies. However, I do now have a solution: avoid adding the flite or festival modules when running speech-dispatcher. Chuck - -- The Moon is Waning Crescent (35% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG3pSJ0maTgpPXM9cRAvoeAJ9JNieFIrvHB++SyY9ykfuhG3S1IACeK5dB 5+3jbqg7nJmMio6G2gq1emY= =tECH -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Chuck Hallenbeck @ ` Kerry Hoath ` Chuck Hallenbeck ` Lukas Loehrer 1 sibling, 1 reply; 10+ messages in thread From: Kerry Hoath @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. It depends on what soundcard you have and whether or not the soundcard is using dmix. dmix is the plugin for alsa that mixes output streams together, and it is part of the alsa-lib package I think or the plugins package I can't remember which one to be honest. It depends on which soundcard you are using as to how many hardware output channels you have; however dmix is supposed to mix in software to overcome this problem. Make sure your libs, utils and driver are all 1.14rc something or later because they changed the way they handled the plugins in 1.0.13 or later I seem to recall. None of this may help; and I haven't tried to use alsa with speech dispatcher. the killer will be to test if 2 oss applications can run at the same time with alsa; is it a multiple open problem on /dev/dsp or is it specific to speech dispatcher? Shouldn't speech dispatcher be using alsa directly and if so; should this not free up /dev/dsp if dmix is in use? We need to acertain if this is speech dispatcher's fault or simply a funny with alsa and its plugins even if it did work before. No idea if any of the above helps; i've had a long day at work and i'm just thinking at my keyboard. Regards, Kerry. ----- Original Message ----- From: "Chuck Hallenbeck" <chuckh@ftml.net> To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca> Sent: Wednesday, September 05, 2007 7:35 PM Subject: Re: speech-dispatcher 0.6.4 issue > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jan and Willem, thanks for your suggestions. > > And Jan, thanks for helping fix the speechd mailing list issue. > > The aoss solution does not work for me. At least not completely. The > test Willem made using the play command was not conclusive, since as I > think I reported earlier, the play command continues to work when other > oss applications, such as swift, madplay, and flite, all fail. > > I used aoss followed by examples of swift, madplay, and flite, with and > without speech-dispatcher running. Here is what I find: > > 1. madplay works as well with or without speech-dispatcher, so that > seems to solve the issue for that application. > > 2. swift and flite sound unacceptably distorted when used with aoss, > with or without speech-dispatcher running. So while aoss seems to solve > the speech-dispatcher issue, it cannot be used due to this serious > distortion. > > 3. Play works with or without aoss, with or without speech-dispatcher, > and so is not a helpful application with which to test the problem. > > Finally, I have found that if I add only one module to > speech-dispatcher, the espeak-generic module, all my applications work > correctly and none of them require aoss. > > This behavior is new behavior for recent upgrades of speech-dispatcher > on my system, but at the same time I have made so many other upgrades > that I cannot say for sure where the problem lies. However, I do now > have a solution: avoid adding the flite or festival modules when > running speech-dispatcher. > > Chuck > > - -- > The Moon is Waning Crescent (35% of Full) > My new web site location is at: http://hallenbeck.ftml.net > College, that fountain of knowledge, where everyone goes to drink. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFG3pSJ0maTgpPXM9cRAvoeAJ9JNieFIrvHB++SyY9ykfuhG3S1IACeK5dB > 5+3jbqg7nJmMio6G2gq1emY= > =tECH > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Kerry Hoath @ ` Chuck Hallenbeck 0 siblings, 0 replies; 10+ messages in thread From: Chuck Hallenbeck @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Kerry, Thanks. My alsa is 0.1.14RC3, and dmix is running. I can play multiple alsa apps simultaneously, and I can play one oss application along with an alsa application, but I can only run one oss application at a time. My sound subsystem is the onboard system with the Intel D945 motherboard, and the alsa driver is pretty primitive for it, the snd-hda-intel. It lacks a lot of controls I am used to. Chuck On Wed, Sep 05, 2007 at 08:34:14PM +0800, Kerry Hoath wrote: > It depends on what soundcard you have and whether or not the soundcard is > using dmix. > > dmix is the plugin for alsa that mixes output streams together, > and it is part of the alsa-lib package I think or the plugins package I > can't remember which one to be honest. > > It depends on which soundcard you are using as to how many hardware output > channels you have; however dmix is supposed to mix in software to overcome > this problem. > > Make sure your libs, utils and driver are all 1.14rc something or later > because they changed the way they handled the plugins in 1.0.13 or later I > seem to recall. > > None of this may help; and I haven't tried to use alsa with speech > dispatcher. > the killer will be to test if 2 oss applications can run at the same time > with alsa; > is it a multiple open problem on /dev/dsp or is it specific to speech > dispatcher? > Shouldn't speech dispatcher be using alsa directly and if so; should this > not free up /dev/dsp if dmix is in use? > > We need to acertain if this is speech dispatcher's fault or simply a funny > with alsa and its plugins even if it did work before. > > No idea if any of the above helps; i've had a long day at work and i'm just > thinking at my keyboard. > > Regards, Kerry. > > ----- Original Message ----- > From: "Chuck Hallenbeck" <chuckh@ftml.net> > To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca> > Sent: Wednesday, September 05, 2007 7:35 PM > Subject: Re: speech-dispatcher 0.6.4 issue > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Jan and Willem, thanks for your suggestions. > > > > And Jan, thanks for helping fix the speechd mailing list issue. > > > > The aoss solution does not work for me. At least not completely. The > > test Willem made using the play command was not conclusive, since as I > > think I reported earlier, the play command continues to work when other > > oss applications, such as swift, madplay, and flite, all fail. > > > > I used aoss followed by examples of swift, madplay, and flite, with and > > without speech-dispatcher running. Here is what I find: > > > > 1. madplay works as well with or without speech-dispatcher, so that > > seems to solve the issue for that application. > > > > 2. swift and flite sound unacceptably distorted when used with aoss, > > with or without speech-dispatcher running. So while aoss seems to solve > > the speech-dispatcher issue, it cannot be used due to this serious > > distortion. > > > > 3. Play works with or without aoss, with or without speech-dispatcher, > > and so is not a helpful application with which to test the problem. > > > > Finally, I have found that if I add only one module to > > speech-dispatcher, the espeak-generic module, all my applications work > > correctly and none of them require aoss. > > > > This behavior is new behavior for recent upgrades of speech-dispatcher > > on my system, but at the same time I have made so many other upgrades > > that I cannot say for sure where the problem lies. However, I do now > > have a solution: avoid adding the flite or festival modules when > > running speech-dispatcher. > > > > Chuck > > > > - -- > > The Moon is Waning Crescent (35% of Full) > > My new web site location is at: http://hallenbeck.ftml.net > > College, that fountain of knowledge, where everyone goes to drink. > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.4.6 (GNU/Linux) > > > > iD8DBQFG3pSJ0maTgpPXM9cRAvoeAJ9JNieFIrvHB++SyY9ykfuhG3S1IACeK5dB > > 5+3jbqg7nJmMio6G2gq1emY= > > =tECH > > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup - -- The Moon is Waning Crescent (34% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG3qYD0maTgpPXM9cRAjX6AKCHQD4hAT3voFbB3bGXf5uxFuE/9ACfRFH4 sGXm5p9a3DNqNcn/cAHLlnU= =VbZG -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Chuck Hallenbeck ` Kerry Hoath @ ` Lukas Loehrer 1 sibling, 0 replies; 10+ messages in thread From: Lukas Loehrer @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. I doubht your problem is specific to speech-dispatcher. In general, it is true that multiple applications can play sound via alsa at the same time using plugins like dmix. However, they will still prevent OSS programs from accessing /dev/dsp. There appear to be ways of configuring alsa in such a way that /dev/dsp goes through dmix as well, but I have never managed to get this to work myself. Your best bet is to use Alsa enabled applications wherever possible and use aoss for the legacy OSS stuff. As for the aoss command, it seems to depend heavily on the specific OSS application whether or not you get usable results with it. For flite, use a version of flite that contains my patch for alsa support. Best regards, Lukas Chuck Hallenbeck writes ("Re: speech-dispatcher 0.6.4 issue"): > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Jan and Willem, thanks for your suggestions. > > And Jan, thanks for helping fix the speechd mailing list issue. > > The aoss solution does not work for me. At least not completely. The > test Willem made using the play command was not conclusive, since as I > think I reported earlier, the play command continues to work when other > oss applications, such as swift, madplay, and flite, all fail. > > I used aoss followed by examples of swift, madplay, and flite, with and > without speech-dispatcher running. Here is what I find: > > 1. madplay works as well with or without speech-dispatcher, so that > seems to solve the issue for that application. > > 2. swift and flite sound unacceptably distorted when used with aoss, > with or without speech-dispatcher running. So while aoss seems to solve > the speech-dispatcher issue, it cannot be used due to this serious > distortion. > > 3. Play works with or without aoss, with or without speech-dispatcher, > and so is not a helpful application with which to test the problem. > > Finally, I have found that if I add only one module to > speech-dispatcher, the espeak-generic module, all my applications work > correctly and none of them require aoss. > > This behavior is new behavior for recent upgrades of speech-dispatcher > on my system, but at the same time I have made so many other upgrades > that I cannot say for sure where the problem lies. However, I do now > have a solution: avoid adding the flite or festival modules when > running speech-dispatcher. > > Chuck > > - -- > The Moon is Waning Crescent (35% of Full) > My new web site location is at: http://hallenbeck.ftml.net > College, that fountain of knowledge, where everyone goes to drink. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFG3pSJ0maTgpPXM9cRAvoeAJ9JNieFIrvHB++SyY9ykfuhG3S1IACeK5dB > 5+3jbqg7nJmMio6G2gq1emY= > =tECH > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > ^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: speech-dispatcher 0.6.4 issue ` Chuck Hallenbeck ` Chuck Hallenbeck @ ` Chuck Hallenbeck 1 sibling, 0 replies; 10+ messages in thread From: Chuck Hallenbeck @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hynek, and another illustration. The sound is heard immediately before the final line below, the return of the cq prompt: cq:~# invoke-rc.d speech-dispatcher start Starting Speech Dispatcher: speech-dispatcher. cq:~# swift hello world oss_audio: failed to open audio device /dev/dsp oss_audio: failed to open audio device /dev/dsp cq:~# invoke-rc.d speech-dispatcher stop Stopping Speech Dispatcher: speech-dispatcher. cq:~# swift hello world cq:~# and the same for several other apps using OSS, but apps using alsa continue to work fine, such as mplayer, aplay, and strangely enough, play itself. Chuck - -- The Moon is Waning Gibbous (85% of Full) My new web site location is at: http://hallenbeck.ftml.net College, that fountain of knowledge, where everyone goes to drink. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFG2GXZ0maTgpPXM9cRAj7QAJ9GB6nAzomm/cgz8AJzecbOsT3dfACgsz7f nR7ZpKcs6opXafoK19LCKoc= =qnrd -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
speech-dispatcher 0.6.4 issue Chuck Hallenbeck
` Hynek Hanke
` Chuck Hallenbeck
` Chuck Hallenbeck
` Jan Buchal
` Chuck Hallenbeck
` Kerry Hoath
` Chuck Hallenbeck
` Lukas Loehrer
` Chuck Hallenbeck
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).