GNOME Bugzilla – Bug 479347
crash in Gimmie: Tried to switch to fulls...
Last modified: 2007-09-23 14:35:40 UTC
What were you doing when the application crashed? Tried to switch to fullscreen mode in MPlayer while playing a video 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: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 64.0 kbit/4.54% (ratio: 8005->176400) Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg)) ========================================================================== AO: [oss] 44100Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 720 x 576 (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] 720x576 => 720x576 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: 5.1 V: 5.0 A-V: 0.077 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 5.1 V: 5.0 A-V: 0.047 ct: -0.004 2/ 2 ??% ??% ??,?% 0 0 A: 5.1 V: 5.1 A-V: 0.016 ct: -0.0 -------------------------------------------------- Traceback (most recent call last):
+ Trace 164705
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 ***