GNOME Bugzilla – Bug 469002
crash in Epiphany Web Browser: nothing
Last modified: 2007-08-21 22:14:25 UTC
Version: 2.18.3 What were you doing when the application crashed? nothing Distribution: Unknown Gnome Release: 2.18.3 2007-07-07 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.22-ARCH #1 SMP PREEMPT Wed Aug 15 23:33:00 CEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70200000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 109727744 vsize: 109727744 resident: 35897344 share: 23842816 rss: 35897344 rss_rlim: 4294967295 CPU usage: start_time: 1187731377 rtime: 174 utime: 159 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' (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 -1241191680 (LWP 24695)] [New Thread -1254708336 (LWP 24700)] [New Thread -1244312688 (LWP 24699)] 0xb7fb6410 in __kernel_vsyscall ()
+ Trace 156959
Thread 1 (Thread -1241191680 (LWP 24695))
----------- .xsession-errors --------------------- Gtk-CRITICAL **:gtk_tree_view_column_cell_layout_pack_start: assertion `! gtk_tree_view_column_get_cell_info (column, cell)' failed Unmatched element: source ** (gnome-help:16767): WARNING **: AT_SPI_REGISTRY was not started at session startup. ** (gnome-help:16767): WARNING **: IOR not set. ** (gnome-help:16767): WARNING **: Could not locate registry ** (epiphany:24695): CRITICAL **: ephy_window_get_active_tab: assertion `EPHY_IS_WINDOW (window)' failed ** (grdesktop:27136): WARNING **: Unable to find keyboad definitions: /usr/local/share/rdesktop/keymaps/ ** (epiphany:24695): WARNING **: Could not get rules file from filterg site sys:1: Warning: g_strsplit: assertion `string != 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 452119 ***