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 493216 - crash in Gimmie: nothing, just clicked on...
crash in Gimmie: nothing, just clicked on...
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-03 23:46 UTC by estelar57
Modified: 2007-12-01 15:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description estelar57 2007-11-03 23:46:11 UTC
What were you doing when the application crashed?
nothing, just clicked on "recently used"


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 Wed Oct 10 06:00:47 GMT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Tangerine

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 (44 sec old) ---------------------
** Message: Not starting remote desktop server
Throttle level is 0
Initializing gnome-mount extension
Initializing nautilus-open-terminal extension
evolution-alarm-notify-Message: Setting timeout for 1061 1194134400 1194133339
evolution-alarm-notify-Message:  Sat Nov  3 20:00:00 2007
evolution-alarm-notify-Message:  Sat Nov  3 19:42:19 2007
(pessulus:5949): GConf-WARNING **: haven't implemented getting a specific locale in GConfClient
Window manager warning: last_user_time (132471927) is greater than comparison timestamp (132471421).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_
Window manager warning: 0x3200003 (Lockdown E) appears to be one of the offending windows with a timestamp of 132471927.  Working around...
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600028 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Gimmie Version: 0.2.8

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 *args: self.emit("reload"))
NameError: free variable 'self' referenced before assignment in enclosing scope

Comment 1 H. 2007-12-01 15:51:25 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 ***