GNOME Bugzilla – Bug 457872
crash in Epiphany Web Browser: adblock editor-trying to...
Last modified: 2007-07-19 14:20:41 UTC
Version: 2.18.3 What were you doing when the application crashed? adblock editor-trying to refresh Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-nvidia #1 SMP Wed Jul 18 09:26:17 IST 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Mist Memory status: size: 177328128 vsize: 177328128 resident: 66441216 share: 26468352 rss: 66441216 rss_rlim: 4294967295 CPU usage: start_time: 1184741154 rtime: 21362 utime: 19891 stime: 1471 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 -1241151808 (LWP 3477)] [New Thread -1301984368 (LWP 7552)] [New Thread -1274696816 (LWP 7547)] [New Thread -1283089520 (LWP 5067)] [New Thread -1266304112 (LWP 5066)] [New Thread -1257911408 (LWP 3485)] [New Thread -1249518704 (LWP 3481)] (no debugging symbols found) 0xb7f8d410 in __kernel_vsyscall ()
+ Trace 148770
----------- .xsession-errors (6 sec old) --------------------- (no Display connection). ERROR: Unable to assign attribute XVideoSyncToDisplay specified on line 49 of configuration file '/home/prakash/.nvidia-settings-rc' (no Display connection). ** Message: drive = 0 ** Message: volume = 0 ** (epiphany-browser:3477): WARNING **: Could not get changelog from filterg site ** (epiphany-browser:3477): WARNING **: Could not get rules file from filterg site (epiphany-browser:3477): 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 ***