GNOME Bugzilla – Bug 543167
crash in Home Folder: I was trying to open a s...
Last modified: 2008-07-16 07:54:05 UTC
What were you doing when the application crashed? I was trying to open a samba shared folder. Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 83857408 vsize: 83857408 resident: 30793728 share: 16846848 rss: 30793728 rss_rlim: 4294967295 CPU usage: start_time: 1216155049 rtime: 344 utime: 320 stime: 24 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 0xb6a48710 (LWP 13217)] [New Thread 0xb4963b90 (LWP 13241)] (no debugging symbols found) 0xb7f53424 in __kernel_vsyscall ()
+ Trace 202926
Thread 1 (Thread 0xb6a48710 (LWP 13217))
----------- .xsession-errors --------------------- seahorse nautilus module initialized ** (nautilus:13149): WARNING **: Geen beschrijving gevonden voor MIME-type ‘x-directory/smb-share’ (bestand is ‘Dolumar’), gelieve dit door te geven aan de gnome-vfs mailing lijst. Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:13186): WARNING **: Geen beschrijving gevonden voor MIME-type ‘x-directory/smb-share’ (bestand is ‘SharedDocs’), gelieve dit door te geven aan de gnome-vfs mailing lijst. Initializing gnome-mount extension seahorse nautilus module initialized connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:13217): WARNING **: Hit unhandled case 38 (Service is niet beschikbaar) in fm_report_error_loading_directory ** (nautilus:13217): WARNING **: Geen beschrijving gevonden voor MIME-type ‘x-directory/smb-share’ (bestand is ‘SharedDocs’), gelieve dit door te geven aan de gnome-vfs mailing lijst. --------------------------------------------------
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 ***