GNOME Bugzilla – Bug 541810
crash in Open Folder: Trying to connect to the...
Last modified: 2008-07-06 22:06:24 UTC
Version: 2.20.0 What were you doing when the application crashed? Trying to connect to the Maxtor shared network drive... crashes every time on directories that are password protected. Network drive uses Samba. Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (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: Clearlooks Icon Theme: gnome Memory status: size: 76107776 vsize: 76107776 resident: 24662016 share: 14741504 rss: 24662016 rss_rlim: 4294967295 CPU usage: start_time: 1215356551 rtime: 290 utime: 274 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 0xb6b29940 (LWP 8348)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 202186
Thread 1 (Thread 0xb6b29940 (LWP 8348))
----------- .xsession-errors (34 sec old) --------------------- Initializing gnome-mount extension connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! seahorse nautilus module initialized Initializing gnome-mount extension ** (totem:8382): WARNING **: Unknown codec ID 86022, please add here --------------------------------------------------
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 ***