Bug 436266 – 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 436266 - crash in Epiphany Web Bookmarks:


Summary:	crash in Epiphany Web Bookmarks:


Status:	RESOLVED DUPLICATE of bug 350988

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Marco Pesenti Gritti

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-05-06 05:09 UTC by wgraue
Modified:	2007-05-06 12:00 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description wgraue 2007-05-06 05:09:40 UTC

Version: 2.16.1

What were you doing when the application crashed?



Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 161177600 vsize: 0 resident: 161177600 share: 0 rss: 69111808 rss_rlim: 0
CPU usage: start_time: 1178426875 rtime: 0 utime: 11531 stime: 0 cutime:10969 cstime: 0 timeout: 562 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228814672 (LWP 5146)]
[New Thread -1318339680 (LWP 5833)]
[New Thread -1271923808 (LWP 5152)]
[New Thread -1263207520 (LWP 5151)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 132648

Thread 1 (Thread -1228814672 (LWP 5146))

#0 __kernel_vsyscall
#1 waitpid
from /lib/tls/i686/cmov/libc.so.6
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 gtk_moz_embed_get_title
from /usr/lib/firefox/libgtkembedmoz.so
#4 <signal handler called>
#5 __kernel_vsyscall
#6 raise
from /lib/tls/i686/cmov/libc.so.6
#7 abort
from /lib/tls/i686/cmov/libc.so.6
#8 g_logv
from /usr/lib/libglib-2.0.so.0
#9 g_log
from /usr/lib/libglib-2.0.so.0
#10 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#11 _gtk_file_chooser_default_new
from /usr/lib/libgtk-x11-2.0.so.0
#12 _gtk_file_chooser_embed_should_respond
from /usr/lib/libgtk-x11-2.0.so.0
#13 _gtk_file_chooser_embed_set_delegate
from /usr/lib/libgtk-x11-2.0.so.0
#14 _gtk_file_chooser_embed_should_respond
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_file_chooser_dialog_new
from /usr/lib/libgtk-x11-2.0.so.0
#16 g_cclosure_marshal_VOID
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_dialog_response
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#24 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#25 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#26 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#27 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#28 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#31 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#32 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#33 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#34 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 main
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2007-05-06 12:00:15 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 350988 ***