We don't need so much additional information anymore from the debug
packages.

I was able to write a small python script that reproduces the issue:
https://code.launchpad.net/~mathieu-tl/+junk/test-indicator-update

Playing with the delays there and the number of updates in a row, you
can easily wedge dbusmenu in a matter of about an hour.

As far as I'm concerned, this proves that the issue isn't in nm-applet
but somewhere in the way that dbusmenu takes care of updates to the
menus, but I'm still not quite sure what is wong with it.

Any help is of course welcome :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1117730

Title:
  nm-applet becomes unresponsive to interactions and submenus such as
  'VPN Connections' show completely empty

Status in DBus Menu:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project precise series:
  Triaged
Status in OEM Priority Project quantal series:
  Triaged
Status in OEM Priority Project raring series:
  Triaged
Status in “libdbusmenu” package in Ubuntu:
  Triaged
Status in “network-manager-applet” package in Ubuntu:
  Confirmed

Bug description:
  broken out of bug 780602, because we believe the root cause to be
  different. From that bug report:


  I experience exactly the same symptoms as the bug report description
  has.

  After some time nm-applet stops reacting to user input and submenu
  entries do not populate. This is with latest 12.10 packages.

  I noticed that the indicator tries to get the menu but it fails - 
dbus-monitor output below:
  method call sender=:1.12 -> dest=:1.67 serial=14296 
path=/com/canonical/Unity/Panel/Service; 
interface=com.canonical.Unity.Panel.Service; member=ShowEntry
     string "0x26ef470"
     uint32 0
     int32 1147
     int32 24
     uint32 1
     uint32 1356027813
  method return sender=:1.67 -> dest=:1.12 reply_serial=14296
  method call sender=:1.67 -> dest=:1.14 serial=107621 
path=/org/ayatana/NotificationItem/nm_applet/Menu; 
interface=com.canonical.dbusmenu; member=AboutToShowGroup
     array [
        int32 80799
     ]
  error sender=:1.14 -> dest=:1.67 
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0 
reply_serial=107621
     string "The IDs supplied '[80799]' do not refer to any menu items we have"

  When some item is clicked (e.g. disconnect for current wifi AP) the following 
happens:
  signal sender=:1.67 -> dest=(null destination) serial=107704 
path=/com/canonical/Unity/Panel/Service; 
interface=com.canonical.Unity.Panel.Service; member=EntryActivated
     string ""
     struct {
        int32 0
        int32 0
        uint32 0
        uint32 0
     }
  method call sender=:1.67 -> dest=:1.14 serial=107705 
path=/org/ayatana/NotificationItem/nm_applet/Menu; 
interface=com.canonical.dbusmenu; member=EventGroup
     array [
        struct {
           int32 80846
           string "clicked"
           variant int32 0
           uint32 106251172
        }
     ]
  error sender=:1.14 -> dest=:1.67 
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0 
reply_serial=107705
     string "The IDs supplied '[80846]' do not refer to any menu items we have"

  So this looks like like dbus menu is losing the IDs or nm-applet is
  using the ids that are no longer valid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libdbusmenu/+bug/1117730/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to