This crash seems completely internal to glib. It's because of an assert that an internal callback is called with the same connection it was started with.
I don't see another bug about this to dup, so I'm switching tasks to glib. ** Package changed: indicator-messages (Ubuntu) => glib2.0 (Ubuntu) ** Project changed: indicator-messages => glib ** Bug watch added: GNOME Bug Tracker #685995 https://bugzilla.gnome.org/show_bug.cgi?id=685995 ** Changed in: glib Importance: Medium => Unknown ** Changed in: glib Status: Confirmed => Unknown ** Changed in: glib Remote watch: None => GNOME Bug Tracker #685995 ** Changed in: glib Assignee: Lars Uebernickel (larsu) => (unassigned) ** Summary changed: - indicator-messages-service crashed with SIGABRT in g_assertion_message() + indicator-messages-service crashed with assert in g_menu_exporter_name_vanished() -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1044322 Title: indicator-messages-service crashed with assert in g_menu_exporter_name_vanished() To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1044322/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
