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 457838 - crash in Gimmie: Searching the "Linux" ta...
crash in Gimmie: Searching the "Linux" ta...
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-07-18 04:02 UTC by Mike Ginou
Modified: 2007-09-11 18:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Mike Ginou 2007-07-18 04:02:51 UTC 
What were you doing when the application crashed?
Searching the "Linux" tab (applet)


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.5 2007-07-11 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 GMT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
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 (104 sec old) ---------------------
 to Wed Jul 18 00:00:01 2007
alarm-queue.c:479 (load_alarms) 
alarm-queue.c:498 (load_alarms) - Disevolution-alarm-notify-Message: alarm.c:235: Requested removal of nonexistent alarm!
evolution-alarm-notify-Message: Setting timeout for 86400 1184817600 1184731200
evolution-alarm-notify-Message:  Thu Jul 19 00:00:00 2007
evolution-alarm-notify-Message:  Wed Jul 18 00:00:00 2007
checking for valid crashreport now
checking for valid crashreport now
Window manager warning: last_user_time (32) is greater than comparison timestamp (3615236063).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Bottom Exp) appears to be one of the offending windows with a timestamp of 32.  Working around...
Window manager warning: last_user_time (32) is greater than comparison timestamp (3615241576).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE
Window manager warning: 0x1000003 (Bottom Exp) appears to be one of the offending windows with a timestamp of 32.  Working around...
--------------------------------------------------
Gimmie Version: 0.2.7

Traceback (most recent call last):

+ Trace 148746

  • File "/usr/lib/python2.5/site-packages/gimmie/gimmie_computer.py", line 234 in <lambda> 
    printer.connect("attributes_changed", lambda p: self.emit("reload"))
NameError: free variable 'self' referenced before assignment in enclosing scope 






Comment 1


Benedikt Henrichs





          2007-09-11 18:27: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 ***