Re: Orca Using orca at gdm
- From: Willie Walker <William Walker Sun COM>
- To: "Padraig O'Briain" <Padraig Obriain Sun COM>
- Cc: orca-list gnome org
- Subject: Re: Orca Using orca at gdm
- Date: Mon, 08 Jan 2007 11:52:00 -0500
Hi Padraig:
I did some work with Brian prior to the Orca v2.17.4 release to get Orca
and gdm working well together. At the time (around 08-Dec and on an
early 50's release of Nevada x86), it worked very well.
The _exit(50) you're seeing is coming from gnomespeechfactory.py, and it
is happening due to what looks like some repeated resets of speech.
These will occur if the synthesis driver is dying (or maybe it just
never activated correctly). It may be that the activation of the
synthesis driver is just plain failing.
Will
On Mon, 2007-01-08 at 14:38 +0000, Padraig O'Briain wrote:
I am looking at why orca does not start when one proesses ctrl+s at gdm
screen on Solaris.
I am using orca 2.17.4 and I have got to the stage where the
orca process, /usr/bin/python -c import orca.orca; orca.orca.main() -n
-d main-window
and freetts-synthesis-driver process start.
However the orca process exits with _exit(50).
If I stop gdm and restart it leaving freetts-synthesis-driver running
then the orca process does not terminate.
This suggest that the problem may be timing out waiting for the speech
driver to be initialised. I have noticed that shortly before the orca
process terminates it receives a SIGALRM signal.
Help solving this would be greatly appreciated.
Padraig
_______________________________________________
Orca-list mailing list
Orca-list gnome org
http://mail.gnome.org/mailman/listinfo/orca-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]