Menu item becomes unresponsive if too many menus are sent.
Bug #826944 reported by
David Euresti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DBus Menu |
Triaged
|
Low
|
Unassigned | ||
| libdbusmenu (Ubuntu) |
Triaged
|
Low
|
Unassigned | ||
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/
int32 182768
string "clicked"
variant int32 0
uint32 611384815
error sender=:1.758 -> dest=:1.43 error_name=
string "The ID supplied 182768 does not refer to a menu item we have"
Revision history for this message
| David Euresti (david-dropbox) wrote | #1 |
| affects: | indicator-application → dbusmenu |
| Changed in dbusmenu: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
Revision history for this message
| David Euresti (david-dropbox) wrote | #2 |
| Changed in libdbusmenu (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
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.
Thanks,
David