GNOME Bugzilla – Bug 490525
crash in Movie Player:
Last modified: 2007-10-26 14:45:23 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Gentoo Base System release 1.12.10 Gnome Release: 2.18.1 2007-05-04 (Gentoo) BugBuddy Version: 2.18.1 System: Linux 2.6.22-sabayon #1 SMP Sat Jul 21 08:41:12 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Human-Graphite Icon Theme: Tango Memory status: size: 353726464 vsize: 353726464 resident: 47935488 share: 26382336 rss: 47935488 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193407701 rtime: 403 utime: 375 stime: 28 cutime:2 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/totem' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) 0x00002b4d1d293978 in ?? () from /lib/libpthread.so.0
+ Trace 173035
----------- .xsession-errors --------------------- AO: [oss] 44100Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 320 x 240 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 320x240 => 320x240 Planar YV12 A: 4.0 V: 4.0 A-V: 0.009 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 4.0 V: 4.0 A-V: -0.003 ct: -0.003 2/ 2 ??% ??% ??,?% 0 0 A: 4.0 V: 4.1 A-V: -0.030 ct: -0.0 Exiting... (Quit) (totem:10001): GStreamer-WARNING **: adding flushing pad 'audio_00' to running element 'asfdemux0' (totem:10001): GStreamer-WARNING **: adding flushing pad 'video_00' to running element 'asfdemux0' ** ERROR **: file gstasfdemux.c: line 493 (gst_asf_demux_get_var_length): assertion failed: (*p_size >= 2) aborting... --------------------------------------------------
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 336370 ***