the issue has been fixed since
** Changed in: indicator-appmenu
Status: New = Fix Released
** Changed in: indicator-appmenu (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah, I figured out why it doesn't work now. If GetLayout fails once, then
it never works again. This branch fixes that too:
lp:~chrisccoulson/dbusmenu/signal-on-new-menu
With both of those changes, window registration is working every time
now
--
You received this bug notification because you
Okay,
So I'd like to avoid burdening the server implementors with having to
worry about when things get registered. It is just a low-level detail
they shouldn't have to know about. I think that we can achieve the same
thing with this branch:
lp:~ted/dbusmenu/signal-on-new-menu
It sends a
Hmmm, that doesn't seem to work. I still frequently get no menubar
--
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
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
These 2 patches completely fix menu registration in Firefox:
http://bazaar.launchpad.net/~chrisccoulson/dbusmenu/lp703689/revision/185
http://bazaar.launchpad.net/~chrisccoulson/globalmenu-extension/async-registration/revision/62
The dbusmenu patch adds a registered signal to DbusmenuServer
