Bug 481824 - Wrong application name propagated to at-spi2 registry
Summary: Wrong application name propagated to at-spi2 registry
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.5.1   Edit
Hardware: PC Linux
: P2 major (vote)
Target Milestone: 4.8   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: accessibility
Depends on:
Blocks:
 
Reported: 2015-11-10 06:11 EST by Jann Schneider CLA
Modified: 2017-11-14 11:55 EST (History)
8 users (show)

See Also:


Attachments
python script to get the accessible names from the at-spi2 registry including the cmd-line (449 bytes, text/x-python)
2015-11-10 06:11 EST, Jann Schneider CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jann Schneider CLA 2015-11-10 06:11:23 EST
Created attachment 257846 [details]
python script to get the accessible names from the at-spi2 registry including the cmd-line

Due to Bug 470031 i am running Eclipse forcing GTK2. Not sure if this makes a difference for this issue but i just wanted to mention it, too. 
When eclipse is running it looks like it is propagating a wrong application name to the at-spi2 registry: orca is reading the application title from the at-spi2 registry and reads "SWT" instead of "Eclipse" as window / application name. This is causing some accessibility issues. For example: orca is no longer able to load the proper scripts for eclipse etc.. 

You could use the attached python script to get the accessible names from the at-spi2 registry. Also you could simply use accerciser for this purpose.
Comment 1 jose vilmar estacio de souza CLA 2015-11-10 07:35:33 EST
In my environment the name eclipse is shown correctly but the attached script shows two instances of eclipse when I execute eclipse 4.5.
The instance  is shown by the script as a dead app and the script takes about 15 seconds to complete in my machine.
Comment 2 jose vilmar estacio de souza CLA 2015-11-10 07:57:56 EST
The problem described in my previous comment happens if I force GTK2 or GTK3.
Actually I am using gnome 3.18 in a arch box.
Comment 3 jose vilmar estacio de souza CLA 2015-11-10 12:39:56 EST
(In reply to jose vilmar estacio de souza from comment #2)
> The problem described in my previous comment happens if I force GTK2 or GTK3.
> Actually I am using gnome 3.18 in a arch box.

And it only happens if I run eclipse 4.5. I didn't see this problem with previous versions of eclipse.
Comment 4 Dani Megert CLA 2016-04-27 08:01:44 EDT
Alex, is that the bug you said you'll take a look?
Comment 5 Alexander Kurtakov CLA 2016-04-27 08:05:39 EDT
Yes, I'm looking into it (as much as time permits).
Comment 6 Arun Thondapu CLA 2016-05-17 05:56:57 EDT
(In reply to Alexander Kurtakov from comment #5)
> Yes, I'm looking into it (as much as time permits).

Alex, I'm deferring to 4.6.1, please re-target in case you think otherwise...
Comment 7 Alexander Kurtakov CLA 2016-05-17 05:58:09 EDT
That's fine I spent a lot of time on this one but can't figure it out yet.
Comment 8 Arun Thondapu CLA 2016-08-29 02:51:18 EDT
Moving to 4.6.2 as there is no fix yet...
Comment 9 Arun Thondapu CLA 2016-11-21 02:52:15 EST
Moving to 4.7, fix can be backported to 4.6.3 if possible.
Comment 10 Arun Thondapu CLA 2017-05-17 13:24:39 EDT
No fix in 4.7 either, deferring to 4.7.1 now.
Comment 11 Eric Williams CLA 2017-08-09 12:55:11 EDT
I'm not sure I can reproduce this issue. Can anyone else confirm?

When running the script, here is the output:

12:42:13   pid:  6315  [application | Eclipse]

This is with Eclipse in GTK3 mode. There is a noticeable hang though. The script takes about 10-20 seconds to read the Eclipse application info, before terminating.

OS details:
Fedora 26 with GTK3.22
Eclipse 4.7
Comment 12 Eric Williams CLA 2017-08-10 16:01:16 EDT
It's worth noting that Accerciser does *not* work with Eclipse at all (whether it be GTK2 or 3). It hangs for awhile and then prints the following message into the command line:

** (accerciser:16298): WARNING **: AT-SPI: Error in GetItems, sender=(null), error=Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Comment 13 Eric Williams CLA 2017-11-14 11:44:31 EST
After the fixes to bug 470031, both GTK2 and GTK3 report the correct application name to the at-spi2 registry. Running the attached script no longer reproduces this bug.

Marking this as WORKSFORME since there is no actual fix for this bug, it's all part of the work for bug 470031.
Comment 14 Carolyn MacLeod CLA 2017-11-14 11:55:58 EST
Nice work, Eric! Thanks!