GNOME Bugzilla – Bug 515913
crash in Open Folder: I closed the window then...
Last modified: 2008-02-12 09:56:54 UTC
Version: 2.20.0 What were you doing when the application crashed? I closed the window then the bug report tool came up Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Neu Memory status: size: 427462656 vsize: 427462656 resident: 35799040 share: 19025920 rss: 35799040 rss_rlim: 18446744073709551615 CPU usage: start_time: 1202751471 rtime: 731 utime: 679 stime: 52 cutime:0 cstime: 1 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b6cd9332060 (LWP 3931)] [New Thread 0x40800950 (LWP 4055)] (no debugging symbols found) 0x00002b6cd306834f in waitpid () from /lib/libpthread.so.0
+ Trace 188900
Thread 1 (Thread 0x2b6cd9332060 (LWP 3931))
----------- .xsession-errors (246353 sec old) --------------------- WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 STAT: VOBU 1808 at 717MB, 1 PGCS WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: unknown mpeg2 aspect ratio 1 WARN: u ...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 346401 ***