Turns out that the GdkX11.X11Display has no public constructor, so it's
invalid to create a GdkDisplay like that. The official API is to use
Gdk.Display.get_default(), which makes this whole thing work. The
question is now, how did that ever work? The same python command crashes
in saucy and raring as well, so it's not something new on the GI/GTK
side. Did we perhaps just recently start doing multi-monitor testing in
CI?
test_panel_title_updates_moving_window() does not have a direct
reference to the "geometry" property, but that might be called somewhere
internally (and that might be a new thing).
autopilot itself doesn't seem to use that property anywhere by itself,
nor does it have a test for it.
** Changed in: autopilot
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1258170
Title:
autopilot crashed with SIGSEGV in XLastKnownRequestProcessed()
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1258170/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
