GNOME Bugzilla – Bug 545747
crash in Home Folder: nautilus em smb://
Last modified: 2008-08-01 08:16:42 UTC
What were you doing when the application crashed? nautilus em smb:// Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 78069760 vsize: 78069760 resident: 27029504 share: 15925248 rss: 27029504 rss_rlim: 4294967295 CPU usage: start_time: 1217525659 rtime: 183 utime: 175 stime: 8 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 0xb6ade720 (LWP 15844)] [New Thread 0xb59ffb90 (LWP 15881)] [New Thread 0xb6327b90 (LWP 15879)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 204300
Thread 1 (Thread 0xb6ade720 (LWP 15844))
----------- .xsession-errors (7 sec old) --------------------- CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! warning: .dynamic section for "/usr/lib/nautilus/extensions-1.0/libtotem-properties-page.so" is not at the expected address (wrong library or version mismatch?) seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:15804): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "home"), por favor notifique a lista de discussão do gnome-vfs. seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:15844): WARNING **: Não foi encontrada descrição para o tipo MIME "x-directory/smb-share" (o arquivo é "home"), por favor notifique a lista de discussão do gnome-vfs. --------------------------------------------------
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 ***