Bug 1274468
Summary: | Need updated pyatspi package for GTK3 testing | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Sean Toner <stoner> |
Component: | pyatspi | Assignee: | Rui Matos <rmatos> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.2 | CC: | jgalipea, jsefler, lmiksik, stoner, tpelka |
Target Milestone: | rc | Keywords: | Rebase, TestBlocker |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | pyatspi-2.14.0-1.el7 | Doc Type: | Rebase: Bug Fixes and Enhancements |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-11-04 01:48:21 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Sean Toner
2015-10-22 19:08:50 UTC
Sean does the rebased pyatspi & friends full filled your needs in rhel7.3? Can we move this bz to verified? Thanks -Tom I am trying to verify this, but have been running into issues with my test environment. I will update as soon as I can get past these issues. (In reply to Sean Toner from comment #7) > I am trying to verify this, but have been running into issues with my test > environment. I will update as soon as I can get past these issues. OK I can wait week or two (Sep 22.) and than move to verified as our test framework using AT-SPI works as expected. Deal? That's fair. I have verified that we can do keyevents and the spinners now. The combo box appears broken still. I can set a value for the combo box, but getting the current value of the combo box seems to be broken (it always returns the same starting value, even if you change it). I want to try to isolate if getting the value from the combo box might be an LDTP issue rather than a pyatspi one. I was not able to test out pyatspi unfortunately. I will close this issue out as I suspect this might be a ldtp bug rather than a pyatspi one. All the other functionality is working though. (In reply to Sean Toner from comment #10) > I was not able to test out pyatspi unfortunately. I will close this issue > out as I suspect this might be a ldtp bug rather than a pyatspi one. All > the other functionality is working though. Thanks Sean. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2262.html |