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 582479 - Doubling of items when reading messages in Evolution
Doubling of items when reading messages in Evolution
Status: RESOLVED INCOMPLETE
Product: orca
Classification: Applications
Component: speech
2.27.x
Other Linux
: Normal normal
: 2.28.0
Assigned To: Joanmarie Diggs (IRC: joanie)
Orca Maintainers
Depends on:
Blocks: 423346
 
 
Reported: 2009-05-13 15:31 UTC by Nolan Darilek
Modified: 2009-08-20 03:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Debug log (43.81 KB, text/plain)
2009-05-13 15:33 UTC, Nolan Darilek
Details

Description Nolan Darilek 2009-05-13 15:31:02 UTC
When reading messages in Evolution line-by-line (or even char-by-char I think) Orca reads each item twice.

In looking at the attached log it would appear that moving via arrows generates both a caret move and focus change, and Orca processes both by reading the destination of the move. Just a guess.
Comment 1 Nolan Darilek 2009-05-13 15:33:49 UTC
Created attachment 134574 [details]
Debug log
Comment 2 Mike Pedersen 2009-05-13 15:48:09 UTC
I've seen this very occasionally but on my opensolaris system it is not at all reproducible for me.  I don't even get the same result with the same message from session to session.  I find if I close and re-open evo when this happens the problem goes away.  
  
 
Comment 3 Willie Walker 2009-05-17 18:18:08 UTC
I tested this on Ubuntu 9.04 with Orca 2.26.1 and Evolution 2.26.1.  I cannotg reproduce the problem.  Does this problem always happen for you, or is it an intermittent problem?  Please also let us know the OS distribution and version you are using as well as the Evolution and Orca versions.
Comment 4 Nolan Darilek 2009-05-25 15:38:08 UTC
It's intermittent, and unfortunately I can't really pin down a series of circumstances that trigger it. I'm using Ubuntu 9.04, Orca head and Evolution 2.26.1.
Comment 5 Joanmarie Diggs (IRC: joanie) 2009-07-31 15:48:09 UTC
I've not been able to reproduce this (yet). But I'll take a look.
Comment 6 Joanmarie Diggs (IRC: joanie) 2009-07-31 22:36:22 UTC
(In reply to comment #0)
> When reading messages in Evolution line-by-line (or even char-by-char I think)
> Orca reads each item twice.
> 
> In looking at the attached log it would appear that moving via arrows generates
> both a caret move and focus change, and Orca processes both by reading the
> destination of the move. Just a guess.
> 
And an excellent one at that. Looking at your debug.out, that seems to be exactly what's going on. Nice work!

I've tried some more to reproduce this issue, in particular:

1. HTML text versus plain text messages

2. Reading the messages in a dedicated window versus reading them in the preview pane

3. Evolution 2.26.2 (OpenSolaris) versus Evolution 2.27.4.1 (Ubuntu)

I still cannot reproduce it. I even looked through each and every debug.out (I did one test at a time) to see if Orca was perhaps repeating the text but I wasn't hearing repetitions (which in theory might could happen if the events came quickly enough with the second event cutting off the speech that would have resulted from the first event). Orca is most definitely not repeating the text.

So.... Maybe we fixed the bug without knowing it? Maybe it was something weird in Evo 2.26.1 that no longer exists?

Nolan, are you still seeing this?
Comment 7 Joanmarie Diggs (IRC: joanie) 2009-08-14 23:02:44 UTC
Nolan: Ping. :-) Thanks!
Comment 8 Nolan Darilek 2009-08-19 13:43:02 UTC
Apologies. Crazy week, and I'm no longer using Evo as my mail client.

But, yes, under 2.26.1, I still saw the behavior, on the very first message I tried no less. Maybe it's a 2.26.1 issue, since it doesn't appear as if that version was checked.
Comment 9 Joanmarie Diggs (IRC: joanie) 2009-08-20 03:58:59 UTC
Thanks Nolan. Given that:

1. You are no longer using Evo

2. No one else (to my knowledge) is experiencing this issue

3. The version you indicate had the problem is obsolete (both in the stable and unstable Evo releases)

4. I cannot reproduce this issue in the current Evo's

I'm going to close this out as INCOMPLETE. If the issue reappears in a current version of Evo, then we can re-open this bug.