GNOME Bugzilla – Bug 475184
crash in Dictionary:
Last modified: 2007-09-12 22:22:51 UTC
Version: 2.18.1 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-1-amd64 #1 SMP Sun Jul 29 13:54:41 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 159875072 vsize: 159875072 resident: 17633280 share: 10674176 rss: 17633280 rss_rlim: 18446744073709551615 CPU usage: start_time: 1189359343 rtime: 22 utime: 16 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-dictionary' (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 47449521548816 (LWP 6855)] (no debugging symbols found) 0x00002b27ae936c45 in waitpid () from /lib/libpthread.so.0
+ Trace 161578
Thread 1 (Thread 47449521548816 (LWP 6855))
----------- .xsession-errors --------------------- (bug-buddy:6804): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:6804): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (epiphany-browser:6279): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:6279): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:6279): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (epiphany-browser:6279): Gtk-CRITICAL **: gtk_window_group_remove_window: assertion `GTK_IS_WINDOW_GROUP (window_group)' failed (gnome-dictionary:6855): GLib-CRITICAL **: g_strrstr_len: assertion `haystack != NULL' failed (gnome-dictionary:6855): GLib-CRITICAL **: g_string_append: assertion `val != NULL' failed --------------------------------------------------
*** This bug has been marked as a duplicate of 475183 ***