After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 642552 - crash in Epiphany: Yes, I was clearing All ...
crash in Epiphany: Yes, I was clearing All ...
Status: RESOLVED DUPLICATE of bug 606933
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.30.x
Other All
: Normal critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-02-17 10:28 UTC by dstudio101
Modified: 2011-02-17 11:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description dstudio101 2011-02-17 10:28:34 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

Thread 1 (Thread 0x7f3e708039c0 (LWP 14609))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    at /tmp/buildd/glib2.0-2.28.0/./glib/gspawn.c line 392
  • #2 g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.28.0/./glib/gspawn.c line 706
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 IA__gtk_tree_model_get_iter_first
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtktreemodel.c line 1086
  • #6 clear_all_dialog_response_cb
    at pdm-dialog.c line 289
  • #7 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gclosure.c line 767
  • #8 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3252
  • #9 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 2983
  • #10 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3040
  • #11 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gclosure.c line 767
  • #12 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3252
  • #13 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 2983
  • #14 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3040
  • #15 gtk_real_button_released
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkbutton.c line 1725
  • #16 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gclosure.c line 767
  • #17 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3182
  • #18 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 2983
  • #19 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3040
  • #20 gtk_button_button_release
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkbutton.c line 1617
  • #21 _gtk_marshal_BOOLEAN__BOXED
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkmarshalers.c line 84
  • #22 g_closure_invoke
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gclosure.c line 767
  • #23 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3290
  • #24 g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 2993
  • #25 g_signal_emit
    at /tmp/buildd/glib2.0-2.28.0/./gobject/gsignal.c line 3040
  • #26 gtk_widget_event_internal
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkwidget.c line 4943
  • #27 IA__gtk_propagate_event
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkmain.c line 2442
  • #28 IA__gtk_main_do_event
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkmain.c line 1647
  • #29 gdk_event_dispatch
    at /scratch/build-area/gtk+2.0-2.20.1/gdk/x11/gdkevents-x11.c line 2372
  • #30 g_main_dispatch
    at /tmp/buildd/glib2.0-2.28.0/./glib/gmain.c line 2440
  • #31 g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.28.0/./glib/gmain.c line 3013
  • #32 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.28.0/./glib/gmain.c line 3091
  • #33 g_main_loop_run
    at /tmp/buildd/glib2.0-2.28.0/./glib/gmain.c line 3299
  • #34 IA__gtk_main
    at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkmain.c line 1219
  • #35 main
    at ephy-main.c line 741

	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'
--------------------------------------------------
Comment 1 Akhil Laddha 2011-02-17 11:18:01 UTC
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 ***