GNOME Bugzilla – Bug 461361
crash in Epiphany Web Browser: I was trying to update r...
Last modified: 2007-07-29 11:49:45 UTC
Version: 2.18.3 What were you doing when the application crashed? I was trying to update rules in the Ablock extension 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-33.fc7 #1 SMP Mon Jul 23 17:33:07 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: nuoveXT.2.2 Memory status: size: 164327424 vsize: 164327424 resident: 48984064 share: 35872768 rss: 48984064 rss_rlim: 4294967295 CPU usage: start_time: 1185671344 rtime: 556 utime: 495 stime: 61 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 -1209035040 (LWP 2571)] [New Thread -1267475568 (LWP 2573)] [New Thread -1256985712 (LWP 2572)] (no debugging symbols found) 0x0012d402 in __kernel_vsyscall ()
+ Trace 151266
Thread 1 (Thread -1209035040 (LWP 2571))
----------- .xsession-errors --------------------- localuser:jclemon being added to access control list SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2390 Unable to open desktop file /usr/share/applications/openoffice.org-1.9-writer.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-impress.desktop for panel launcher: No such file or directory Unable to open desktop file /usr/share/applications/openoffice.org-1.9-calc.desktop for panel launcher: No such file or directory ** (epiphany:2571): WARNING **: Could not get rules file from filterg site (epiphany:2571): 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 ***