GNOME Bugzilla – Bug 642552
crash in Epiphany: Yes, I was clearing All ...
Last modified: 2011-02-17 11:18:01 UTC
Version: 2.30.6 What were you doing when the application crashed? Yes, I was clearing All Personal Data -- checked all check boxes. when I click the clear button -- this shows up. Distribution: Debian wheezy/sid Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10904000 Selinux: No Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 663437312 vsize: 663437312 resident: 60416000 share: 35999744 rss: 60416000 rss_rlim: 18446744073709551615 CPU usage: start_time: 1297937423 rtime: 514 utime: 432 stime: 82 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' [Thread debugging using libthread_db enabled] [New Thread 0x7f3e5be8a700 (LWP 14612)] [New Thread 0x7f3e5c68b700 (LWP 14611)] 0x00007f3e6a389b4d in waitpid () from /lib/libpthread.so.0
+ Trace 225999
Thread 1 (Thread 0x7f3e708039c0 (LWP 14609))
Inferior 1 [process 14609] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (35 sec old) --------------------- ** Message: console message: @1: Refused to set unsafe header "Connection" ** Message: console message: @1: Refused to set unsafe header "Connection" (epiphany-browser:10959): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed Launching a SCIM daemon with Socket FrontEnd... Loading simple Config module ... Creating backend ... Loading socket FrontEnd module ... Starting SCIM as daemon ... GTK Panel of SCIM 1.4.9 (epiphany-browser:14609): GLib-GObject-WARNING **: invalid cast from `PrefsDialog' to `PdmDialog' --------------------------------------------------
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 bug 606933 ***