GNOME Bugzilla – Bug 535352
crash in Open Folder: opening a network smb sh...
Last modified: 2008-05-28 22:50:15 UTC
Version: 2.20.0 What were you doing when the application crashed? opening a network smb share Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (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: gnome Memory status: size: 88895488 vsize: 88895488 resident: 34017280 share: 16019456 rss: 34017280 rss_rlim: 4294967295 CPU usage: start_time: 1212010109 rtime: 121 utime: 113 stime: 8 cutime:0 cstime: 0 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 0xb6bce720 (LWP 9527)] [New Thread 0xb45fdb90 (LWP 9549)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 198907
Thread 1 (Thread 0xb6bce720 (LWP 9527))
----------- .xsession-errors --------------------- gstffmpegdemux.c(1103): gst_ffmpegdemux_open (): /play/decodebin0/ffdemux_swf0: Unhandled error code received ** Message: Error: GStreamer encountered a general supporting library error. gstffmpegdemux.c(1103): gst_ffmpegdemux_open (): /play/decodebin0/ffdemux_swf0: Unhandled error code received connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:9527): WARNING **: No description found for mime type "x-directory/smb-share" (file is "chadmichael"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***