Re: gnome-terminal crash in Feisty
We need to know what the calls in libvte are. Padraig Kenny Hitt wrote: > Hi. > > Thanks to help from Luke, I was able to get the following from gdb. > > Program received signal SIGABRT, Aborted. > [Switching to Thread -1226291520 (LWP 15468)] > 0xb7fba410 in ?? () > (gdb) bt > #0 0xb7fba410 in ?? () > #1 0xbfa25e6c in ?? () > #2 0x0006 in ?? () > #3 0x3c6c in ?? () > #4 0xb759cdf0 in raise () from /lib/tls/i686/cmov/libc.so.6 > #5 0xb759e641 in abort () from /lib/tls/i686/cmov/libc.so.6 > #6 0xb76eb4b2 in g_logv () from /usr/lib/libglib-2.0.so.0 > #7 0xb76eb4e9 in g_log () from /usr/lib/libglib-2.0.so.0 > #8 0xb76ea0b9 in g_malloc () from /usr/lib/libglib-2.0.so.0 > #9 0xb7dedbe7 in ?? () from /usr/lib/libvte.so.9 > #10 0xffd2 in ?? () > #11 0xb7e70ae8 in ?? () from /usr/lib/libvte.so.9 > #12 0x in ?? () > > > I noticed gdb didn't find debug symbols for some of the libs linked to > gnome-terminal. Is this enough info, or do I need to do more? > > Kenny > > On Mon, Jan 08, 2007 at 03:48:37PM +, Padraig O'Briain wrote: > >> I think that a stack trace for gnome-terminal process will be necessary. >> >> Padraig >> >> Kenny Hitt wrote: >> >>> Hi. >>> >>> I am having a strange problem using gnome-terminal in Feisty. >>> Gnome-terminal crashes with no error dialog. Then it crashes, all >>> terminal sessions close. The crash is random, but it seems to happen >>> when I use a Orca review key. >>> >>> Gnome-terminal is at version 2.16.1-0ubuntu1 >>> Libvte9 is at version 1:0.15.0-0ubuntu1 >>> >>> The only other information I can provide is my .xsession-errors file. >>> If there's anything I can do to provide more information, please let me >>> know and I'll do it. >>> >>> Thanks in advance. >>> Kenny >>> >>> >>> >>> >>> /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp >>> /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w >>> /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" >>> "kenny" >>> /etc/gdm/Xsession: Beginning session setup... >>> Xlib: extension "XEVIE" missing on display ":0.0". >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 >>> GTK Accessibility Module initialized >>> >>> ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. >>> GTK Accessibility Module initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> Initializing gnome-mount extension >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> >>> ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 >>> >>> ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 >>> 1168248013 >>> evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 >>> >>> evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 >>> >>> GTK Accessibility Module initialized >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> ** Message: drive = 0 >>> ** Message: volume = 0 >>> >>> (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to >>> allocate widget with width -3 and height 24 >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> >>> ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray >>> icon, because the CUPS server could not be contacted. >>> anykey >>> anykey >>> anykey >>> anykey >>> GTK Accessibility Module initialized >>> Bonobo accessibility support initialized >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> Window manager warning: Log level 8: atk_relation_set_get_n_relations: >>> assertion `ATK_IS_RELATION_SET (set)' failed >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> anykey >>> an
Re: gnome-terminal crash in Feisty
Hi. Thanks to help from Luke, I was able to get the following from gdb. Program received signal SIGABRT, Aborted. [Switching to Thread -1226291520 (LWP 15468)] 0xb7fba410 in ?? () (gdb) bt #0 0xb7fba410 in ?? () #1 0xbfa25e6c in ?? () #2 0x0006 in ?? () #3 0x3c6c in ?? () #4 0xb759cdf0 in raise () from /lib/tls/i686/cmov/libc.so.6 #5 0xb759e641 in abort () from /lib/tls/i686/cmov/libc.so.6 #6 0xb76eb4b2 in g_logv () from /usr/lib/libglib-2.0.so.0 #7 0xb76eb4e9 in g_log () from /usr/lib/libglib-2.0.so.0 #8 0xb76ea0b9 in g_malloc () from /usr/lib/libglib-2.0.so.0 #9 0xb7dedbe7 in ?? () from /usr/lib/libvte.so.9 #10 0xffd2 in ?? () #11 0xb7e70ae8 in ?? () from /usr/lib/libvte.so.9 #12 0x in ?? () I noticed gdb didn't find debug symbols for some of the libs linked to gnome-terminal. Is this enough info, or do I need to do more? Kenny On Mon, Jan 08, 2007 at 03:48:37PM +, Padraig O'Briain wrote: > I think that a stack trace for gnome-terminal process will be necessary. > > Padraig > > Kenny Hitt wrote: > > Hi. > > > > I am having a strange problem using gnome-terminal in Feisty. > > Gnome-terminal crashes with no error dialog. Then it crashes, all > > terminal sessions close. The crash is random, but it seems to happen > > when I use a Orca review key. > > > > Gnome-terminal is at version 2.16.1-0ubuntu1 > > Libvte9 is at version 1:0.15.0-0ubuntu1 > > > > The only other information I can provide is my .xsession-errors file. > > If there's anything I can do to provide more information, please let me > > know and I'll do it. > > > > Thanks in advance. > > Kenny > > > > > > > > > > /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp > > /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w > > /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" > > "kenny" > > /etc/gdm/Xsession: Beginning session setup... > > Xlib: extension "XEVIE" missing on display ":0.0". > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 > > GTK Accessibility Module initialized > > > > ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. > > GTK Accessibility Module initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > Initializing gnome-mount extension > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > > > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 > > 1168248013 > > evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 > > > > evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 > > > > GTK Accessibility Module initialized > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > ** Message: drive = 0 > > ** Message: volume = 0 > > > > (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to > > allocate widget with width -3 and height 24 > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > > > ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray > > icon, because the CUPS server could not be contacted. > > anykey > > anykey > > anykey > > anykey > > GTK Accessibility Module initialized > > Bonobo accessibility support initialized > > anykey > > anykey > > anykey > > anykey > > anykey > > Window manager warning: Log level 8: atk_relation_set_get_n_relations: > > assertion `ATK_IS_RELATION_SET (set)' failed > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > anykey > > a
Re: espeak and orca
Hi. Yes, they are both available in the Orca preferences. Both aren't being used at the same time, but you can switch any time you want. Kenny On Mon, Jan 08, 2007 at 10:40:50PM +0100, Krister Ekstrom wrote: > On Mon, 2007-01-08 at 13:04 -0600, Kenny Hitt wrote: > > Normally, I use espeak with the speech-dispatcher gnome-speech driver. > > This driver doesn't support the read to end command, so I either > > switch > > to festival when I want to read an entire document, or use the direct > > speech-dispatcher backend for Orca. > > Can you actually use both drivers at the same time? I thought it was > > one or the other and installing them both would mean conflict. How > > does one choose between them? I guess they get visible in the orca > > prefs in some way, right? > -- > /Krister > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: espeak and orca
On Mon, 2007-01-08 at 13:04 -0600, Kenny Hitt wrote: > Normally, I use espeak with the speech-dispatcher gnome-speech driver. > This driver doesn't support the read to end command, so I either > switch > to festival when I want to read an entire document, or use the direct > speech-dispatcher backend for Orca. > Can you actually use both drivers at the same time? I thought it was > one or the other and installing them both would mean conflict. How > does one choose between them? I guess they get visible in the orca > prefs in some way, right? -- /Krister -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: espeak and orca
On Mon, 2007-01-08 at 17:56 +0100, Henrik Nilsen Omma wrote: > * For those who have eSpeak working (which option did you use the > experimental Orca support or the gnome-speech->SD bridge?) -- how is > it > working? Any issues? > Well it's working quite ok, i'd say. The only issues i have as of now is that i can't seem to use document reading (numeric plus) because Orca is only reading one line and then stops, but i think it has to do with the lack of indexing somewhere. I think it's a known issue. Other than that, i haven't had any noticable problems. I'm running the Speech dispatcher solution. -- /Krister -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: espeak and orca
Hi. The problem I have with festival is it's slow responsiveness. Normally, I use espeak with the speech-dispatcher gnome-speech driver. This driver doesn't support the read to end command, so I either switch to festival when I want to read an entire document, or use the direct speech-dispatcher backend for Orca. Kenny On Mon, Jan 08, 2007 at 05:56:04PM +0100, Henrik Nilsen Omma wrote: > You currently need speech-dispatcher to use eSpeak with Orca, and there > are some instructions here: http://live.gnome.org/Orca/SpeechDispatcher > > Gilles is working on a gnome-speech driver for eSpeak though which will > be a more robust solution (until SD and Orca support matures anyway). > > We are currently evaluating whay technical solutions to use for the > future so we are *very* interested in feedback about peoples user > experiences. > > * What is the exact problem with Festival, the speed of speech of lack > of responsiveness? > * For those who have eSpeak working (which option did you use the > experimental Orca support or the gnome-speech->SD bridge?) -- how is it > working? Any issues? > * When we have the gnome-speech eSpeak driver working how does that > compare with the other setups? > > etc. > > Henrik > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
Re: espeak and orca
Beth Koenig wrote: > I need this info ASAP also. Festival is driving me up a wall and is > WAY too slow. So instructions on how to get espeak on Orca would be > great. Also does anyone know where to find a binary of brlapi 4.1? I > am having problems getting my Braille Lite 2000 to work and I know > it's not brltty as I have been using it for years. It's not the > braille Lite either. > > You currently need speech-dispatcher to use eSpeak with Orca, and there are some instructions here: http://live.gnome.org/Orca/SpeechDispatcher Gilles is working on a gnome-speech driver for eSpeak though which will be a more robust solution (until SD and Orca support matures anyway). We are currently evaluating whay technical solutions to use for the future so we are *very* interested in feedback about peoples user experiences. * What is the exact problem with Festival, the speed of speech of lack of responsiveness? * For those who have eSpeak working (which option did you use the experimental Orca support or the gnome-speech->SD bridge?) -- how is it working? Any issues? * When we have the gnome-speech eSpeak driver working how does that compare with the other setups? etc. Henrik -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
gnome-terminal crash in Feisty
Hi. I am having a strange problem using gnome-terminal in Feisty. Gnome-terminal crashes with no error dialog. Then it crashes, all terminal sessions close. The crash is random, but it seems to happen when I use a Orca review key. Gnome-terminal is at version 2.16.1-0ubuntu1 Libvte9 is at version 1:0.15.0-0ubuntu1 The only other information I can provide is my .xsession-errors file. If there's anything I can do to provide more information, please let me know and I'll do it. Thanks in advance. Kenny /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "kenny" /etc/gdm/Xsession: Beginning session setup... Xlib: extension "XEVIE" missing on display ":0.0". Bonobo accessibility support initialized GTK Accessibility Module initialized SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 GTK Accessibility Module initialized ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized GTK Accessibility Module initialized Bonobo accessibility support initialized GTK Accessibility Module initialized Bonobo accessibility support initialized Initializing gnome-mount extension GTK Accessibility Module initialized Bonobo accessibility support initialized ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 GTK Accessibility Module initialized Bonobo accessibility support initialized evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 1168248013 evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 GTK Accessibility Module initialized ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -3 and height 24 anykey anykey anykey anykey anykey anykey ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray icon, because the CUPS server could not be contacted. anykey anykey anykey anykey GTK Accessibility Module initialized Bonobo accessibility support initialized anykey anykey anykey anykey anykey Window manager warning: Log level 8: atk_relation_set_get_n_relations: assertion `ATK_IS_RELATION_SET (set)' failed anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey (gnome-terminal:5383): Vte-WARNING **: No handler for control sequence `device-control-string' defined. anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anykey anyke
Re: gnome-terminal crash in Feisty
I think that a stack trace for gnome-terminal process will be necessary. Padraig Kenny Hitt wrote: > Hi. > > I am having a strange problem using gnome-terminal in Feisty. > Gnome-terminal crashes with no error dialog. Then it crashes, all > terminal sessions close. The crash is random, but it seems to happen > when I use a Orca review key. > > Gnome-terminal is at version 2.16.1-0ubuntu1 > Libvte9 is at version 1:0.15.0-0ubuntu1 > > The only other information I can provide is my .xsession-errors file. > If there's anything I can do to provide more information, please let me > know and I'll do it. > > Thanks in advance. > Kenny > > > > > /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp > /etc/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w > /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" > "kenny" > /etc/gdm/Xsession: Beginning session setup... > Xlib: extension "XEVIE" missing on display ":0.0". > Bonobo accessibility support initialized > GTK Accessibility Module initialized > SESSION_MANAGER=local/spot:/tmp/.ICE-unix/4838 > GTK Accessibility Module initialized > > ** (gnome-session:4838): WARNING **: Host name lookup failure on localhost. > GTK Accessibility Module initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > Bonobo accessibility support initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > GTK Accessibility Module initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > GTK Accessibility Module initialized > Bonobo accessibility support initialized > Initializing gnome-mount extension > GTK Accessibility Module initialized > Bonobo accessibility support initialized > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > > ** (gnome-cups-icon:4964): WARNING **: IPP request failed with status 1280 > GTK Accessibility Module initialized > Bonobo accessibility support initialized > evolution-alarm-notify-Message: Setting timeout for 52787 1168300800 > 1168248013 > evolution-alarm-notify-Message: Mon Jan 8 18:00:00 2007 > > evolution-alarm-notify-Message: Mon Jan 8 03:20:13 2007 > > GTK Accessibility Module initialized > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > ** Message: drive = 0 > ** Message: volume = 0 > > (gnome-panel:4932): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to > allocate widget with width -3 and height 24 > anykey > anykey > anykey > anykey > anykey > anykey > > ** (gnome-cups-icon:4964): WARNING **: Could not start the printer tray icon, > because the CUPS server could not be contacted. > anykey > anykey > anykey > anykey > GTK Accessibility Module initialized > Bonobo accessibility support initialized > anykey > anykey > anykey > anykey > anykey > Window manager warning: Log level 8: atk_relation_set_get_n_relations: > assertion `ATK_IS_RELATION_SET (set)' failed > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > > (gnome-terminal:5383): Vte-WARNING **: No handler for control sequence > `device-control-string' defined. > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > anykey > a
Re: espeak and orca
I need this info ASAP also. Festival is driving me up a wall and is WAY too slow. So instructions on how to get espeak on Orca would be great. Also does anyone know where to find a binary of brlapi 4.1? I am having problems getting my Braille Lite 2000 to work and I know it's not brltty as I have been using it for years. It's not the braille Lite either. Thanks, Beth Koenig [EMAIL PROTECTED] On 12/15/06, mike coulombe <[EMAIL PROTECTED]> wrote: > Hi, has anyone gotten espeek to work with orca. > If so how do I go about doing this. > Mike. > X-Antivirus: avast! (VPS 0659-0, 12/15/2006), Outbound message > X-Antivirus-Status: Clean > > > -- > Ubuntu-accessibility mailing list > Ubuntu-accessibility@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility > -- Beth Koenig [EMAIL PROTECTED] Director of Deaf Blind Services Orange County Deaf Advocacy Center http://www.deafadvocacy.org/dbs Health, safety, and productivity are the cornerstones of independence. At the Orange County Deaf Advocacy Center we provide the training and services necessary for the deaf and disabled to achieve equally and independence in all areas of life. Orange County Deaf Advocacy Center Donate: https://www.networkforgood.org/donate/MakeDonation2.aspx?ORGID2=330806007&PcaItemId=400 -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
[Fwd: Announcing Orca v2.17.5]
FYI... --- Begin Message --- === * What is Orca? === Orca is a free, open source, flexible, and extensible screen reader that provides access to the graphical desktop via user-customizable combinations of speech, braille, and/or magnification. Orca development has been led by the Sun Microsystems, Inc., Accessibility Program Office via continued engagement with its end users and contributions from wonderful community members. The Orca 2.17.x series are designated for the GNOME 2.17.x releases, but should also work well on the GNOME 2.16.x releases. NOTE ON FIREFOX SUPPORT: we know many of you are anxiously awaiting compelling access to the web via Orca and Firefox. As of v2.17.5, the support is still under development and both the Orca and Firefox teams are working feverishly to get it there for Firefox 3. == * What's changed for Orca v2.17.5? == * Brand new script for Adobe Acrobat Reader from Joanie Diggs (Thanks Joanie!!!). NOTE: there are still some accessibility issues to be worked out with the team at Adobe, but this script helps provide some level of access to PDF documents via Reader. * Much more work on Gecko.py script for Firefox 3.0. There's still much more work to do in the Firefox 3.0 internals as well as the Gecko.py script. We're still working feverishly on it. * Update to outloud.py to add more voices and prevent crash when ViaVoice is used (thanks to community member Bart Bunting!!!) * Adjusted bleeding edge Orca code to work with bleeding edge BrlAPI code. We expect there to be one more change in BrlAPI 0.5.0 before it stabilizes, but it wasn't ready at the time of this release. * Work on bug 350233 (actually an RFE): New script for the Liferea application from community member Francisco Javier Dorado Martínez (thanks Javier!!!). * Work on bug 376517: Orca now speaks the unit of measure (pixels) after the left-margin and/or right-margin text attributes if they differ from the norm. * Work on bug 347124: Added feature to allow user to tell gksu to disable keyboard grabs. This is just one of the several pieces of the puzzle to help prevent hangs when launching sysadmin apps from the desktop of a non-root user. * Fix for bug 393074: Repeated characters are now correctly read. (Thanks to Juan Ramon Jimenez for this fix!!!). * Fix for bug 362546: Fixed problem speaking status bar contents (Insert+KP_Enter) when the status bar is a single component (e.g., text field), rather than a container with multiple sub-components. * Moved the keyboard layout to the first tab in the preferences dialog. * Fix for bug 388620: Fixed wording of "not not" string. * Fix for bug 388317: Prevent crash in Adobe Acrobat Reader (thanks Joanie!!!). * Fix for bug 387556: Make arrowing to end of line in OOo consistent with what happens in gedit (thanks Joanie!!!). * Fix for bug 388039: prevent stack trace when running orca -t. * Fix for bug 386267: In Evolution, Orca now speaks/brailles the unread status instead of the read status in the message summary list. * Fix for bug 382890: Extended dynamic row and column header support to OOo Writer tables. * New and updated translations (THANKS EVERYONE!!!): ar Arabic Djihed Afifi en_GB English/British David Lodge es Spanish Francisco Javier F. Serrador nb Norwegian Bokmål Kjartan Maraas sv Swedish Daniel Nylander = * Where can I get it? = You can obtain Orca v2.17.5 in source code form at the following URL: http://ftp.gnome.org/pub/gnome/sources/orca/2.17/orca-2.17.5.tar.bz2 http://ftp.gnome.org/pub/gnome/sources/orca/2.17/orca-2.17.5.tar.gz >From the Sun Microsystems, Inc., Accessibility Program Office, Willie Walker, Project Lead Mike Pedersen, User Interface Design Rich Burridge, Core Development and Scripting Lynn Monsanto, Core Development and Java Platform Support Michele Budris, Program Management ___ gnome-announce-list mailing list gnome-announce-list@gnome.org http://mail.gnome.org/mailman/listinfo/gnome-announce-list --- End Message --- -- Ubuntu-accessibility mailing list Ubuntu-accessibility@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-accessibility
