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 422039 - 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-03-23 21:23 UTC by Bruno
Modified: 2007-03-27 22:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Bruno 2007-03-23 21:23:23 UTC 
What were you doing when the application crashed?



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

System: Linux 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
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 ---------------------
alarm-queue.c:526 (load_alarms) - Setting Call backs 
alarm-notify.c:337 (alarm_msgport_replied) - 0x80c4958: Replied to GUI thread
alarm-notify.c:393 (cal_opened_cb) contacts:/// - Calendar Status 0
alarm-queue.c:2057 (alarm_queue_add_client) - Posting a task
alarm-notify.c:349 (alarm_msg_received) - 0x80c39e0:** Message: drive = 0
** Message: volume = 0
** Message: <information>	You are now connected to the wired network.
** Message: <information>	You are now connected to the wired network.
** Message: <information>	You are now connected to the wired network.
** Message: <information>	You are now connected to the wired network.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x3600020 (How_to_Rec); these messages lack timestamps and therefore suck.
--------------------------------------------------
Traceback (most recent call last):

+ Trace 121569

  • 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-25 23:17:30 UTC
        



What version of Gimmie are you running? This bug should have been fixed since version 0.2.5.






Comment 2


Tony Tsui





          2007-03-27 22:27:38 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 ***