GNOME Bugzilla – Bug 508853
crash in CD/DVD Creator: I was creating new direc...
Last modified: 2008-01-12 11:28:36 UTC
What were you doing when the application crashed? I was creating new directory Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 81068032 vsize: 81068032 resident: 30547968 share: 15765504 rss: 30547968 rss_rlim: 4294967295 CPU usage: start_time: 1200053371 rtime: 4206 utime: 3923 stime: 283 cutime:381 cstime: 43 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6def6b0 (LWP 4012)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 184989
Thread 1 (Thread 0xb6def6b0 (LWP 4012))
----------- .xsession-errors (14881 sec old) --------------------- [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code [mpeg4 @ 0xb6cc4b48]marker does not match f_code ...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 355018 ***