Bug 639278 – crash in Epiphany Web Bookmarks: 在清除个人数据时全部选择，然后确定。

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 639278 - crash in Epiphany Web Bookmarks: 在清除个人数据时全部选择，然后确定。


Summary:	crash in Epiphany Web Bookmarks: 在清除个人数据时全部选择，然后确定。


Status:	RESOLVED DUPLICATE of bug 606933

Product:	epiphany
Classification:	Core
Component:	[obsolete] BugBuddyBugs
Version:	2.30.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Epiphany Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2011-01-12 03:03 UTC by jeff_jian
Modified:	2011-01-12 04:06 UTC

See Also:
GNOME target:	---
GNOME version:	2.29/2.30

Description jeff_jian 2011-01-12 03:03:59 UTC

Version: 2.30.6

What were you doing when the application crashed?
在清除个人数据时全部选择，然后确定。


Distribution: Debian 6.0
Gnome Release: 2.30.2 2010-11-12 (Debian)
BugBuddy Version: 2.30.0

System: Linux 2.6.34.8 #2 SMP Sun Jan 9 19:36:30 CST 2011 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10707000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: gnomebreakpad, canberra-gtk-module

Memory status: size: 895578112 vsize: 895578112 resident: 77770752 share: 28803072 rss: 77770752 rss_rlim: 18446744073709551615
CPU usage: start_time: 1294799516 rtime: 2517 utime: 2211 stime: 306 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/epiphany-browser'

[Thread debugging using libthread_db enabled]
[New Thread 0x7fd56b779710 (LWP 15508)]
[New Thread 0x7fd56c07a710 (LWP 15507)]
0x00007fd583188b4d in __libc_waitpid (pid=17866, 
    stat_loc=<value optimized out>, options=0)
    at ../sysdeps/unix/sysv/linux/waitpid.c:41
	in ../sysdeps/unix/sysv/linux/waitpid.c

+ Trace 225498

Thread 1 (Thread 0x7fd5894de800 (LWP 15503))

#0 __libc_waitpid
at ../sysdeps/unix/sysv/linux/waitpid.c line 41
#1 IA__g_spawn_sync
at /scratch/build-area/glib2.0-2.24.2/glib/gspawn.c line 386
#2 IA__g_spawn_command_line_sync
at /scratch/build-area/glib2.0-2.24.2/glib/gspawn.c line 700
#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 IA__g_closure_invoke
at /scratch/build-area/glib2.0-2.24.2/gobject/gclosure.c line 767
#8 signal_emit_unlocked_R
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3248
#9 IA__g_signal_emit_valist
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 2981
#10 IA__g_signal_emit
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3038
#11 IA__g_closure_invoke
at /scratch/build-area/glib2.0-2.24.2/gobject/gclosure.c line 767
#12 signal_emit_unlocked_R
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3248
#13 IA__g_signal_emit_valist
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 2981
#14 IA__g_signal_emit
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3038
#15 gtk_real_button_released
at /scratch/build-area/gtk+2.0-2.20.1/gtk/gtkbutton.c line 1725
#16 IA__g_closure_invoke
at /scratch/build-area/glib2.0-2.24.2/gobject/gclosure.c line 767
#17 signal_emit_unlocked_R
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3178
#18 IA__g_signal_emit_valist
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 2981
#19 IA__g_signal_emit
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3038
#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 IA__g_closure_invoke
at /scratch/build-area/glib2.0-2.24.2/gobject/gclosure.c line 767
#23 signal_emit_unlocked_R
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3286
#24 IA__g_signal_emit_valist
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 2991
#25 IA__g_signal_emit
at /scratch/build-area/glib2.0-2.24.2/gobject/gsignal.c line 3038
#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 /scratch/build-area/glib2.0-2.24.2/glib/gmain.c line 1960
#31 IA__g_main_context_dispatch
at /scratch/build-area/glib2.0-2.24.2/glib/gmain.c line 2513
#32 g_main_context_iterate
at /scratch/build-area/glib2.0-2.24.2/glib/gmain.c line 2591
#33 IA__g_main_loop_run
at /scratch/build-area/glib2.0-2.24.2/glib/gmain.c line 2799
#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 15503] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


----------- .xsession-errors ---------------------
Loaded configuration: 
ask_confirmation = False
show_notification = True
preset = paste.debian.net
open_browser = False
Create Settings object...
Reading configuration from GConf...
Loaded configuration: 
ask_confirmation = False
show_notification = True
preset = paste.debian.net
open_browser = False
(epiphany-browser:15503): GLib-GObject-WARNING **: invalid cast from `PrefsDialog' to `PdmDialog'
41	../sysdeps/unix/sysv/linux/waitpid.c: 没有那个文件或目录.
--------------------------------------------------

Comment 1 Akhil Laddha 2011-01-12 04:06:43 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 ***