Bug 511471 – 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 511471 - 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-01-23 07:37 UTC by tero.toivola
Modified:	2008-03-10 12:14 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description tero.toivola 2008-01-23 07:37:06 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: IndustrialTango
Icon Theme: Tango

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 (206 sec old) ---------------------
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
(mail-notification:6619): mail-notification-WARNING **: thtoivol@imap.hut.fi: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found
--------------------------------------------------
Gimmie Version: 0.2.8

Traceback (most recent call last):

+ Trace 186451

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-03-10 12:14:13 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 ***