GNOME Bugzilla – Bug 460145
crash in Epiphany Web Browser: Updating the Adblock fil...
Last modified: 2007-07-25 09:09:37 UTC
Version: 2.18.3 What were you doing when the application crashed? Updating the Adblock filters from the website. Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.21-2-amd64 #1 SMP Tue Jul 10 21:39:38 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 531173376 vsize: 531173376 resident: 70365184 share: 31621120 rss: 70365184 rss_rlim: 18446744073709551615 CPU usage: start_time: 1185351625 rtime: 789 utime: 744 stime: 45 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47929441696608 (LWP 7235)] [New Thread 1140881744 (LWP 7252)] [New Thread 1107310928 (LWP 7251)] [New Thread 1090525520 (LWP 7237)] [New Thread 1082132816 (LWP 7236)] 0x00002b976d071b0f in waitpid () from /lib/libpthread.so.0
+ Trace 150395
Thread 1 (Thread 47929441696608 (LWP 7235))
----------- .xsession-errors (6 sec old) --------------------- /home/neil/~/Mail/inbox: chdir: No such file or directory /home/neil/~/Mail/sent: chdir: No such file or directory /home/neil/~/Mail/draft: chdir: No such file or directory /home/neil/~/Mail/queue: chdir: No such file or directory /home/neil/~/Mail/trash: chdir: No such file or directory (sylpheed:6546): LibSylph-WARNING **: Can't execute command: bogofilter (sylpheed:6546): LibSylph-WARNING **: Can't execute command: bogofilter ** (epiphany-browser:7235): WARNING **: Could not get rules file from filterg site sys:1: Warning: 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 ***