GNOME Bugzilla – Bug 483352
[blocked] New e-mail in Evolution can cause Orca to become unresponsive for a period of time
Last modified: 2012-08-14 21:23:31 UTC
From the orca-list http://mail.gnome.org/archives/orca-list/2007-October/msg00018.html: "When typing a new message, if a new e-mail arrives in my inbox orca stops echoing words (I only have echo words on, not echo key presses), and does not start to again until I alt-tab focus away and back. The set up: orca from svn trunk (although I have noticed this for quite a time, its not really new), evolution 2.10 with view set to not show preview pane and not to hide deleted messages (I think those might be the most important settings in evolution relating to this), gnome 2.18.3 (on a slackware system, gnome being from the slacky project http://www.slacky.eu)."
I can reproduce this in Gutsy with the latest everything. What seems to be happening in this: 1. We get a focus event for the message list in the frame that doesn't have focus. 2. Somehow in the process, the text object loses STATE_FOCUSED. Here's before the new message comes in: -------------------------------------- OBJECT EVENT: object:text-changed:insert detail=(20,1) app.name='evolution' name=None role='text' state='EDITABLE ENABLED FOCUSABLE FOCUSED MULTI_LINE SENSITIVE SHOWING VISIBLE' relations='' -------------------------------------- And after: -------------------------------------- OBJECT EVENT: object:text-changed:insert detail=(21,1) app.name='evolution' name=None role='text' state='EDITABLE ENABLED FOCUSABLE MULTI_LINE SENSITIVE SHOWING VISIBLE' relations='' -------------------------------------- Looks like YAEB.
Filed bug 483452 against Evolution. We're blocked.
Just reassigning to Joanie so she can track the progress on the blocking bug.
Note that this is responsible for 2/3 of the problem in bug #582491. Rather than keep multiple bugs open to track a bug against Evo which was filed in October 2007 and which has not yet been triaged, I'm just going to reference that bug here.
*** This bug has been marked as a duplicate of bug 483452 ***