After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 483326 - crash in Gimmie:
crash in Gimmie:
Status: RESOLVED DUPLICATE of bug 475020
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-04 12:27 UTC by Borislav Arnaudov
Modified: 2007-10-06 11:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Borislav Arnaudov 2007-10-04 12:27:58 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.0 2007-09-17 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: nuoveXT.2.2

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors (18530 sec old) ---------------------
u1
n1
xo
drawing
download
upload
    0
    0
xo
drawing
u1
n1
xo
draw
...Too much output, ignoring rest...
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):

+ Trace 167676

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 232 in <lambda> 
    printer.connect("attributes_changed", lambda p: self.emit("reload"))
NameError: free variable 'self' referenced before assignment in enclosing scope 






Comment 1


Susana





          2007-10-06 11:01:43 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 475020 ***