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

[Robert Roth]

Binary package hint: gwibber

This happened three times to me with the following usecase:

1) open the about dialog
2) click a @mention link
3) try to close the about dialog

Gwibber crashes.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gwibber 2.91.93-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
Date: Sat Apr 2 22:42:10 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110202)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
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: Upgraded to natty on 2011-03-28 (5 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[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)]

same here, this is possible a regression of an old one.

[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.