Correctly handle at-spi2-registryd dying when processing NameOwnerChanged
authorMike Gorse <mgorse@suse.com>
Thu, 2 Jun 2016 23:53:26 +0000 (18:53 -0500)
committerMike Gorse <mgorse@suse.com>
Thu, 2 Jun 2016 23:53:26 +0000 (18:53 -0500)
commita61ec0f6086b81fc9c9d811d48069228ac9c5f34
tree73f312724f62c56142f923fb8f7f061e78cae55f
parentcdb353694464aeb1686fa7a559db38945aa28eee
Correctly handle at-spi2-registryd dying when processing NameOwnerChanged

If at-spi2-registryd dies, then we receive two NameOwnerChanged signals,
one for org.a11y.atspi.Registry and the other for the initial dbus-issued
name. When we received the latter, we were matching it to the AtspiApplication
corresponding to the desktop and inadvertently disposing it, leading to a
crash later on.
atspi/atspi-misc.c