GNOME Bugzilla – Bug 461102
crash in File Browser: I opened the preferences...
Last modified: 2007-07-28 19:22:20 UTC
Version: 2.18.3 What were you doing when the application crashed? I opened the preferences on a .mp4 file Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-1-amd64 #1 SMP Mon Jul 23 12:43:14 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 375443456 vsize: 375443456 resident: 36749312 share: 18132992 rss: 36749312 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185576106 rtime: 172 utime: 159 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47765852654416 (LWP 9936)] 0x00002b7154881c7f in waitpid () from /lib/libpthread.so.0
+ Trace 151068
Thread 1 (Thread 47765852654416 (LWP 9936))
----------- .xsession-errors (4548 sec old) --------------------- Selected video codec: [ffodivx] vfm: ffmpeg (FFmpeg MPEG-4) ========================================================================== ========================================================================== Opening audio decoder: [mp3lib] MPEG layer-2, layer-3 AUDIO: 48000 Hz, 2 ch, s16le, 128,0 kbit/8,33% (ratio: 16000->192000) Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3) ========================================================================== AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... VDec: vo config request - 640 x 272 (preferred colorspace: Planar YV12) VDec: using Planar YV12 as output csp (no 0) Movie-Aspect is 2,35:1 - prescaling to correct movie aspect. VO: [xv] 640x272 => 640x272 Planar YV12 A: 0,0 V: 0,0 A-V: 0,005 ct: 0,000 1/ 1 ??% ??% ??,?% 0 0 A: 0,0 V: 0,0 A-V: -0,011 ct: -0,002 2/ 2 ??% ??% ??,?% 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 the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 449643 ***