GNOME Bugzilla – Bug 531073
crash in Open Folder: accessing a network shar...
Last modified: 2008-05-02 23:20:52 UTC
Version: 2.20.0 What were you doing when the application crashed? accessing a network 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 Sat Apr 19 00:37:55 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: Crux Memory status: size: 86167552 vsize: 86167552 resident: 31535104 share: 16658432 rss: 31535104 rss_rlim: 4294967295 CPU usage: start_time: 1209733185 rtime: 678 utime: 431 stime: 247 cutime:0 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 0xb6bc2720 (LWP 3800)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196685
Thread 1 (Thread 0xb6bc2720 (LWP 3800))
----------- .xsession-errors --------------------- Window manager warning: Failed to read saved session file /home/malaphus/.metacity/sessions/default0.ms: Failed to open file '/home/malaphus/.metacity/sessions/default0.ms': No such file or directory 11 Initializing gnome-mount extension seahorse nautilus module initialized (gnome-panel:3798): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -37 and height 26 closing (gnome-terminal:4366): Vte-WARNING **: No handler for control sequence `device-control-string' defined. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3800): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Radio%20Database"), 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 ***