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 477408 - crash in Gimmie: I just wanted to start i...
crash in Gimmie: I just wanted to start i...
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-09-16 07:26 UTC by Philipp Baer
Modified: 2007-09-16 09:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Philipp Baer 2007-09-16 07:26:19 UTC 
What were you doing when the application crashed?
I just wanted to start it....


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.19.92 2007-09-04 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-11-generic #1 SMP Fri Sep 7 04:31:16 GMT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
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 (59284 sec old) ---------------------
(gnome-terminal:16588): atk-bridge-WARNING **: failure: no device event controller found.
(gnome-terminal:16588): atk-bridge-WARNING **: failure: no device event controller found.
(gnome-terminal:16588): atk-bridge-WARNING **: failure: no device event controller found.
(gnome-terminal:16588): atk-bridge-WARNING **: failure: no device event controller found.
...Too much output, ignoring rest...
--------------------------------------------------
Gimmie Version: 0.2.7

TypeError: <lambda>() takes exactly 2 arguments (1 given)
Comment 1 H. 2007-09-16 09:54:26 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 ***