GNOME Bugzilla – Bug 460576
crash in Epiphany Web Browser: I was updating filterset...
Last modified: 2007-07-26 13:58:48 UTC
Version: 2.18.3 What were you doing when the application crashed? I was updating filtersetG, for the adblock extension Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 131796992 vsize: 131796992 resident: 36794368 share: 22515712 rss: 36794368 rss_rlim: 4294967295 CPU usage: start_time: 1185457163 rtime: 339 utime: 307 stime: 32 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 -1208146208 (LWP 3190)] [New Thread -1230091376 (LWP 3194)] [New Thread -1219601520 (LWP 3193)] (no debugging symbols found) 0x00f9b402 in __kernel_vsyscall ()
+ Trace 150686
Thread 1 (Thread -1208146208 (LWP 3190))
----------- .xsession-errors (8 sec old) --------------------- ** Message: <info> Vous êtes connecté au réseau sans fil « ottignies ». Loading "installonlyn" plugin Importing additional filelist information Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/smart/interfaces/gtk/interactive.py", line 188, in delete gtk.main_quit() RuntimeError: called outside of a mainloop ** (epiphany:3190): WARNING **: Could not get rules file from filterg site (epiphany:3190): 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 ***