GNOME Bugzilla – Bug 486471
crash in Gimmie:
Last modified: 2007-10-14 13:31:44 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 (4402 sec old) --------------------- Opening audio decoder: [libmad] libmad mpeg audio decoder AUDIO: 44100 Hz, 2 ch, s16le, 224.0 kbit/15.87% (ratio: 28000->176400) Selected audio codec: [mad] afm: libmad (libMAD MPEG layer 1-2-3) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 352 x 240 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.30:1 - prescaling to correct movie aspect. VO: [x11] 352x240 => 352x270 Planar YV12 [zoom] SwScaler: using unscaled yuv420p -> rgb32 special converter A: 0.9 V: 0.0 A-V: 0.848 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 1.0 V: 0.3 A-V: 0.641 ct: 0.003 2/ 2 ??% ??% ??,?% 1 0 A: 1.0 V: 0.6 A-V: 0.365 ct: 0.0 fixme:heap:RtlCompactHeap stub A: 509.8 V: 509.6 A-V: 0.234 ct: 0.137 307/307 ??% ??% ??,?% 0 0 A: 509.8 V: 509.6 A-V: 0.219 ct: 0.140 308/308 ??% ??% ??,?% 0 0 A: 509.8 V: 509.6 A-V: 0.228 ct: 0.1 ...Too much output, ignoring rest... -------------------------------------------------- Gimmie Version: 0.2.7 TypeError: <lambda>() takes exactly 2 arguments (1 given)
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 ***