GNOME Bugzilla – Bug 542938
crash in File Browser: stavo entrando in una ca...
Last modified: 2008-07-14 17:34:44 UTC
Version: 2.20.0 What were you doing when the application crashed? stavo entrando in una cartella della mia rete LAN... Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.23.17-vanilla #1 SMP Wed Apr 23 20:57:37 CEST 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: 99041280 vsize: 99041280 resident: 33353728 share: 18702336 rss: 33353728 rss_rlim: 4294967295 CPU usage: start_time: 1216048640 rtime: 1158 utime: 1048 stime: 110 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 0xb6b8a720 (LWP 4340)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 202793
Thread 1 (Thread 0xb6b8a720 (LWP 4340))
----------- .xsession-errors (33 sec old) --------------------- (synaptic:5486): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed (synaptic:5486): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed kbuildsycoca running... Reusing existing ksycoca /usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) current dist not found in meta-release file connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:4340): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «G»); avvisare cortesemente la mailing list di gnome-vfs. --------------------------------------------------
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 ***