GNOME Bugzilla – Bug 462032
crash in Show Desktop: usig mplayer
Last modified: 2007-09-02 12:04:16 UTC
Version: 2.18.0 What were you doing when the application crashed? usig mplayer Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 43769856 vsize: 43769856 resident: 10817536 share: 6770688 rss: 10817536 rss_rlim: 4294967295 CPU usage: start_time: 1185828295 rtime: 8202 utime: 7500 stime: 702 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/libexec/wnck-applet' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208891680 (LWP 3060)] (no debugging symbols found) 0x00c35402 in __kernel_vsyscall ()
+ Trace 151748
Thread 1 (Thread -1208891680 (LWP 3060))
----------- .xsession-errors (65310 sec old) --------------------- ASF file format detected. [asfheader] Audio stream found, -aid 1 Clip info: name: Don'T Say Goodbye Girl author: Tevin Campbell ========================================================================== Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders AUDIO: 44100 Hz, 2 ch, s16le, 48.0 kbit/3.40% (ratio: 6003->176400) Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg)) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Video: no video Starting playback... A: 3.1 (03.0) of 272.0 (04:32.0) ??,?% A: 3.1 (03.0) of 272.0 (04:32.0) ??,?% A: 3.1 (03.0) of 272.0 (04:32.0) ??, ...Too much output, ignoring rest... --------------------------------------------------
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 420713 ***