GNOME Bugzilla – Bug 484172
crash in Computer: CTRL+F then i typed "ams...
Last modified: 2007-10-07 11:19:44 UTC
Version: 2.18.3 What were you doing when the application crashed? CTRL+F then i typed "amsn" then enter 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: 100225024 vsize: 100225024 resident: 48001024 share: 20914176 rss: 48001024 rss_rlim: 4294967295 CPU usage: start_time: 1191686423 rtime: 158 utime: 145 stime: 13 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 -1208346912 (LWP 3723)] [New Thread -1242436720 (LWP 3733)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 168351
Thread 2 (Thread -1242436720 (LWP 3733))
----------- .xsession-errors --------------------- (bug-buddy:3713): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:3713): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:3713): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:3713): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Initializing nautilus-flac-converter extension Initializing nautilus-image-converter extension seahorse nautilus module initialized Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension (nautilus:3723): GLib-CRITICAL **: g_utf8_strdown: assertion `str != 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 454799 ***