GNOME Bugzilla – Bug 479348
crash in Gimmie: Playing a HD (x264) vid...
Last modified: 2007-09-23 14:35:57 UTC
What were you doing when the application crashed? Playing a HD (x264) video with MPlayer (not fullscreen) 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 Fri Aug 31 00:55:27 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 --------------------- ========================================================================== Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) AUDIO: 48000 Hz, 2 ch, s16le, 126.4 kbit/8.23% (ratio: 15797->192000) Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder) ========================================================================== AO: [oss] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 1280 x 544 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. [swscaler @ 0x88be2b0]SwScaler: using unscaled yuv420p -> bgr24 special converter VO: [x11] 1280x544 => 1280x544 Planar YV12 [zoom] New_Face failed. Maybe the font path is wrong. Please supply the text font file (~/.mplayer/subfont.ttf). subtitle font: load_sub_face failed. A: 0.3 V: 0.0 A-V: 0.298 ct: 0.000 1/ 1 ??% ??% ??,?% 1 0 A: 0.3 V: 0.0 A-V: 0.261 ct: 0.002 2/ 2 ??% ??% ??,?% 2 0 A: 0.3 V: 0.1 A-V: 0.229 ct: 0.0 -------------------------------------------------- Traceback (most recent call last):
+ Trace 164706
self.recent_items[recent_item.get_uri()] = recent_item
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 ***