GNOME Bugzilla – Bug 538954
crash in Computer: try to connect to a shar...
Last modified: 2008-06-18 13:37:38 UTC
Version: 2.20.0 What were you doing when the application crashed? try to connect to a share folder on windows XP. 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 Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaCandy Icon Theme: gartoon Memory status: size: 60424192 vsize: 60424192 resident: 28037120 share: 15773696 rss: 28037120 rss_rlim: 4294967295 CPU usage: start_time: 1213795420 rtime: 834 utime: 800 stime: 34 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 0xb6ba9720 (LWP 3595)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 200755
Thread 1 (Thread 0xb6ba9720 (LWP 3595))
----------- .xsession-errors --------------------- CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! (bug-buddy:3587): libebook-WARNING **: Can't find installed BookFactories (bug-buddy:3587): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed Initializing gnome-mount extension Initializing nautilus-open-terminal extension ** (nautilus:3595): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « Mes%20documents »), veuillez avertir la liste de diffusion de gnome-vf --------------------------------------------------
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 ***