GNOME Bugzilla – Bug 468730
crash in Epiphany Web Bookmarks: Updating filterset for a...
Last modified: 2007-08-21 08:46:25 UTC
Version: 2.18.3 What were you doing when the application crashed? Updating filterset for adblock extension Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-kamikaze5.070808 #1 SMP PREEMPT Wed Aug 8 14:38:54 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: MurrinaOrange Icon Theme: Tangerine Memory status: size: 515051520 vsize: 515051520 resident: 76386304 share: 29159424 rss: 76386304 rss_rlim: 18446744073709551615 CPU usage: start_time: 1187669328 rtime: 1839 utime: 1589 stime: 250 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 47473524869984 (LWP 12363)] [New Thread 1124096336 (LWP 14337)] [New Thread 1115703632 (LWP 14336)] [New Thread 1090525520 (LWP 12365)] [New Thread 1082132816 (LWP 12364)] 0x00002b2d46344c7f in waitpid () from /lib/libpthread.so.0
+ Trace 156733
Thread 1 (Thread 47473524869984 (LWP 12363))
----------- .xsession-errors (18 sec old) --------------------- ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** (epiphany-browser:12363): WARNING **: Could not get rules file from filterg site (epiphany-browser:12363): 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 ***