Some analysis on #ubuntu-devel today suggests this may be a reference counting bug somewhere in the unity stack that has been exposed by refcount fixes in the new version of glib2.0 found in saucy.
Colin Watson points out a similar issue was fixed in ubiquity 2.15.3.
ubiquity (2.15.3) saucy; urgency=low
* Increment reference count on address before returning it from
ubiquity_mock_resolver_lookup_by_name_finish, fixing a segfault in the
test suite.
-- Colin Watson <email address hidden> Wed, 15 May 2013 22:22:07 +0100
Some analysis on #ubuntu-devel today suggests this may be a reference counting bug somewhere in the unity stack that has been exposed by refcount fixes in the new version of glib2.0 found in saucy.
Colin Watson points out a similar issue was fixed in ubiquity 2.15.3.
ubiquity (2.15.3) saucy; urgency=low
* Increment reference count on address before returning it from mock_resolver_ lookup_ by_name_ finish, fixing a segfault in the
ubiquity_
test suite.
-- Colin Watson <email address hidden> Wed, 15 May 2013 22:22:07 +0100