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 495613 - crash in Gimmie: i just run the command "...
crash in Gimmie: i just run the command "...
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-11-10 15:25 UTC by j.leuenberg
Modified: 2007-11-11 14:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description j.leuenberg 2007-11-10 15:25:35 UTC 
What were you doing when the application crashed?
i just run the command "gimmie"


Distribution: Fedora release 8 (Werewolf)
Gnome Release: 2.20.1 2007-10-15 (Red Hat, Inc)
BugBuddy Version: 2.20.1

System: Linux 2.6.23.1-42.fc8 #1 SMP Tue Oct 30 13:55:12 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

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 ---------------------
TypeError: <lambda>() takes exactly 1 argument (2 given)
picRunningList: Running Applications
 *** Reloading TopicRunningList: Opened Documents
 *** Reloading TopicRunningList: Active Conversations
 *** Reloading TopicRunningList: Computer Running Source
** (gimmie:16346): WARNING **: IPP request failed with status 1030
** (gimmie:16346): WARNING **: IPP request failed with status 1030
Gimmie Version: 0.2.7
TypeError: <lambda>() takes exactly 1 argument (2 given)
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: <lambda>() takes exactly 1 argument (2 given)
Comment 1 H. 2007-11-11 14:16:47 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 ***