GNOME Bugzilla – Bug 522997
crash in Open Folder: searching windows networ...
Last modified: 2008-03-19 00:08:39 UTC
Version: 2.20.0 What were you doing when the application crashed? searching windows network Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24.xps #2 SMP Tue Feb 19 22:44:17 CST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: gnome Memory status: size: 82157568 vsize: 82157568 resident: 27525120 share: 15794176 rss: 27525120 rss_rlim: 4294967295 CPU usage: start_time: 1205770538 rtime: 231 utime: 215 stime: 16 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 0xb6bad720 (LWP 10815)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 192700
Thread 1 (Thread 0xb6bad720 (LWP 10815))
----------- .xsession-errors --------------------- (nautilus:5193): libgnomevfs-CRITICAL **: gnome_vfs_uri_get_parent: assertion `uri != NULL' failed (nautilus:5193): libgnomevfs-CRITICAL **: gnome_vfs_uri_unref: assertion `uri != NULL' failed ** Message: <info> You are now connected to the wired network. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:10815): WARNING **: No description found for mime type "x-directory/smb-share" (file is "D"), please tell the gnome-vfs mailing list. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
I installed the -dbg packages and reproduced the error again, hope this helps, if you need more I'll help. Distribution: Debian lenny/sid Gnome Release: 2.22.0 2008-03-14 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.24.xps #2 SMP Tue Feb 19 22:44:17 CST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Crux Icon Theme: gnome Memory status: size: 66252800 vsize: 66252800 resident: 28680192 share: 16359424 rss: 28680192 rss_rlim: 4294967295 CPU usage: start_time: 1205882798 rtime: 221 utime: 203 stime: 18 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb6bf6720 (LWP 22017)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 192813
Thread 1 (Thread 0xb6bf6720 (LWP 22017))
----------- .xsession-errors --------------------- ** (nautilus:12175): WARNING **: No description found for mime type "x-directory/smb-share" (file is "D"), please tell the gnome-vfs mailing list. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:21190): WARNING **: No description found for mime type "x-directory/smb-share" (file is "D"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized (gnome-terminal:22066): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** (nautilus:22017): WARNING **: No description found for mime type "x-directory/smb-share" (file is "D"), please tell the gnome-vfs mailing list. --------------------------------------------------
Thanks, now I identified the bug. 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 ***