After a bit more research the problem is clear: GDBus makes no guarantees that cancelling a cancellable will result in the associated async operation terminating in an error. Specifically: if the (successful) result is already sent to the main context as an idle and waiting for dispatch then cancel() at this time will not be enough to fail it.
Talking to David and Alex about if GIO should make this guarantee or if we need to fix dbusmenu... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/953562 Title: hud-service crashed with SIGSEGV in menuproxy_build_cb() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-appmenu/+bug/953562/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
