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 425676 - crash in Gimmie:
crash in Gimmie:
Status: RESOLVED DUPLICATE of bug 417988
Product: gimmie
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Gimmie Maintainers
Gimmie Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-02 23:31 UTC by Igor Miletic
Modified: 2007-04-03 22:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Igor Miletic 2007-04-02 23:31:40 UTC 
What were you doing when the application crashed?



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:38:26 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

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 (79 sec old) ---------------------
NetworkManager is stopped
#swat#
xinetd (pid 2595) is running...
camel-Message: --
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x5c000b1 specified for 0x5c018c2 (Find).
Compiler did not align stack variables. Libavcodec has been miscompiled
and may be very slow or crash. This is not a bug in libavcodec,
but in the compiler. Do not report crashes to FFmpeg developers.
[wmv3 @ 0x1339b64]Extra data: 8 bits left, value: 0
Debug: Loading Beagle.Util.Conf+IndexingConfig from indexing.xml
Debug: Loading Beagle.Util.Conf+DaemonConfig from daemon.xml
Debug: Loading Beagle.Util.Conf+SearchingConfig from searching.xml
Debug: Creating a ResponseMessageException from an ErrorResponse
Debug: Creating a ResponseMessageException from an ErrorResponse
*** Using mono runtime at mono ***
--------------------------------------------------
Traceback (most recent call last):

+ Trace 124478

  • File "/usr/local/lib/python2.4/site-packages/gimmie/gimmie_util.py", line 865 in _model_changed 
    self.recent_items[recent_item.get_uri()] = recent_item
TypeError: <lambda>() takes exactly 1 argument (2 given) 






Comment 1


Tony Tsui





          2007-04-03 22:48:16 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 417988 ***