Bug 491941 – 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 491941 - 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:	2007-10-31 03:49 UTC by hallettj
Modified:	2008-06-11 19:10 UTC

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

Description hallettj 2007-10-31 03:49:12 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-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
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 ---------------------
 *** Reloading TopicRunningList: Running Applications
 *** Reloading TopicRunningList: Opened Documents
 *** Reloading TopicRunningList: Active Conversations
 *** Window class matches launcher command: firefox-bin == firefox %u
 *** Reloading TopicRunningList: Computer Running Source
 *** Setting source: <FacebookSource object at 0x9896d9c (gimmie_base+Item at 0x98d4280)>
 *** Setting source: <OnlineBuddySource object at 0x9896d4c (gimmie_base+Item at 0x98d66a0)>
 !!! Error loading Administration items: The menu file system-settings.menu could not be found.
 *** RGimmie Version: 0.3.0
Traceback (most recent call last):

+ Trace 174074

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

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

--------------------------------------------------
Gimmie Version: 0.3.0

Traceback (most recent call last):

+ Trace 174074

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

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

Comment 1 H. 2007-11-01 00:08:30 UTC

Thanks for taking the time to report this bug.
As i see you are using the SVN version of Gimmie could you also tell us what you did to see Gimmie crashing? Thanks in advance.

This could be related to bug 475020.

Comment 2 Jesse Hallett 2007-11-01 00:31:44 UTC

No problem.

The crash occurs when I am running standalone and I open the Linux topic for the first time. The topic window appears, and Gimmie crashes almost immediately after that.

Gimmie does not crash every time that I perform the above steps. I would say it works correctly about half the time. After the Linux topic has been opened once, it seems to be safe to open it again, even if I close the window instead of letting it hide itself.

Comment 3 Susana 2008-06-11 19:10:44 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 ***