GNOME Bugzilla – Bug 304449
Gnopernicus can die if multiple errors from speech during speech recovery
Last modified: 2005-05-18 15:25:24 UTC
1. Start Gnopernicus, wait for speech to be fully initialized and working with FreeTTS. 2. From an xterm (or better still, another system using ssh into this system) 'pkill java' a whole bunch of times, while arrowing through the GUI causing Gnopernicus to try to speak. 3. Gnopernicus will try to reinitialize speech, but will not only fail to do so (as expected), srcore will crash as well. The last messages in stdout/err from Gnopernicus are: (srcore:6466): gnopernicus-WARNING **: Message : Unable to unref the speaker (srcore:6466): gnopernicus-WARNING **: Exception Unknown CORBA exception id: 'ID L:omg.org/CORBA/COMM_FAILURE:1.0' occured. (srcore:6466): gnopernicus-WARNING **: Message : Unable to unref the driver (srcore:6466): gnopernicus-WARNING **: Exception Unknown CORBA exception id: 'ID L:omg.org/CORBA/COMM_FAILURE:1.0' occured. (srcore:6466): gnopernicus-WARNING **: Message : Cannot create speaker ! Restarting speech. gnopernicus-ERROR **: file srs-gs-wrap.c: line 469 (srs_gs_wrap_speaker_set_para meter): assertion failed: (speaker && name) aborting... (gnopernicus:6465): gnopernicus-WARNING **: srcore exited.
Created attachment 46532 [details] [review] proposed patch If an error occurs during creating a gnom-speech speaker, then, the gnopernicus voice using it is not reported as created.
Created attachment 46543 [details] [review] improved patch This patch also fixes bug #304448.
Comment on attachment 46543 [details] [review] improved patch Patch committed.