GNOME Bugzilla – Bug 487091
crash in Epiphany Web Bookmarks: aggiornando le regole di...
Last modified: 2007-10-16 09:52:11 UTC
Version: 2.18.3 What were you doing when the application crashed? aggiornando le regole di adblock Distribution: Slackware Slackware 11.0.0 Gnome Release: 2.18.1 2007-05-10 (Dropline GNOME) BugBuddy Version: 2.18.1 System: Linux 2.6.9 #9 SMP Mon Feb 26 18:08:38 CET 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled GTK+ Theme: TwoEighteen Icon Theme: Gion Memory status: size: 126509056 vsize: 126509056 resident: 63496192 share: 75993088 rss: 63496192 rss_rlim: 4294967295 CPU usage: start_time: 1192524098 rtime: 8830 utime: 8275 stime: 555 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 16384 (LWP 15825)] [New Thread 32769 (LWP 17303)] [New Thread 16386 (LWP 17304)] [New Thread 32771 (LWP 18904)] [New Thread 131081 (LWP 23230)] [New Thread 147466 (LWP 23231)] 0x411e362b in waitpid () from /lib/libpthread.so.0
+ Trace 170529
----------- .xsession-errors --------------------- end from FAM server connection end from FAM server connection end from FAM server connection end from FAM server connection ** (epiphany:15825): WARNING **: Could not get rules file from filterg site (epiphany:15825): GLib-CRITICAL **: g_strsplit: assertion `string != NULL' failed (bug-buddy:27866): gnome-vfs-modules-WARNING **: Could not initialize inotify end from FAM server connection end from FAM server connection end from FAM server connection end from FAM server connection --------------------------------------------------
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 ***