I'm not entirely sure this is a bug in autopilot-gtk. See http://paste.ubuntu.com/6725605/. Where you can see that the segfault occurs before the autopilot test executes the progress bar tests. Which is where we get the MatchStringProperty fail when trying to match the webkitwindow's name.
I cannot find anything sinister that would cause the atk_object_set_parent in Gtk/Atk and WebKitGtk, I even ran various tests against the GtkWidgets that use set_parent, which resulted in no problems. I also went through at-spi2-atk, thinking maybe if there was an invalid pointer a d-bus connection was being closed, but even that seemed to be ok. I'm wondering if this is something to do with bug 1260396, and also with this bug starting to appear after the update to Gtk 3.10. on 10th December. The point where the segfault is occurring is the point I highlight in bug 1260396 where the window flickers back from full screen width to the correct size. Could this be caused by slow rendering/transitioning of the window coming back to to its default size??? i.e a parent object not entirely in place before the atk object cache is being 're-synced'?? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267116 Title: ubiquity crashed with SIGSEGV in GtkNode::MatchStringProperty() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot-gtk/+bug/1267116/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
