I suspect this is happening because g_dbus_connection_register_object is called asynchronously from server.c:register_object() in dbusmenu. Menus are being constructed and the window is registered synchronously (after creating the DbusmenuServer) by appmenu-gtk and firefox, so the window registration dbus call is happening before returning to the main loop (where the menu object would be registered).
I'm not sure this can actually fixed reliably in indicator-appmenu. I think what we really need is a new "registered" signal from DbusmenuServer, which can be fired from bus_got_cb(). We can then do the window registration asynchronously from this signal and avoid the race condition altogether. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/703689 Title: Window registration racy with GDbus port -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
