GNOME Bugzilla – Bug 536580
crash in Open Folder: Opening a windows networ...
Last modified: 2008-06-04 14:27:26 UTC
Version: 2.20.0 What were you doing when the application crashed? Opening a windows network share/folder Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 462405632 vsize: 462405632 resident: 38473728 share: 18243584 rss: 38473728 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212567164 rtime: 256 utime: 228 stime: 28 cutime:0 cstime: 0 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 0x2ae66c264240 (LWP 2984)] (no debugging symbols found) 0x00002ae665a5aedf in waitpid () from /lib/libpthread.so.0
+ Trace 199547
Thread 1 (Thread 0x2ae66c264240 (LWP 2984))
----------- .xsession-errors (7 sec old) --------------------- Error: No running window found (liferea:3700): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed (gnome-terminal:3775): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:3999): Vte-WARNING **: No handler for control sequence `device-control-string' defined. (gnome-terminal:4065): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:2984): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory ** (nautilus:2984): WARNING **: Hit unhandled case 38 (Service not available) in fm_report_error_loading_directory ** (nautilus:2984): WARNING **: No description found for mime type "x-directory/smb-share" (file is "kiekjes"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***