awn-settings crashed with GError in bind_to_gtk_component()

[masrafas]

Binary package hint: avant-window-navigator

Description: Ubuntu lucid (development branch)
Release: 10.04

Package version: 0.3.9~bzr1890-0ubuntu1

each time opening leads to an error

Traceback (most recent call last):
  File "/usr/bin/awn-settings", line 1102, in <module>
    awnmanager = awnManagerMini()
  File "/usr/bin/awn-settings", line 968, in __init__
    self.prefManager = awnPreferencesMini(self.wTree)
  File "/usr/bin/awn-settings", line 192, in __init__
    self.wTree.get_object(wtree_name), False)
  File "/usr/share/avant-window-navigator/awn-settings/awnSettingsHelper.py", line 142, in bind_to_gtk_component
    config.BIND_METHOD_FALLBACK)
glib.GError: Could not find the key specified: /apps/instances/avant-window-navigator/panel-1/panel/monitor_align.

ProblemType: Crash
Architecture: amd64
Date: Sat Jan 30 08:49:43 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/awn-settings
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20091209)
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: awn-settings 0.3.9~bzr1890-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/awn-settings
ProcEnviron:
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
PythonArgs: ['/usr/bin/awn-settings']
SourcePackage: avant-window-navigator
Title: awn-settings crashed with GError in bind_to_gtk_component()
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev root sambashare tape video

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #514205, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.