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 154487 - accessibility doesn't support apps run with ssh -[XY]
accessibility doesn't support apps run with ssh -[XY]
Status: RESOLVED DUPLICATE of bug 163132
Product: at-spi
Classification: Platform
Component: registry
0.0.1
Other Linux
: Normal enhancement
: ---
Assigned To: bill.haneman
bill.haneman
Depends on:
Blocks:
 
 
Reported: 2004-10-04 18:19 UTC by Zack Cerza
Modified: 2006-06-27 17:14 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Zack Cerza 2004-10-04 18:19:15 UTC
If your ssh client doesn't implement -Y, s/Y/X/ .
This isn't specific to gedit. It affects all GNOME apps that I've tested.

user@host1 $ gconftool-2 --type bool --set
/desktop/gnome/interface/accessibility true
user@host2 $ ssh -Y host1
user@host2 $ gedit
Bonobo accessibility support initialized
GTK Accessibility Module initialized
X11 connection rejected because of wrong authentication.

** ERROR **: Accessibility app error: exception during registry activation from
id: IDL:Bonobo/GeneralError:1.0

aborting...

(Loops continuously, with a ~1s delay after each loop.)

Versions of stuff (this is an amd64, hence the atk dupe):
$ rpm -q atk at-spi libgail-gnome
atk-1.8.0-1
atk-1.8.0-1
at-spi-1.6.0-3
libgail-gnome-1.1.0-1
Comment 1 Zack Cerza 2004-10-04 18:20:46 UTC
Ah, forgot to mention: it doesn't make a difference if accessibility is enabled
or not on host2.
Comment 2 bill.haneman 2004-10-05 16:07:01 UTC
sorry Zack, I don't quite understand the report.
Comment 3 Zack Cerza 2004-10-18 19:31:34 UTC
This involves two computers (I call them host1 and host2). host1 should have
accessibility turned on. Whether it's on or not on host2 doesn't matter. 

I can most reliably reproduce this when the part of host1 is being played by my
dual-Opteron workstation. I haven't figured out if it's amd64 (or generic
64-bit) specific.

Here is how to reproduce:
From host2, ssh -Y (or ssh -X if you're using an older version of ssh) to host1.
In the ssh session, run any GNOME app. gedit was the example I gave, but any
will do. 

The result is the error message shown in the original report. It loops forever.
The GIMP works fine, because it is not accessible.

I hope this is a little bit more clear :/
Comment 4 Calum Benson 2004-10-21 16:44:03 UTC
Apologies for spam-- ensuring Sun a11y team are cc'ed on all current a11y bugs.
 Filter on "SUN A11Y SPAM" to ignore.
Comment 5 Calum Benson 2006-04-26 17:05:32 UTC
Apologies for spam... ensuring Sun a11y folks are cc'ed on all current accessibility bugs.
Comment 6 bill.haneman 2006-06-23 16:51:36 UTC
Hmm, I think this is a dup of 163132, since the issue is that the app is connecting to a user/host-based at-spi-registryd instead of using one associated with the local DISPLAY.

*** This bug has been marked as a duplicate of 163162 ***
Comment 7 Morten Welinder 2006-06-26 13:36:15 UTC
This might be a duplicate, but surely not of bug 163162.

--> Reopening.
Comment 8 bill.haneman 2006-06-27 17:14:34 UTC

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