GNOME Bugzilla – Bug 458048
crash in Gimmie: Just starting standalone...
Last modified: 2007-10-07 11:58:50 UTC
What were you doing when the application crashed? Just starting standalone Gimmie Distribution: Ubuntu 7.10 (gutsy) Gnome Release: 2.19.5 2007-07-11 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 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 (16 sec old) --------------------- (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found (mail-notification:14254): mail-notification-WARNING **: mike@ginou.ca: unable to start SASL authentication: SASL(-4): no mechanism available: No worthy mechs found ***MEMORY-WARNING***: gnome-terminal[31288]: GSlice: g_thread_init() must be called before all other GLib functions; memory corruption due to late invocation of g_thread_init() has been detected; this -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 1 argument (2 given)
I got the same crash, also running Ubuntu 7.10. The problem is that when certain lambda expressions are evaluated after being passed to wnck.Screen.connect, the are complaining that they are receiving more arguments than they expect. Maybe earlier versions of Python could ignore extra arguments?, so this isn't a problem in other OS versions? The method _workspace_changed has the same problem when it is passed to wnck.Screen.connect. I have included a patch that seems to make everything work again. It also fixes another issue in gimmie_computer. Certain lambda expressions were throwing exceptions saying that "self" was evaluated before being bound in the enclosed scope. The patch fixes this by moving calls to wnck.Screen.connect before other invocations of "self".
Created attachment 93764 [details] [review] Fixes a number of cases of too many arguments being passed
*** Bug 454901 has been marked as a duplicate of this bug. ***
*** Bug 470382 has been marked as a duplicate of this bug. ***
*** Bug 469011 has been marked as a duplicate of this bug. ***
*** Bug 470239 has been marked as a duplicate of this bug. ***
*** Bug 470745 has been marked as a duplicate of this bug. ***
*** Bug 470913 has been marked as a duplicate of this bug. ***
*** Bug 454898 has been marked as a duplicate of this bug. ***
I can confirm this bug on Ubuntu Gutsy, it seems to always occur on Gnome 2.19 though. I'll mark this as blocker. I'll report back, after I've tried Jesse's patch.
*** Bug 471857 has been marked as a duplicate of this bug. ***
*** Bug 471907 has been marked as a duplicate of this bug. ***
*** Bug 471981 has been marked as a duplicate of this bug. ***
*** Bug 472011 has been marked as a duplicate of this bug. ***
*** Bug 464652 has been marked as a duplicate of this bug. ***
Jesse Hallets patch is working with the last svn version of Gimmie (so 0.3.0)
*** Bug 460410 has been marked as a duplicate of this bug. ***
*** Bug 460448 has been marked as a duplicate of this bug. ***
*** Bug 461973 has been marked as a duplicate of this bug. ***
*** Bug 458873 has been marked as a duplicate of this bug. ***
*** Bug 466084 has been marked as a duplicate of this bug. ***
*** Bug 450692 has been marked as a duplicate of this bug. ***
Confirmed that Jesse's patch fixes it here also - gimmie 0.2.7 on Mandriva Linux Cooker. Awesome! Thanks, Jesse.
*** Bug 472381 has been marked as a duplicate of this bug. ***
*** Bug 472382 has been marked as a duplicate of this bug. ***
*** Bug 472383 has been marked as a duplicate of this bug. ***
*** Bug 474214 has been marked as a duplicate of this bug. ***
*** Bug 474560 has been marked as a duplicate of this bug. ***
*** Bug 474595 has been marked as a duplicate of this bug. ***
*** Bug 474693 has been marked as a duplicate of this bug. ***
*** Bug 474702 has been marked as a duplicate of this bug. ***
*** Bug 474703 has been marked as a duplicate of this bug. ***
*** Bug 474741 has been marked as a duplicate of this bug. ***
*** Bug 475054 has been marked as a duplicate of this bug. ***
*** Bug 475208 has been marked as a duplicate of this bug. ***
*** Bug 475484 has been marked as a duplicate of this bug. ***
*** Bug 475543 has been marked as a duplicate of this bug. ***
*** Bug 475832 has been marked as a duplicate of this bug. ***
*** Bug 476118 has been marked as a duplicate of this bug. ***
*** Bug 458383 has been marked as a duplicate of this bug. ***
*** Bug 476396 has been marked as a duplicate of this bug. ***
*** Bug 455345 has been marked as a duplicate of this bug. ***
*** Bug 462325 has been marked as a duplicate of this bug. ***
*** Bug 476397 has been marked as a duplicate of this bug. ***
Fixed in SVN. Thanks!
*** Bug 484363 has been marked as a duplicate of this bug. ***