GNOME Bugzilla – Bug 468585
crash in Epiphany Web Bookmarks: updating adblock Filters...
Last modified: 2007-08-20 22:48:05 UTC
Version: 2.18.3 What were you doing when the application crashed? updating adblock Filterset.G 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: Neu Memory status: size: 124325888 vsize: 124325888 resident: 39772160 share: 23584768 rss: 39772160 rss_rlim: 4294967295 CPU usage: start_time: 1187628575 rtime: 136 utime: 128 stime: 8 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 -1241696560 (LWP 8788)] [New Thread -1307440240 (LWP 8810)] [New Thread -1299047536 (LWP 8809)] [New Thread -1290654832 (LWP 8808)] [New Thread -1273844848 (LWP 8807)] [New Thread -1282237552 (LWP 8799)] [New Thread -1262769264 (LWP 8797)] [New Thread -1246602352 (LWP 8789)] 0xb7f4f410 in __kernel_vsyscall ()
+ Trace 156620
Thread 1 (Thread -1241696560 (LWP 8788))
----------- .xsession-errors --------------------- (epiphany:8664): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed (epiphany:8788): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:8788): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany:8788): libgnomevfs-WARNING **: Failed to create service browser: Bad state ** (epiphany:8788): WARNING **: Could not get rules file from filterg site (epiphany:8788): GLib-CRITICAL **: 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 ***