GNOME Bugzilla – Bug 514748
crash in Open Folder: I wanted to search ".mp3...
Last modified: 2008-02-07 09:21:43 UTC
Version: 2.18.3 What were you doing when the application crashed? I wanted to search ".mp3" word on my desktop. 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.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 183988224 vsize: 183988224 resident: 44609536 share: 20996096 rss: 44609536 rss_rlim: 4294967295 CPU usage: start_time: 1202303061 rtime: 318 utime: 218 stime: 100 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208498464 (LWP 24984)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 188285
Thread 1 (Thread -1208498464 (LWP 24984))
----------- .xsession-errors --------------------- warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib/libpoppler-glib.so.1" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations (bug-buddy:24975): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:24975): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:24975): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:24975): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:24984): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed --------------------------------------------------
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 436071 ***