GNOME Bugzilla – Bug 441004
crash in Gimmie: Opening the ::Computer w...
Last modified: 2007-05-26 00:58:55 UTC
What were you doing when the application crashed? Opening the ::Computer window in nautilus Distribution: Ubuntu 7.04 (feisty) Gnome Release: 2.18.1 2007-04-10 (Ubuntu) BugBuddy Version: 2.18.1 System: Linux 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora-looks Icon Theme: OSX 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 (171851 sec old) --------------------- Forced audio codec: mad Opening audio decoder: [libmad] libmad mpeg audio decoder AUDIO: 48000 Hz, 2 ch, s16le, 160.0 kbit/10.42% (ratio: 20000->192000) 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 - 512 x 288 (preferred colorspace: Planar YV12) Opening video filter: [pp] VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.78:1 - prescaling to correct movie aspect. VO: [xv] 512x288 => 512x288 Planar YV12 A: 0.1 V: 0.0 A-V: 0.145 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.5 V: 0.0 A-V: 0.448 ct: 0.003 2/ 2 ??% ??% ??,?% 0 0 A: 0.5 V: 0.1 A-V: 0.415 ct: 0.0 A: 4.6 V: 4.6 A-V: 0.016 ct: 0.048 139/139 5% 6% 1.9% 8 0 A: 4.7 V: 4.6 A-V: 0.016 ct: 0.049 140/140 5% 6% 1.9% 8 0 A: 4.7 V: 4.7 A-V: 0.004 ct: 0.0 ...Too much output, ignoring rest... -------------------------------------------------- Traceback (most recent call last):
+ Trace 135873
for recent_item in self.get_items():
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 ***