GNOME Bugzilla – Bug 532914
crash in Open Folder: This happens all the tim...
Last modified: 2008-05-13 09:52:22 UTC
Version: 2.20.0 What were you doing when the application crashed? This happens all the time when I browse a windows partition using nautilus. Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25.1 #1 Wed May 7 09:57:30 BST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 79101952 vsize: 79101952 resident: 42528768 share: 16125952 rss: 42528768 rss_rlim: 4294967295 CPU usage: start_time: 1210667184 rtime: 924 utime: 872 stime: 52 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 0xb6b6c720 (LWP 3050)] (no debugging symbols found) 0xb7f1a424 in __kernel_vsyscall ()
+ Trace 197606
Thread 1 (Thread 0xb6b6c720 (LWP 3050))
----------- .xsession-errors --------------------- ** (nautilus:2067): WARNING **: Possibly invalid new URI 'smb://fileserver/main/Technical 2006' This can cause subtle evils like #48423 ** (nautilus:2067): WARNING **: Possibly invalid new URI 'smb://fileserver/main/Technical 2006/PMT%20Screenshots' This can cause subtle evils like #48423 Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:3050): WARNING **: No description found for mime type "x-directory/smb-share" (file is "main"), please tell the gnome-vfs mailing list. ** (nautilus:3050): WARNING **: Possibly invalid new URI 'smb://fileserver/main/Technical 2006/' This can cause subtle evils like #48423 ** (nautilus:3050): WARNING **: Possibly invalid new URI 'smb://fileserver/main/Technical 2006/PMT Screenshots/' This can cause subtle evils like #48423 --------------------------------------------------
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 ***