GNOME Bugzilla – Bug 538376
crash in Open Folder:
Last modified: 2008-06-15 10:09:47 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: black-white_2-Neon Memory status: size: 77463552 vsize: 77463552 resident: 27217920 share: 15429632 rss: 27217920 rss_rlim: 4294967295 CPU usage: start_time: 1213478539 rtime: 11905 utime: 10487 stime: 1418 cutime:690 cstime: 82 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 0xb6b51720 (LWP 3667)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200456
Thread 1 (Thread 0xb6b51720 (LWP 3667))
----------- .xsession-errors (199 sec old) --------------------- ** Message: Error: Resource not found. gstfilesrc.c(977): gst_file_src_start (): /play/source: No such file "/home/job/.local/share/Trash/files/soundtest_menu.mpg" totem-video-thumbnailer couln't open file 'file:///home/job/.local/share/Trash/files/soundtest_menu.mpg' Reason: Location not found.. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3667): WARNING **: No description found for mime type "x-directory/smb-share" (file is "My%20Documents"), please tell the gnome-vfs mailing list. No accelerated IMDCT transform found gnome-video-thumbnailer couln't process file: 'file:///mnt/windows2/Football/MilanPool2ndhalf.mpg' Reason: Took too much time to process. --------------------------------------------------
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 ***