GNOME Bugzilla – Bug 535499
crash in Open Folder: accessing the keyring to...
Last modified: 2008-05-29 15:28:23 UTC
Version: 2.20.0 What were you doing when the application crashed? accessing the keyring to store a password to access a Samba share from nautilus Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 97886208 vsize: 97886208 resident: 24866816 share: 16490496 rss: 24866816 rss_rlim: 4294967295 CPU usage: start_time: 1212071090 rtime: 252 utime: 240 stime: 12 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 0xb6b39720 (LWP 12461)] (no debugging symbols found) 0xb7ef0424 in __kernel_vsyscall ()
+ Trace 198995
Thread 1 (Thread 0xb6b39720 (LWP 12461))
----------- .xsession-errors (86 sec old) --------------------- CALLBACK: save-authentication!!! warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib/gnome-vfs-2.0/modules/libfile.so" is not at the expected address (wrong library or version mismatch?) Error while mapping shared library sections: /usr/lib/nautilus/extensions-1.0/libnautilus-gst-shares.so: No such file or directory. Error while mapping shared library sections: /usr/lib/liboobs-1.so.3: No such file or directory. Initializing gnome-mount extension seahorse nautilus module initialized Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:12461): WARNING **: No description found for mime type "x-directory/smb-share" (file is "TECHCommun%24"), please tell the gnome-vfs mailing list. --------------------------------------------------
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 ***