"Veli-Pekka Tatila" <vtatila@mail.student.oulu.fi> writes: > Now sound works both in the console and in Gnome just fine. Festival > and Flight speak all right in the console and even the Festival server > is running, I think. However, Gnopernicus doesn't give any speech > output at all. When testing the Kevin Festival voice in Gnopernicus, > it says the following: > > (srcore:684): gnopernicus-CRITICAL **: file libsrconf.c: line 247 > (sr_config_changed_callback): assertion `entry->value' failed > > Why does this appear and can anyone think of any solutions or workarounds? Not right now, but I will look into this tomorrow if I find time. I am up for 36 hours now, it is really time to get some physical rest... > Someone had a similar problem in a RedHat forum but no-one had > answered that one. > > I'm running Testing with a 2.4 kernel and the AWE 32 drivers and > currently no ALSA, I think. I've installed Gnopernicus, gnome-speech, > gnome-mag, festival and gnome with apt-get. Sounds OK. > In one mini Gnopernicus tutorial, it was adviced that you install > gnopernicus, festival and gnome-speech with all dependencies. How do I > do this with apt-get? I thought it should auto-install any dependent > packages anyway. Yes, that is true. apt-get automatically resolves dependencies for you. > Regarding that assert message, as far as I know assertions are a kind > of runtime, debugging aid. An app should only give an assertion if > something goes terribly wrong, that is something unexpected happens. Right. Can you post a complete log of what Gnopernicus emits from startup to when you get the assertion? BTW, Gnopernicus even worked for me on amd64 (pure64) last time I tried. -- CYa, Mario
Attachment:
pgpq1rI8LSHnX.pgp
Description: PGP signature