After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 143518 - Speech is partially working within the content application or web page
Speech is partially working within the content application or web page
Status: RESOLVED DUPLICATE of bug 154246
Product: gnopernicus
Classification: Deprecated
Component: speech
unspecified
Other Linux
: Normal major
: ---
Assigned To: mp
mp
Depends on:
Blocks:
 
 
Reported: 2004-06-01 16:29 UTC by tvuong
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description tvuong 2004-06-01 16:29:04 UTC
Speech is not fully working within the application/web beyond the menu and tool 
bars ...

Steps:
1. Bring up Gnopernicus
2. Enable Speech only
3. Open up any applications (i.e. Mozilla or open office)
4. Keyboard Nav, do <alt f>
5. Listen for speech, then once done annoucning, hit <ESC> to get out
6. Begin to <tab> down to content of the page or data
7. Listen for speech 

Speech is only working partially and not fully working with all contents within 
the page or application.
Comment 1 remus draica 2004-06-15 09:44:34 UTC
This bug is too general. Please specify a scenario where gnopernicus fails to
work. Also check if the other app is accessible, specially if the curent object
is. For this you can use at-poke application. Also you can check if that
application fires events. For that you have to set GNOPERNICUS_LOG environment
variable to at-spi (export GNOPERNICUS_LOG=at-spi).
If you will not get any event, then this is not a gnopernicus bug.
Comment 2 tvuong 2004-06-15 18:24:44 UTC
1. "Please specify a scenario where gnopernicus fails to work."

PLease see above steps in orginal msg to reproduce.

2. "Also check if the other app is accessible,"

 Please see detail above original msg. Other apps have the same problem (tested 
with Mozilla and OpenOffice applications, etc.).

3. GNOPERNICUS_LOG wise, if you want a stack trace or coredump trace, please 
let me know. I can try to capture that for you, since I'm not too familiar with 
what you recomend me to do in your comment #1. If you still want me to provide 
what you're asking, please let me know in Detail how to obtain this info for 
you.
Comment 3 remus draica 2004-06-16 07:35:44 UTC
On my computer, the bug cannot be reproduced. That's why I asked you about a
more specific scenario.

I'm trying to see if this is a gnopernicus bug, a gnome-speech bug or an app
bug. If events are still coming to gnopernicus (this can be checked by exporting
GNOIPERNICUS_LOG and viewing in the terminal from where gnopernicus was started
a feedback for all your actions) this is not an app bug. If gnopernicus send a
text to speech and that text is not spoken, then this is a gnome-speech bug.
This can be checked by turning on braille monitor and looking if it reflects
your actions in same scenarios where it did.

So, please turn on braille monitor and check if it is still working for you.
Usually if gnopernicus sends something to speech, it sends to braille monitor
too, specially for focus tracking.
Comment 4 tvuong 2004-06-16 15:42:12 UTC
Thanks for the info.
I did turn on braille monitor and using the procedure/steps above to reproduce. 
Braille monitor stops showing current msg (as soon as gnopernicus speech quits 
working), while I gracefully <TABs> thru application page.

Speech is only working partially and not fully working within the content of
the page or application. For those non-working items, when speech is not 
working, braille monitor only show last working text, not current one.

Comment 5 Dana Ormenisan 2004-10-08 09:24:53 UTC
If both speech and brlmonitor stop working for some items and start working
again for another items (so this is not an srcore crash), the explanation is
that gnopernicus does not receive at-spi events for some objects. 
This is the same problem like the one described in bug #154246, comment #4. 
Comment 6 Dana Ormenisan 2004-10-08 09:25:28 UTC

*** This bug has been marked as a duplicate of 154246 ***