GNOME Bugzilla – Bug 459968
crash in Epiphany Web Browser: I was udapting Adblock f...
Last modified: 2007-07-24 20:26:37 UTC
Version: 2.18.3 What were you doing when the application crashed? I was udapting Adblock for epiphany Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.1-27.fc7 #1 SMP Tue Jul 17 17:13:26 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Clearlooks Memory status: size: 170799104 vsize: 170799104 resident: 54861824 share: 36098048 rss: 54861824 rss_rlim: 4294967295 CPU usage: start_time: 1185296111 rtime: 909 utime: 862 stime: 47 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 -1209088288 (LWP 19855)] [New Thread -1290798192 (LWP 19871)] [New Thread -1256596592 (LWP 19867)] [New Thread -1244693616 (LWP 19857)] [New Thread -1234203760 (LWP 19856)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 150268
Thread 1 (Thread -1209088288 (LWP 19855))
----------- .xsession-errors --------------------- ** 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) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** (epiphany:19855): WARNING **: Could not get rules file from filterg site (epiphany:19855): 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 ***