GNOME Bugzilla – Bug 494454
crash in Gimmie:
Last modified: 2007-12-01 15:51:03 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: Clearlooks Icon Theme: Vista-Inspirate_1.0 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 (968 sec old) --------------------- ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ASSERT: "width" in /build/buildd/kdelibs-3.5.6/./kate/part/katerenderer.cpp (798) ...Too much output, ignoring rest... -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 2 arguments (1 given)
*** Bug 494455 has been marked as a duplicate of this bug. ***
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 ***