Bug 544276 – crash in Gimmie:

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 544276 - crash in Gimmie:


Summary:	crash in Gimmie:


Status:	RESOLVED DUPLICATE of bug 475020

Product:	gimmie
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gimmie Maintainers
QA Contact:	Gimmie Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-07-23 06:52 UTC by joe
Modified:	2008-07-23 17:51 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description joe 2008-07-23 06:52:50 UTC

What were you doing when the application crashed?



Distribution: Ubuntu 8.04 (hardy)
Gnome Release: 2.22.2 2008-06-03 (Ubuntu)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-19-generic #1 SMP Fri Jul 11 23:41:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

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 ---------------------
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
CachingBackend: Saving <#ClearCalendar1> :) ...
OK
--------------------------------------------------
Gimmie Version: 0.2.8

Traceback (most recent call last):

+ Trace 203548

File "/usr/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 232 in <lambda>
```
printer.connect("attributes_changed", lambda *args: self.emit("reload"))
```

NameError: free variable 'self' referenced before assignment in enclosing scope

Comment 1 Cosimo Cecchi 2008-07-23 17:51:08 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 ***