gwibber crashed with NameError in <lambda>(): free variable 'about_dialog' referenced before assignment in enclosing scope

[Simon Butcher]

Binary package hint: gwibber

Testing gwibber in natty:

1) open help-about
2) refresh gwibber
3) try to close help-about window
4) gwibber crash.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 2.91.90-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Mon Feb 28 15:57:54 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gwibber']
SourcePackage: gwibber
Title: gwibber crashed with NameError in <lambda>(): free variable 'about_dialog' referenced before assignment in enclosing scope
Traceback:
 Traceback (most recent call last):
   File "/usr/lib/python2.7/dist-packages/gwibber/client.py", line 507, in <lambda>
     about_dialog.connect("response", lambda *a: about_dialog.hide())
 NameError: free variable 'about_dialog' referenced before assignment in enclosing scope
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout dip fax floppy fuse nopasswdlogin plugdev tape video

[Apport retracing service (apport)]

This crash has the same stack trace characteristics as bug #346336. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

[Victor Vargas (kamus)]

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 607405, 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 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.