GNOME Bugzilla – Bug 545687
crash in Home Folder: Estava acessando uma pas...
Last modified: 2008-07-31 17:30:00 UTC
What were you doing when the application crashed? Estava acessando uma pasta na rede Windows. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (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: Vista-Inspirate_1.0 Memory status: size: 96997376 vsize: 96997376 resident: 32657408 share: 17788928 rss: 32657408 rss_rlim: 4294967295 CPU usage: start_time: 1217509504 rtime: 1242 utime: 1110 stime: 132 cutime:2 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6ad6720 (LWP 3331)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 204268
Thread 1 (Thread 0xb6ad6720 (LWP 3331))
----------- .xsession-errors --------------------- (firefox-bin:4220): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (shares-admin:17064): Gtk-WARNING **: Unknown property: GtkComboBox.items ** (gnome-app-install:17384): WARNING **: return value of custom widget handler was not a GtkWidget /usr/lib/python2.5/site-packages/AppInstall/AppInstall.py:1269: GtkWarning: gtk_tree_model_sort_sort: assertion `tree_model_sort->default_sort_func != NULL' failed item.applications.set_default_sort_func(None) closing connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3331): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "ivan"), por favor notifique a lista de discussão do 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 ***