Bug 345721 – Press Number key, will cause orca hang when try to read the mail in Evolution.

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 345721 - Press Number key, will cause orca hang when try to read the mail in Evolution.


Summary:	Press Number key, will cause orca hang when try to read the mail in Evolution.


Status:	RESOLVED FIXED

Product:	orca
Classification:	Applications
Component:	speech
Version:	0.2.x
Hardware:	Other All

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Rich Burridge
QA Contact:	Orca Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-06-23 07:09 UTC by Emily chen
Modified:	2015-12-21 21:30 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Fix to dramatically improve the situation, nay dare I even say, fix the problem. (556 bytes, patch) 2006-06-28 20:07 UTC, Rich Burridge	none	Details \| Review
Traceback with latest master. (2.99 KB, text/plain) 2015-07-28 22:32 UTC, Mike Gorse		Details

Description Emily chen 2006-06-23 07:09:26 UTC

Please describe the problem:
Press Number key, will cause orca hang when try to read the mail in Evolution. 

Steps to reproduce:
1. Start Orca;
2. Start Evolution;
3. Go to one mail, focus on the mail body;
4. Press Number key, for example, Press 6 in the Number keyboard


Actual results:
Orca will hang and aslo evolution will hang. 

Expected results:
Orca will read out the mail word by word. 

Does this happen every time?
yes

Other information:
Not only happened in Evolution. Another application like Gaim, when focus on the conversation message, press number key, orca will hang. After kill orca, then all the application work well.

Comment 1 Rich Burridge 2006-06-28 19:43:20 UTC

I couldn't get this to hang, but I did get it to cause a traceback
everytime I hit the 6 on the numeric keypad:

Traceback (most recent call last):

+ Trace 69105

File "/usr/lib/python2.4/site-packages/orca/input_event.py", line 172 in processInputEvent
```
consumed = self._function(script, inputEvent)
```
File "/usr/lib/python2.4/site-packages/orca/default.py", line 2516 in reviewNextItem
```
context = self.getFlatReviewContext()
```
File "/usr/lib/python2.4/site-packages/orca/default.py", line 2070 in getFlatReviewContext
```
lines = self.clusterZonesByLine(self.getShowingZones())
```
File "/usr/lib/python2.4/site-packages/orca/default.py", line 1902 in getShowingZones
```
return flat_review.getShowingZones(obj)
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1414 in getShowingZones
```
objlist.extend(getShowingZones(child))
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1368 in getShowingZones
```
return getZonesFromAccessible(root, root.extents)
```
File "/usr/lib/python2.4/site-packages/orca/flat_review.py", line 1071 in getZonesFromAccessible
```
extents = accessible.component.getExtents(0)
```

AttributeError: 'NoneType' object has no attribute 'getExtents'


Investigating further...

Comment 2 Mike Pedersen 2006-06-28 19:55:11 UTC

We have many places in evolution where flat review doesn't work.  You can almost always have this problem while trying to flat review the inbox at any place as well.

Comment 3 Rich Burridge 2006-06-28 19:58:22 UTC

    The Evolution accessible object with a component field of None
    is the Status table column header in the mail message summary table:

    gZFA: accessible:  <orca.atspi.Accessible instance at 0x87b9c0c>
    gZFA: object role:  table column header
    gZFA: name:  Status
    gZFA: component:  None
    +-name='evolution-2.6' role='application' state=''
      +-name='Evolution - INBOX (12 total, 4 unread)' role='frame' state='ACTIVE
    ENABLED RESIZABLE SENSITIVE SHOWING VISIBLE'
        +-name=None role='filler' state='ENABLED SENSITIVE SHOWING VERTICAL
    VISIBLE'      +-name=None role='panel' state='ENABLED SENSITIVE SHOWING
    VISIBLE'
            +-name=None role='filler' state='ENABLED SENSITIVE SHOWING VERTICAL
    VISIBLE'
              +-name=None role='split pane' state='ENABLED FOCUSABLE HORIZONTAL
    SENSITIVE SHOWING VISIBLE'
                +-name=None role='page tab list' state='ENABLED SENSITIVE SHOWING
    VISIBLE'
                  +-name=None role='page tab' state='ENABLED SELECTABLE SELECTED
    SHOWING VISIBLE'
                    +-name=None role='panel' state='ENABLED SENSITIVE SHOWING
    VISIBLE'
                      +-name=None role='panel' state='ENABLED RESIZABLE SENSITIVE
    SHOWING VISIBLE'
                        +-name=None role='filler' state='ENABLED SENSITIVE SHOWING
    VERTICAL VISIBLE'
                          +-name=None role='split pane' state='ENABLED FOCUSABLE
    SENSITIVE SHOWING VERTICAL VISIBLE'
                            +-name=None role='scroll pane' state='ENABLED FOCUSABLE
    SENSITIVE SHOWING VISIBLE'
                              +-name='Messages' role='unknown' state='ENABLED
    FOCUSABLE SENSITIVE SHOWING VISIBLE'
                                +-name='Messages' role='tree table' state='ENABLED
    SENSITIVE SHOWING TRANSIENT VISIBLE'
                                  +-name='Status' role='table column header'
    state='ENABLED SENSITIVE SHOWING VISIBLE'


    From looking at the component hierarchy with at-poke, I can see that
    none of the column headers in this table have a component value. This
    seems like an Evolution bug to me.

    Having said that, we should probably bullet-proof it a little better in
    Orca.

Comment 4 Rich Burridge 2006-06-28 20:07:47 UTC

Created attachment 68131 [details] [review]
Fix to dramatically improve the situation, nay dare I even say, fix the problem.

With the attached two line change flat review seems to work nicely now.
I don't think it'll be able to traverse accessible objects with their
component field set to None (and we should probably file an Evolution 
bug on that), but it sure make Orca a lot more useable.

Will, what ya think?

Comment 5 Rich Burridge 2006-06-30 21:13:01 UTC

After talking with Will, I've checked in this change.
I'm leaving the bug report open for now, to see if there
is anything else we need to do.

Comment 6 Rich Burridge 2006-07-17 18:44:28 UTC

Mike, is this problem still occuring for you?

Comment 7 Mike Pedersen 2006-07-17 19:55:31 UTC

The patch has solved the problem.  We should however still file the evolution bug.

Comment 8 Rich Burridge 2006-07-17 21:40:27 UTC

Evolution bug #347846 has been created. Closing this bug as FIXED.

Comment 9 Mike Gorse 2015-07-28 22:31:12 UTC

I'm seeing this bug again. Will attach a traceback. Also submitted a patch for the evolution bug.

Comment 10 Mike Gorse 2015-07-28 22:32:23 UTC

Created attachment 308345 [details]
Traceback with latest master.

Comment 11 Joanmarie Diggs (IRC: joanie) 2015-07-28 22:34:13 UTC

Thanks Mike.

Comment 12 Mike Gorse 2015-08-14 18:33:57 UTC

The underlying evolution bug is fixed now in master.