ANNOUNCE: atk 1.28.0
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
ANNOUNCE: atk 1.28.0
by Ke Wang-2
::
Rate this Message:
=======================
* What is atk? ======================= The interface definitions of accessibility infrastructure. ======================================== * What's changed for atk 1.28.0? ======================================== Translation update: Bulgarian, Brazilian Portuguese, Serbian. ===================== * Where can I get it? ===================== Source code: http://ftp.acc.umu.se/pub/GNOME/sources/atk/1.28/atk-1.28.0.tar.gz http://ftp.acc.umu.se/pub/GNOME/sources/atk/1.28/atk-1.28.0.tar.bz2 Enjoy! Ke _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@... http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list |
|
|
at-spi-registryd and Xephyr
by sbq
::
Rate this Message:
Greetings,
I am running an application that uses a Xephyr window as its X Display. (See http://labs.o-hand.com/xephyr/ or http://packages.debian.org/sid/xserver-xephyr). When I run my at-spi client, it immediately reports: ** (process:16785): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (process:16785): WARNING **: Could not locate registry (process:16785): Bonobo-CRITICAL **: bonobo_unknown_ping: assertion `object != NULL' failed ** (process:16785): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (process:16785): WARNING **: Could not locate registry Warning: AT-SPI error: pre method check: add: Unknown CORBA exception id: 'IDL:omg.org/CORBA/INV_OBJREF:1.0' (process:16785): Bonobo-CRITICAL **: bonobo_unknown_ping: assertion `object != NULL' failed ... and eventually crashes. I can see that at-spi-registryd is running: > ps aux | grep -i registry user 3176 0.0 0.8 14512 4336 ? S Sep23 0:19 /usr/lib/at-spi/at-spi-registryd Is the at-spi-registryd connected/related to an X Display? Or to the window manager? Is there a known way to make this work? Thanks. -Sam PS: if it matters, the Xephyr window is using a custom window manager (not Xfwm4, not Metacity). _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@... http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list |
|
|
Re: at-spi-registryd and Xephyr
by Nagappan
::
Rate this Message:
Hi Sam,
I think Guofu Xu (lavi) did some work around for custom window manager during his automation effort using LDTP and its working. Probably you can check with him :) Thanks Nagappan
On Fri, Sep 25, 2009 at 2:12 PM, Quiring, Sam <Sam.Quiring@...> wrote: Greetings, -- Linux Desktop (GUI Application) Testing Project - http://ldtp.freedesktop.org http://nagappanal.blogspot.com _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@... http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list |
|
|
Re: at-spi-registryd and Xephyr
by Piñeiro
::
Rate this Message:
From: "Quiring, Sam" <Sam.Quiring@...>
> I can see that at-spi-registryd is running: > > > ps aux | grep -i registry > user 3176 0.0 0.8 14512 4336 ? S Sep23 0:19 > /usr/lib/at-spi/at-spi-registryd > > > Is the at-spi-registryd connected/related to an X Display? Or to the > window manager? AFAIK, the at-spi-registryd is related to the specific X Display, so try to execute the at-spi-registryd using your specific DISPLAY. Probably this at-spi-registry that you are using is your desktop one, and using the default DISPLAY. Ie: working with Maemo (HAIL), and the scratchbox, I usually run the Xephyr display in this way: Xephyr :2 <a lot of other options> And then, inside the scratchbox terminal, I have defined the display as: export DISPLAY=:2 Then I launch by hand a script to launch the window manager and so on. And about the window manager, if you want that the at-spi-registryd manages this process as well, you need to be sure to run the at-spi-registryd before the WM (in this script it launch the at-spi-registryd before the WM). > Is there a known way to make this work? I hope this helps. > PS: if it matters, the Xephyr window is using a custom window manager > (not Xfwm4, not Metacity). In theory, this shouldn't be a issue. === API (apinheiro@...) _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@... http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list |
|
|
RE: at-spi-registryd and Xephyr
by sbq
::
Rate this Message:
Mr. Pinheiro,
Thank you for the reply, I am hoping to utilize your Clutter accessibility work soon. I rebooted my computer (VMware) and am getting different results than I initially reported. When I run my at-spi client I no longer get any errors. It reports 15 apps. When I run my Python app connected to Xephyr, I see this: (progname:15364): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup. (progname:15364): atk-bridge-WARNING **: IOR not set. (progname:15364): atk-bridge-WARNING **: Could not locate registry I read the code for atk-bridge. It prints the above errors after trying and failing to retrieve an atom, "AT_SPI_IOR" from the X display. The app's X display is Xephyr (:1.0). When at-spi-registryd started during Ubuntu boot, its X display was the console (:0.0), so the "AT_SPI_IOR" atom it defined (and that atk-bridge is looking for) is in a different X display. This explains the error messages. So I did pretty much what you suggested, I started Xephyr Xehpyr :1 <stuff> I define DISPLAY to :1.0 and started at-spi-registryd, which starts but silently dies. I think it discovers the already-running registryd and says "there can be only one" and dies. Obviously I could be wrong here. So I killed the running at-spi-registryd, started xephyr, set DISPLAY to :1.0, started at-spi-registryd, and finally started the app. Then ran my at-spi client. This works. Am I correct that you can only have one at-spi-registryd running? -Sam -----Original Message----- From: Piñeiro [mailto:apinheiro@...] Sent: Monday, September 28, 2009 2:49 AM To: Quiring, Sam Cc: gnome-accessibility-list@... Subject: Re: at-spi-registryd and Xephyr From: "Quiring, Sam" <Sam.Quiring@...> > I can see that at-spi-registryd is running: > > > ps aux | grep -i registry > user 3176 0.0 0.8 14512 4336 ? S Sep23 0:19 > /usr/lib/at-spi/at-spi-registryd > > > Is the at-spi-registryd connected/related to an X Display? Or to the > window manager? AFAIK, the at-spi-registryd is related to the specific X Display, so try to execute the at-spi-registryd using your specific DISPLAY. Probably this at-spi-registry that you are using is your desktop one, and using the default DISPLAY. Ie: working with Maemo (HAIL), and the scratchbox, I usually run the Xephyr display in this way: Xephyr :2 <a lot of other options> And then, inside the scratchbox terminal, I have defined the display as: export DISPLAY=:2 Then I launch by hand a script to launch the window manager and so on. And about the window manager, if you want that the at-spi-registryd manages this process as well, you need to be sure to run the at-spi-registryd before the WM (in this script it launch the at-spi-registryd before the WM). > Is there a known way to make this work? I hope this helps. > PS: if it matters, the Xephyr window is using a custom window manager > (not Xfwm4, not Metacity). In theory, this shouldn't be a issue. === API (apinheiro@...) _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@... http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list |
|
|
Re: RE: at-spi-registryd and Xephyr
by Ariel Rios-2
::
Rate this Message:
Yes that's true. Only one registry can run at a time. Ariel El 28 de sep de 2009, 10:45 a.m., "Quiring, Sam" <Sam.Quiring@...> escribió: _______________________________________________ gnome-accessibility-list mailing list gnome-accessibility-list@... http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list |
| Free embeddable forum powered by Nabble | Forum Help |
