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 511368 - 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: 2008-01-22 20:51 UTC by Son
Modified: 2008-03-10 13:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Son 2008-01-22 20:51:47 UTC 
What were you doing when the application crashed?



Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Tue Dec 18 08:02:57 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Watercolor
Icon Theme: experimental-20080113

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 (16 sec old) ---------------------
** (nautilus:5050): WARNING **: Cannot extract frame (72, 72) from the grid
** (nautilus:5050): WARNING **: Cannot extract frame (96, 72) from the grid
** (nautilus:5050): WARNING **: Cannot extract frame (120, 72) from the grid
** (nautilus:5050): WARNING **: Cannot extract frame (144, 72) from the grid
** (nautilus:5050): WARNING **: Cannot extract frame (168, 72) from the grid
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):

+ Trace 186399

  • 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


Cosimo Cecchi





          2008-03-10 13:22:35 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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