BamfWindow in autopilot bamf emulator bails out on geometry property

Bug #1079579 reported by Łukasz Zemczak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
New
Medium
Unassigned

Bug Description

See attached autopilot test for a problem test-case.

When calling the geometry property of a BamfWindow object (for instance, as returned by self.start_app_window()), the bamf emulator bails out with the following error:

  File "/usr/lib/python2.7/dist-packages/autopilot/emulators/bamf.py", line 336, in geometry
    origin = GdkX11.X11Window.foreign_new_for_display(get_display(), self._xid).get_origin()
  File "/usr/lib/python2.7/dist-packages/gi/types.py", line 76, in constructor
    return info.invoke(cls, *args, **kwargs)
TypeError: argument display: Expected Gdk.Display, but got Xlib.display.instance

It seems as if the get_display() function is wrongly used in the geometry property.

Revision history for this message
Łukasz Zemczak (sil2100) wrote :
Revision history for this message
Thomi Richards (thomir-deactivatedaccount) wrote :

Setting to "New" and targetting to 1.3. We need to determine if this property is still supported in the 1.3 tree, and if it is, whether this bug is still valid for the Bamf emulator.

If one or more of these is false then the bug should be closed.

Changed in autopilot:
status: New → Won't Fix
status: Won't Fix → New
milestone: none → 1.3
Martin Mrazik (mrazik)
Changed in autopilot:
importance: Undecided → Medium
Changed in autopilot:
milestone: 1.3 → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.