Ubuntu 13.04 raring, "Show mesh status" fails

[ghost]

Got an error when trying to "Show mesh status" on an established mesh connection under Ubuntu 13.04, running Unity. No window shows and the following is outputed in the terminal window I started commotion-mesh-applet from:

Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/commotion_applet_support.py", line 390, in show_mesh_status
self.meshstatus.show()
File "/usr/lib/python2.7/dist-packages/commotion_applet_support.py", line 114, in show
self.update()
File "/usr/lib/python2.7/dist-packages/commotion_applet_support.py", line 102, in update
if link:
UnboundLocalError: local variable 'link' referenced before assignment

Update:
Apparently olsrd haven't found any neighbors (despite there being a couple of nodes around that are actively meshing) when checking 'echo all | nc localhost 2006'. And I also occasionally get the following error output - I think it's when I start establishing a connection (it comes before NetworkManager lets me know that the connection has been established).

ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 230, in maybe_handle_message
self._handler(_args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/NetworkManager.py", line 108, in helper
handler(_args, *_kwargs)
File "/usr/lib/python2.7/dist-packages/commotion_applet_support.py", line 374, in create_menu
strengths[profile[0]])
File "/usr/lib/python2.7/dist-packages/commotion_applet_support.py", line 300, in add_visible_profile_menu_item
os.path.join(self.nm_icon_dir, 'nm-signal-100.png'))
TypeError: add_menu_item() takes at most 4 arguments (5 given)

I'll dig some more...

[hawkinswnaf]

Thank you for digging into this. Please keep us posted on what you find. I am going to import this into our redmine bug tracking system so that we can keep track of it internally. I will post a link to that. Thanks again for digging into this!

[hawkinswnaf]

https://code.commotionwireless.net/issues/572

[technosopher]

Starting work on this now.

(This message brought to you by Hub board)

[technosopher]

The second issue has been fixed; the first is still a problem. Clicking on "show mesh status" when no mesh is active should result in a visible error, not just a silent failure

[technosopher]

Resolved by completely disabling the "show mesh status button" when no routes are available. The larger issue (that olsrd often fails to get routes when connected to an encrypted mesh" remains, but is outside the scope of this UI concern.