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 495882 - 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-11-11 15:07 UTC by gfdgd
Modified: 2007-12-01 15:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gfdgd 2007-11-11 15:07:28 UTC
What were you doing when the application crashed?



Distribution: Ubuntu 7.04 (feisty)
Gnome Release: 2.18.1 2007-04-10 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 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 ---------------------
korganizer: ERROR: Can't decrement change count. It already is 0.
korganizer: ERROR: Can't decrement change count. It already is 0.
(gimmie:23070): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
(gimmie:23070): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
(gimmie:23070): Wnck-WARNING **: Property _NET_WM_NAME contained invalid UTF-8
Gimmie Version: 0.2.7
TypeError: <lambda>() takes exactly 2 arguments (1 given)
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: <lambda>() takes exactly 2 arguments (1 given)
Comment 1 H. 2007-12-01 15:49:08 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 ***