[at-spi2-core/gnome-3-20] Correctly handle at-spi2-registryd dying when processing NameOwnerChanged
- From: Mike Gorse <mgorse src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [at-spi2-core/gnome-3-20] Correctly handle at-spi2-registryd dying when processing NameOwnerChanged
- Date: Thu, 2 Jun 2016 23:56:08 +0000 (UTC)
commit 9b2c6f2f6d8ea9ec4d65f664910b73a6f317104b
Author: Mike Gorse <mgorse suse com>
Date: Thu Jun 2 18:53:26 2016 -0500
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 | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/atspi/atspi-misc.c b/atspi/atspi-misc.c
index 1ec9be1..1dcc3de 100644
--- a/atspi/atspi-misc.c
+++ b/atspi/atspi-misc.c
@@ -389,7 +389,7 @@ handle_name_owner_changed (DBusConnection *bus, DBusMessage *message, void *user
else if (app_hash)
{
AtspiApplication *app = g_hash_table_lookup (app_hash, old);
- if (app)
+ if (app && !strcmp (app->bus_name, old))
g_object_run_dispose (G_OBJECT (app));
}
return DBUS_HANDLER_RESULT_HANDLED;
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]