GNOME Bugzilla – Bug 543305
crash in Open Folder: Opening a Windows share
Last modified: 2008-07-16 17:05:15 UTC
Version: 2.20.0 What were you doing when the application crashed? Opening a Windows share 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: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 75935744 vsize: 75935744 resident: 17752064 share: 12369920 rss: 17752064 rss_rlim: 4294967295 CPU usage: start_time: 1216192013 rtime: 447 utime: 387 stime: 60 cutime:0 cstime: 1 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 0xb6b50720 (LWP 3028)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 203003
Thread 1 (Thread 0xb6b50720 (LWP 3028))
----------- .xsession-errors (7 sec old) --------------------- CALLBACK: fill-authentication!!! ** (nautilus:3028): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-o5dR4J/socket: Connection refused connection_message_func(): Callback CALLBACK: full-authentication!!! ** (nautilus:3028): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-o5dR4J/socket: Connection refused connection_message_func(): Callback CALLBACK: save-authentication!!! ** (nautilus:3028): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-o5dR4J/socket: Connection refused connection_message_func(): Callback CALLBACK: save-authentication!!! ** (nautilus:3028): WARNING **: couldn't connect to daemon at $GNOME_KEYRING_SOCKET: /tmp/keyring-o5dR4J/socket: Connection refused --------------------------------------------------
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 ***