What were you doing when the application crashed?
I was trying to create access to read a file for one user, for a file that was on another user's Desktop. Just a text file.		


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:54:20 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 122187776 vsize: 0 resident: 122187776 share: 0 rss: 16183296 rss_rlim: 0
CPU usage: start_time: 1183963213 rtime: 0 utime: 63 stime: 0 cutime:57 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209124016 (LWP 5721)]
(no debugging symbols found)
0x0063b402 in __kernel_vsyscall ()

+ Trace 146653

----------- .xsession-errors ---------------------
(nautilus:5721): libgnomevfs-CRITICAL **: gnome_vfs_file_info_dup: assertion `orig != NULL' failed
Introspect error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the ne
Unable to connect to yum-updatesd...
(nautilus:5721): libgnomevfs-CRITICAL **: gnome_vfs_file_info_dup: assertion `orig != NULL' failed
** (nautilus:5721): CRITICAL **: nautilus_launch_show_file: assertion `!nautilus_file_needs_slow_mime_type (file)' failed
** (nautilus:5721): CRITICAL **: nautilus_launch_show_file: assertion `!nautilus_file_needs_slow_mime_type (file)' failed
** ERROR **: file nautilus-file.c: line 295 (add_to_link_hash_table_list): assertion failed: (g_list_find (list, file) == NULL)
aborting...
** (bug-buddy:5893): WARNING **: Couldn't load icon for Open Folder
--------------------------------------------------