GNOME Bugzilla – Bug 542288
crash in File Browser:
Last modified: 2008-07-10 02:06:44 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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Crashbit Memory status: size: 152489984 vsize: 152489984 resident: 35151872 share: 21372928 rss: 35151872 rss_rlim: 4294967295 CPU usage: start_time: 1215647376 rtime: 200 utime: 185 stime: 15 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 0xb6ba8720 (LWP 9288)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 202444
Thread 1 (Thread 0xb6ba8720 (LWP 9288))
----------- .xsession-errors (10 sec old) --------------------- ** (gnome-screensaver-preferences:7945): DEBUG: Found best visual for GL: 0x25 ** Message: Error: Impossibile leggere dalla risorsa. gstgnomevfssrc.c(683): gst_gnome_vfs_src_create (): /play/source: Failed to read data: Parametri non validi (nautilus:4041): GLib-GObject-WARNING **: instance with invalid (NULL) class pointer (nautilus:4041): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed ** (nautilus:4041): CRITICAL **: nautilus_file_unref: assertion `NAUTILUS_IS_FILE (file)' failed seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:9288): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «all»); avvisare cortesemente la mailing list di gnome-vfs. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***