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 494938 - crash in Gimmie: Steps to reproduce the p...
crash in Gimmie: Steps to reproduce the p...
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-11-08 12:00 UTC by chirag.rathod
Modified: 2007-11-11 14:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description chirag.rathod 2007-11-08 12:00:57 UTC
What were you doing when the application crashed?
Steps to reproduce the problem:

1. Started the system.
2. Clicked on "Linux" in the Gimmie bar
3. Set cursor in "Search" textfield
4. Wanted to type "Picasa" in it. Gimmie crashed after I typed "pi" and got the crash

Gimmie gave me an option to Restart. I restarted and redid the above steps and got the crash again.


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: Glossy
Icon Theme: Crux

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 (35 sec old) ---------------------
alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Fri Nov  9 00:00:00 2007
 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/hapuchu/.evolution/calendar/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/hapuchu/.evolution/calendar/local/system - Calendar Open Async... 0x80ca9b0
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/hapuchu/.evolution/tasks/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/hapuchu/.evolution/tasks/local/system - Calendar Open Async... 0x80d1d00
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/hapuchu/.evolution/memos/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/ha
(evolution-alarm-notify:5737): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running...
puchu/.evolution/memos/local/system - Calendar Open Async... 0x80d61b0
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x320001c (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Log level 8: gtk_menu_shell_insert: assertion `GTK_IS_MENU_ITEM (child)' failed
Window manager warning: Log level 8: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):
  • 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 H. 2007-11-11 14:22:33 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 ***