GNOME Bugzilla – Bug 468073
crash in Epiphany Web Browser: I was trying to update t...
Last modified: 2007-08-19 23:46:53 UTC
Version: 2.18.3 What were you doing when the application crashed? I was trying to update the filter.g.set in the adblock extentions i got from installing epiphany-extentions Distribution: Unknown Gnome Release: 2.18.3 2007-07-07 (Archlinux) BugBuddy Version: 2.18.1 System: Linux 2.6.22-ck #1 SMP PREEMPT Fri Aug 10 18:34:41 IST 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: 132456448 vsize: 132456448 resident: 43536384 share: 29114368 rss: 43536384 rss_rlim: 4294967295 CPU usage: start_time: 1187479859 rtime: 462 utime: 384 stime: 78 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 -1241478400 (LWP 26302)] [New Thread -1317934192 (LWP 26312)] [New Thread -1309541488 (LWP 26311)] [New Thread -1301148784 (LWP 26310)] [New Thread -1292756080 (LWP 26309)] [New Thread -1284338800 (LWP 26307)] [New Thread -1273062512 (LWP 26305)] [New Thread -1264649328 (LWP 26304)] 0xb7f5c410 in __kernel_vsyscall ()
+ Trace 156242
Thread 1 (Thread -1241478400 (LWP 26302))
----------- .xsession-errors (32 sec old) --------------------- ** (epiphany:26271): WARNING **: Could not get rules file from filterg site sys:1: Warning: g_strsplit: assertion `string != NULL' failed (epiphany:26302): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:26302): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:26302): libgnomevfs-WARNING **: Failed to create service browser: Bad state ** (epiphany:26302): 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 ***