|
Bugzilla – Full Text Bug Listing |
| Summary: | accerciser and strongwind test couldn't be running remotely after upgrade at-spi-1.28 to 1.29 | ||
|---|---|---|---|
| Product: | [Mono] UI Automation | Reporter: | calen chen <cachen> |
| Component: | Client - AT-SPI | Assignee: | E-mail List <mono-a11y-bugs> |
| Status: | NEW --- | QA Contact: | E-mail List <mono-a11y-qa> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | mgorse |
| Version: | Release 2.0 | ||
| Target Milestone: | Release 2.1 | ||
| Hardware: | All | ||
| OS: | openSUSE 11.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
calen chen
2010-03-08 12:30:29 UTC
I'm not sure what could be going on off-hand. The "AT-SPI Accessibility bus not found - Using session bus" message is a warning that is currently displayed by the at-spi2 version of libatk-bridge.so, so somehow accerciser is running it, although it is using the CORBA version of pyatspi. Do you get this warning if you, say, run gedit on machine A? If so, I'd suggest trying running it under strace to figure out where gtk is looking for libatk-bridge.so. please ignore "** (accerciser:5541): WARNING **: AT-SPI: Accessibility bus not found - Using session bus.", I copied the message from machine which have installed both at-spi1 and at-spi2, sorry for that. but whether at-spi2 is installed or not, RuntimeError would occurred. |