GNOME Bugzilla – Bug 471474
crash in Epiphany Web Browser: Starting from a fresh la...
Last modified: 2007-08-30 00:00:41 UTC
Version: 2.18.3 What were you doing when the application crashed? Starting from a fresh launch of Epiphany (home page about:blank): tools -> adblock editor select "Ruleset.G" tab click on the update button crash Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-1-686 #1 SMP Sun Jul 29 14:37:42 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 106434560 vsize: 106434560 resident: 32849920 share: 21258240 rss: 32849920 rss_rlim: 4294967295 CPU usage: start_time: 1188409000 rtime: 151 utime: 136 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1242003776 (LWP 7361)] [New Thread -1294398576 (LWP 7369)] [New Thread -1286005872 (LWP 7368)] [New Thread -1277613168 (LWP 7367)] [New Thread -1269220464 (LWP 7366)] [New Thread -1260827760 (LWP 7365)] [New Thread -1249145968 (LWP 7362)] 0xffffe410 in ?? ()
+ Trace 158800
----------- .xsession-errors --------------------- Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** (epiphany-browser:3401): WARNING **: Could not get nsIScriptError ** (epiphany-browser:3401): WARNING **: Could not get nsIScriptError ** (epiphany-browser:3401): WARNING **: Could not get rules file from filterg site (epiphany-browser:3401): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed Failed to read a valid object file image from memory. ** (epiphany-browser:7361): WARNING **: Could not get rules file from filterg site (epiphany-browser:7361): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed Failed to read a valid object file image from memory. --------------------------------------------------
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 ***