GNOME Bugzilla – Bug 467444
crash in Epiphany Web Browser: Browser crashed, when I ...
Last modified: 2007-08-16 21:37:19 UTC
Version: 2.18.3 What were you doing when the application crashed? Browser crashed, when I clicked update Filterset.G in Adblock editor Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-bootsplash #2 SMP PREEMPT Thu Jul 19 23:37:57 EEST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Nuvola Memory status: size: 77189120 vsize: 77189120 resident: 30228480 share: 20619264 rss: 30228480 rss_rlim: 4294967295 CPU usage: start_time: 1187295969 rtime: 168 utime: 156 stime: 12 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 -1242843456 (LWP 13037)] [New Thread -1266881648 (LWP 13040)] [New Thread -1258488944 (LWP 13039)] [New Thread -1248298096 (LWP 13038)] (no debugging symbols found) 0xb7f147f2 in ?? () from /lib/ld-linux.so.2
+ Trace 155760
Thread 1 (Thread -1242843456 (LWP 13037))
----------- .xsession-errors --------------------- (gnome-terminal:2957): Vte-WARNING **: Ohjaussarjalle "device-control-string" ei ole määritelty käsittelintä. (epiphany-browser:13037): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany-browser:13037): libgnomevfs-WARNING **: Failed to create service browser: Bad state (epiphany-browser:13037): libgnomevfs-WARNING **: Failed to create service browser: Bad state ** (epiphany-browser:13037): WARNING **: Could not get rules file from filterg site (epiphany-browser:13037): 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 ***