Menu item becomes unresponsive if too many menus are sent.

Bug #826944 reported by David Euresti on 2011-08-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
DBus Menu
libdbusmenu (Ubuntu)

Bug Description

If I update the menu in an app indicator too many times it will become unresponsive. The attached script reproduces the problem. When you run the script it is important to make sure the id of the menu item goes past 30000 to watch it fail.

dbus-monitor replies shows this:

method call sender=:1.43 -> dest=:1.758 serial=509580 path=/org/ayatana/NotificationItem/example_simple_client_0/Menu; interface=org.ayatana.dbusmenu; member=Event
   int32 182768
   string "clicked"
   variant int32 0
   uint32 611384815
error sender=:1.758 -> dest=:1.43 error_name=org.freedesktop.DBus.GLib.UnmappedError.LIBDBUSMENUGLIB.Code0 reply_serial=509580
   string "The ID supplied 182768 does not refer to a menu item we have"

David Euresti (david-dropbox) wrote :
Ted Gould (ted) on 2011-09-20
affects: indicator-application → dbusmenu
Changed in dbusmenu:
importance: Undecided → Low
status: New → Triaged
David Euresti (david-dropbox) wrote :

Hey guys,
I wanted to mention that this doesn't just affect updating the tray menu too quickly. If a user is logged in for long enough they will hit this problem. This happens to the Dropbox client which updates the menu somewhat frequently. And the result is that the menu no longer works at all. None of the callbacks fire, and you can't update the menu anymore.

Ted Gould (ted) on 2014-11-10
Changed in libdbusmenu (Ubuntu):
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers