GNOME Bugzilla – Bug 469211
crash in Epiphany Web Browser: updating ad blocker exte...
Last modified: 2007-08-22 12:02:30 UTC
Version: 2.18.3 What were you doing when the application crashed? updating ad blocker extension filter list Distribution: Debian 4.0 Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-1-k7 #1 SMP Sun Jul 29 15:15:55 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 219693056 vsize: 219693056 resident: 60661760 share: 28102656 rss: 60661760 rss_rlim: 4294967295 CPU usage: start_time: 1187783614 rtime: 1138 utime: 1041 stime: 97 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1242220864 (LWP 8316)] [New Thread -1316836464 (LWP 8346)] [New Thread -1308443760 (LWP 8334)] [New Thread -1325229168 (LWP 8333)] [New Thread -1350444144 (LWP 8332)] [New Thread -1342051440 (LWP 8331)] [New Thread -1274872944 (LWP 8330)] [New Thread -1283265648 (LWP 8329)] [New Thread -1265415280 (LWP 8319)] [New Thread -1249264752 (LWP 8317)] (no debugging symbols found) 0xffffe410 in ?? ()
+ Trace 157108
----------- .xsession-errors --------------------- Failed to read a valid object file image from memory. ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (epiphany-browser:8316): WARNING **: Could not get rules file from filterg site sys:1: Warning: 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 ***