Ubuntu
restricted-manager package

crash when started (right after an update from Feisty to Gutsy)

Bug #134054 reported by Lau on 2007-08-22

This bug report is a duplicate of: Bug #133218: restricted-manager crashed with TypeError in description(). Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	restricted-manager (Ubuntu)	New	Undecided	Unassigned

Bug Description

Nothing happens when asked to click on the "restricted-manager" icon on the menu bar.

A little more verbose on what is going on when called from a terminal:
~$ restricted-manager
  File "/usr/bin/restricted-manager", line 42, in <module>
    rm = RestrictedManager()
  File "/usr/lib/python2.5/site-packages/RestrictedManager/RestrictedManagerGtk.py", line 53, in __init__
    RestrictedManagerCommon.__init__(self,args,opts)
  File "/usr/lib/python2.5/site-packages/RestrictedManager/RestrictedManagerCommon.py", line 186, in __init__
    self.launch_manager()
  File "/usr/lib/python2.5/site-packages/RestrictedManager/RestrictedManagerGtk.py", line 151, in launch_manager
    self.ManagerWindow(self.xml, self.handlers, self)
  File "/usr/lib/python2.5/site-packages/RestrictedManager/RestrictedManagerGtk.py", line 208, in __init__
    self.reset_model()
  File "/usr/lib/python2.5/site-packages/RestrictedManager/RestrictedManagerGtk.py", line 228, in reset_model
    handlers = sorted(self.handlers.values(), key=lambda x: (x._type, x.description))
  File "/usr/lib/python2.5/site-packages/RestrictedManager/RestrictedManagerGtk.py", line 228, in <lambda>
    handlers = sorted(self.handlers.values(), key=lambda x: (x._type, x.description))
  File "/usr/lib/python2.5/site-packages/RestrictedManager/handlers/lrm_driver.py", line 28, in description
    return DriverHandler.description(self)
TypeError: 'property' object is not callable

Revision history for this message

Tommaso R. Donnarumma (tawmas) wrote on 2007-08-23:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 134097, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can add, or to see if there is a workaround for the bug. Feel free to continue to report any other bugs you may find.