GNOME Bugzilla – Bug 492802
crash in Open Folder: File Browser
Last modified: 2007-11-03 01:43:26 UTC
Version: 2.18.3 What were you doing when the application crashed? File Browser Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 127483904 vsize: 127483904 resident: 55709696 share: 28254208 rss: 55709696 rss_rlim: 4294967295 CPU usage: start_time: 1193871298 rtime: 95965 utime: 39734 stime: 56231 cutime:10 cstime: 5 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208400160 (LWP 2677)] [New Thread -1296000112 (LWP 24895)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 174678
Thread 2 (Thread -1296000112 (LWP 24895))
----------- .xsession-errors (23 sec old) --------------------- --- Hash table keys for warning below: --> file:///home/daniel (nautilus:24064): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2677): Gtk-CRITICAL **: gtk_action_group_remove_action: assertion `GTK_IS_ACTION_GROUP (action_group)' failed --- Hash table keys for warning below: --> file:///home/daniel (nautilus:24881): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above) (nautilus:2677): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed Xlib: unexpected async reply (sequence 0x3baee3)! --------------------------------------------------
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 454799 ***