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 424197 - crash in Gimmie: Browsing a file in Gedit
crash in Gimmie: Browsing a file in Gedit
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-03-29 17:26 UTC by jeroen.kurvers
Modified: 2007-03-29 22:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description jeroen.kurvers 2007-03-29 17:26:56 UTC 
What were you doing when the application crashed?
Browsing a file in Gedit


Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.0 2007-03-13 (Ubuntu)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Silicon
Icon Theme: Gorilla

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 (4931 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Traceback (most recent call last):

+ Trace 123276

  • File "/usr/lib/python2.5/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-03-29 22:30:13 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 ***