GNOME Bugzilla – Bug 536395
crash in Open Folder:
Last modified: 2008-06-03 10:25:58 UTC
Version: 2.20.0 What were you doing when the application crashed? 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: Clearlooks Icon Theme: gnome Memory status: size: 78876672 vsize: 78876672 resident: 24031232 share: 15790080 rss: 24031232 rss_rlim: 4294967295 CPU usage: start_time: 1212473990 rtime: 433 utime: 368 stime: 65 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 0xb6c2b720 (LWP 3892)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199469
Thread 1 (Thread 0xb6c2b720 (LWP 3892))
----------- .xsession-errors (15 sec old) --------------------- (evolution:16348): gtkhtml-WARNING **: Cannot create spell dictionary instance (iid:OAFIID:GNOME_Spell_Dictionary:0.3) (evolution:16348): Bonobo-WARNING **: Activation exception 'Failed to activate 'OAFIID:GNOME_Spell_Control:0.3'' (evolution:16348): e-data-server-ui-WARNING **: Unable to find password(s) in keyring (Keyring reports: No matching results) connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: full-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! --------------------------------------------------
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 ***