GNOME Bugzilla – Bug 544916
crash in File Browser:
Last modified: 2008-07-27 09:53:30 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Mist Memory status: size: 83415040 vsize: 83415040 resident: 26181632 share: 17448960 rss: 26181632 rss_rlim: 4294967295 CPU usage: start_time: 1217120168 rtime: 303 utime: 278 stime: 25 cutime:3 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xb6b3d720 (LWP 26908)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 203879
Thread 1 (Thread 0xb6b3d720 (LWP 26908))
----------- .xsession-errors (331337 sec old) --------------------- ========================================================================== ========================================================================== Opening audio decoder: [faad] AAC (MPEG2/4 Advanced Audio Coding) FAAD: compressed input bitrate missing, assuming 128kbit/s! AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000) Selected audio codec: [faad] afm: faad (FAAD AAC (MPEG-2/MPEG-4 Audio) decoder) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 704 x 464 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 1.85:1 - prescaling to correct movie aspect. VO: [xv] 704x464 => 858x464 Planar YV12 A: 0.4 V: 0.0 A-V: 0.384 ct: 0.000 0/ 0 ??% ??% ??,?% 0 0 A: 0.5 V: 0.0 A-V: 0.497 ct: 0.004 0/ 0 ??% ??% ??,?% 3 0 A: 0.6 V: 0.1 A-V: 0.512 ct: 0.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 522534 ***