This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Re: About dogtail on x86 and ppc64
- From: Wu Zhou <woodzltc at cn dot ibm dot com>
- To: Zack Cerza <zcerza at redhat dot com>
- Cc: Elena Zannoni <ezannoni at redhat dot com>, ldimaggi at redhat dot com, frysk at sources dot redhat dot com
- Date: Sun, 23 Jul 2006 07:50:58 -0400
- Subject: Re: About dogtail on x86 and ppc64
Hi Zack,
Thanks for your reply. See below for the answers.
Wu Zhou writes:
> Hello all,
> > We can setup dogtail on x86 and ppc64 as well.
> > On both platform, we run "python ./gedit-test-utf8-procedural-api.py".
> > Here is the results:
> > On x86:
> ========
> # python ./gedit-test-utf8-procedural-api.py
> Creating logfile at >
/tmp/dogtail/logs/gedit-test-utf8-procedural-api_20060712-093635 ...
> Detecting distribution: Red Hat/Fedora/derived distribution
> Warning: AT-SPI error: pre method check: add: Unknown CORBA
exception > id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
> GTK Accessibility Module initialized
> Warning: AT-SPI error: pre method check: add: Unknown CORBA
exception > id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
> Bonobo accessibility support initialized
> Warning: AT-SPI error: pre method check: add: Unknown CORBA
exception > id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
> Warning: AT-SPI error: pre method check: add: Unknown CORBA
exception > id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
> Warning: AT-SPI error: pre method check: add: Unknown CORBA
exception > id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
I haven't seen those warnings so soon in a script. Can you tell me if
the 'sniff' utility works?
Ys. The sniff utility did worked. It can list a tree with the root
being "main" and also some sub-nodes, such as gnome-panel,
gnome-terminal.
> /tmp/dogtail/screenshot_20060712-093640.png
> Screenshot taken: /tmp/dogtail/screenshot_20060712-093640.png
> click on {child with name="Save" ("?$A4f(B(S)",
"$A1#4f(B(S)", "$A1#4f(B", "?$A4f(B", )}
The above line doesn't look right at all. Can you paste the output of
the 'locale' command? I'm guessing your locale is breaking dogtail's
automatic runtime translation.
the locale output is like this:
LANG=zh_CN.UTF-8
LC_CTYPE="zh_CN.UTF-8"
LC_NUMERIC="zh_CN.UTF-8"
LC_TIME="zh_CN.UTF-8"
LC_COLLATE="zh_CN.UTF-8"
LC_MONETARY="zh_CN.UTF-8"
LC_MESSAGES="zh_CN.UTF-8"
LC_PAPER="zh_CN.UTF-8"
LC_NAME="zh_CN.UTF-8"
LC_ADDRESS="zh_CN.UTF-8"
LC_TELEPHONE="zh_CN.UTF-8"
LC_MEASUREMENT="zh_CN.UTF-8"
LC_IDENTIFICATION="zh_CN.UTF-8"
LC_ALL=
> Traceback (most recent call last):
> File "./gedit-test-utf8-procedural-api.py", line 56, in ?
> focus.dialog(u'Save As\u2026')
> File "/usr/lib/python2.4/site-packages/dogtail/procedural.py",
line > 78, in __call__
> result = FocusApplication.node.findChild(predicate, >
requireResult=False, recursive = False)
> File "/usr/lib/python2.4/site-packages/dogtail/tree.py", line
769, > in findChild
> result.debugName = pred.describeSearchResult()
> File "/usr/lib/python2.4/site-packages/dogtail/predicate.py",
line > 235, in describeSearchResult
> return '%s dialog'%self.dialogName
> File "/usr/lib/python2.4/site-packages/dogtail/i18n.py", line
144, > in __str__
> result = '"%s" (%s)' % (self.untranslatedString, translations)
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in
position > 8: ordinal not in range(128)
The above traceback is due to the fact that the runtime translation
isn't working properly.
Sorry, what kind of runtime translation did you mean here? the
translation from english to the language setup in the locale, or
anything else?
> On ppc64:
> ========
> # python ./gedit-test-utf8-procedural-api.py
> Creating logfile at >
/tmp/dogtail/logs/gedit-test-utf8-procedural-api_20060712-133632 ...
> Detecting distribution: Red Hat/Fedora/derived distribution
> /tmp/dogtail/screenshot_20060712-133637.png
> Screenshot taken: /tmp/dogtail/screenshot_20060712-133637.png
> click on {child with name="Save"}
> activate on {child with name="Browse for other folders"}
> activate on {child with name="Desktop" roleName='table cell'}
> click on {child with name="Save"}
> click on {child with name="Quit"}
> > ** (process:26377): WARNING **: Failed to send buffer
> > ** (process:26377): WARNING **: Failed to send buffer
> > ** (process:26377): WARNING **: Failed to send buffer
> > ** (process:26377): WARNING **: Failed to send buffer
> ......
> ** (process:26377): WARNING **: Failed to send buffer
The above warning messages are pretty benign, considering the script
has already run to completion. If you ever see them in the middle of a
script, I'd be worried.
That is ok. I will ignore them then. So dogtail seems to be largely
ok on ppc64, only if the environment be set up correctly. But
sometimes I just don't know what is the correct way to set up dogtail
environment. Is there any documents about that?
> The difference I noticed is:
> > 1. There are some warning messages there in ppc64
complaining that > failed to send buffer
The messages appear on all architectures, just not all the time.
Although it is harmless. I am still curious about what cause this
warning message?
> 2. the gedit session quited on ppc64, don't on x86
> I guess it work correctly on ppc64, not on x86.
It looks like the difference here is probably your locale. On ppc64 you
were using some form of en_US or en_GB, correct?
Yes. This is the locale on ppc64:
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
> 3. on x86, it complained with some warning message:
> Warning: AT-SPI error: pre method check: add: Unknown CORBA
exception > id: 'IDL:omg.org/CORBA/COMM_FAILURE:1.0'
I've seen those messages before (but never where you saw them) and
they're generally not a good sign. The first step is telling me what
locale you were using, so I can try to reproduce.
I am not very sure if this is related to locale setting. But after I
re-install a FC5 and do a "yum update" and "yum install dogtail", this
problem disappeared. So I guess this is related to some setup in the
environment. But I am not sure which part is relevant here.
Regards
- Wu Zhou