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 391279 - crash in Epiphany Web Bookmarks:
crash in Epiphany Web Bookmarks:
Status: RESOLVED DUPLICATE of bug 372545
Product: epiphany
Classification: Core
Component: General
2.17.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-12-31 12:32 UTC by Tomasz Sterna
Modified: 2006-12-31 14:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Tomasz Sterna 2006-12-31 12:32:56 UTC
Version: 2.17.4

What were you doing when the application crashed?



Distribution: Gentoo Base System version 1.12.8
Gnome Release: 2.17.2 2006-12-20 (Gentoo)
BugBuddy Version: 2.17.3

System: Linux 2.6.16-suspend2-r13 #4 PREEMPT Wed Dec 20 23:29:00 CET 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: No
Accessibility: Enabled

Memory status: size: 331120640 vsize: 0 resident: 331120640 share: 0 rss: 103915520 rss_rlim: 0
CPU usage: start_time: 1167565213 rtime: 0 utime: 10744 stime: 0 cutime:10179 cstime: 0 timeout: 565 it_real_value: 0 frequency: 1

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1476872496 (LWP 19765)]
[New Thread -1734636656 (LWP 9158)]
[New Thread -1726243952 (LWP 9157)]
[New Thread -1666151536 (LWP 9156)]
[New Thread -1709458544 (LWP 1159)]
[New Thread -1717851248 (LWP 1158)]
[New Thread -1657758832 (LWP 19781)]
[New Thread -1503257712 (LWP 19775)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1476872496 (LWP 19765))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 870
  • #3 <signal handler called>
  • #4 IA__g_logv
    at gmessages.c line 503
  • #5 IA__g_log
    at gmessages.c line 517
  • #6 IA__g_return_if_fail_warning
  • #7 gail_menu_item_ref_child
    at gailmenuitem.c line 250
  • #8 atk_object_ref_accessible_child
    at atkobject.c line 668
  • #9 spi_atk_bridge_signal_listener
    at bridge.c line 1050
  • #10 signal_emit_unlocked_R
    at gsignal.c line 2406
  • #11 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #12 IA__g_signal_emit_by_name
    at gsignal.c line 2267
  • #13 menu_item_remove_gtk
    at gailsubmenuitem.c line 379
  • #14 IA__g_cclosure_marshal_VOID__OBJECT
    at gmarshal.c line 636
  • #15 IA__g_closure_invoke
    at gclosure.c line 490
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #17 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #18 IA__g_signal_emit
    at gsignal.c line 2243
  • #19 IA__gtk_container_remove
    at gtkcontainer.c line 991
  • #20 gtk_widget_dispose
    at gtkwidget.c line 6875
  • #21 IA__g_object_run_dispose
    at gobject.c line 573
  • #22 IA__gtk_object_destroy
    at gtkobject.c line 403
  • #23 IA__gtk_widget_destroy
    at gtkwidget.c line 2168
  • #24 update_node
    at gtkuimanager.c line 2588
  • #25 update_node
    at gtkuimanager.c line 2571
  • #26 update_node
    at gtkuimanager.c line 2571
  • #27 update_node
    at gtkuimanager.c line 2571
  • #28 update_node
    at gtkuimanager.c line 2571
  • #29 do_updates
    at gtkuimanager.c line 2613
  • #30 ephy_css_menu_rebuild
    at ephy-css-menu.c line 210
  • #31 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #32 IA__g_closure_invoke
    at gclosure.c line 490
  • #33 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #34 IA__g_signal_emit_valist
    at gsignal.c line 2199
  • #35 IA__gtk_signal_emit
    at gtksignal.c line 360
  • #36 EmbedProgress::OnStateChange
    at EmbedProgress.cpp line 107


----------- .xsession-errors (24733 sec old) ---------------------
Watching directory /home/smoku/Archive/docs/developer.gnome.org/gnome-ui/hitsquad (total watches = 2227)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/gnome-ui/helping (total watches = 2228)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/gnome-ui/images (total watches = 2229)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/gnome-ui/links (total watches = 2230)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/gnome-ui/software (total watches = 2231)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/gnome-ui/news (total watches = 2232)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/feature/archive (total watches = 2233)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/feature/current (total watches = 2234)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/tools/repo (total watches = 2235)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/news/summary (total watches = 2236)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/arch/imaging (total watches = 2237)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/arch/widgets (total watches = 2238)
Watching directory /home/smoku/Archive/docs/developer.gnome.org/arch/component (total watches = 2239)
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2006-12-31 14:23:31 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 372545 ***