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 489649 - crash in Epiphany Web Browser: Closing epiphany
crash in Epiphany Web Browser: Closing epiphany
Status: RESOLVED DUPLICATE of bug 351972
Product: epiphany
Classification: Core
Component: General
2.18.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-24 02:09 UTC by mikeamtz
Modified: 2007-10-24 15:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mikeamtz 2007-10-24 02:09:39 UTC
Version: 2.18.3

What were you doing when the application crashed?
Closing epiphany


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 204967936 vsize: 204967936 resident: 112234496 share: 37453824 rss: 112234496 rss_rlim: 4294967295
CPU usage: start_time: 1193154639 rtime: 157543 utime: 129528 stime: 28015 cutime:7 cstime: 578 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208883488 (LWP 20292)]
[New Thread -1245078640 (LWP 20294)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208883488 (LWP 20292))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
    from /usr/lib/firefox-2.0.0.5/libgtkembedmoz.so
  • #4 <signal handler called>
  • #5 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #6 Accessibility_Registry_registerApplication
    from /usr/lib/libspi.so.0
  • #7 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #8 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #9 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #10 gnome_accessibility_module_init
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #11 ??
    from /usr/lib/firefox-2.0.0.5/components/libaccessibility.so
  • #12 ??
    from /usr/lib/firefox-2.0.0.5/components/libaccessibility.so
  • #13 ??
    from /usr/lib/firefox-2.0.0.5/components/libaccessibility.so
  • #14 atk_get_root
    from /usr/lib/libatk-1.0.so.0
  • #15 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #16 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #17 ??
    from /usr/lib/gtk-2.0/modules/libatk-bridge.so
  • #18 ??
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #21 ??
    from /usr/lib/gtk-2.0/modules/libgail.so
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #24 ??
    from /lib/libgobject-2.0.so.0
  • #25 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #26 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #27 gtk_tree_model_row_changed
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 gtk_list_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #29 gtk_list_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #30 ??
  • #31 ??
  • #32 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #33 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #34 ??
    from /lib/libgobject-2.0.so.0
  • #35 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #36 g_signal_emit_by_name
    from /lib/libgobject-2.0.so.0
  • #37 ??
  • #38 ??
    from /usr/lib/firefox-2.0.0.5/components/libembedcomponents.so
  • #39 ??
    from /usr/lib/firefox-2.0.0.5/components/libnecko.so
  • #40 ??
    from /usr/lib/firefox-2.0.0.5/components/libnecko.so
  • #41 PL_HandleEvent
    from /usr/lib/firefox-2.0.0.5/libxpcom_core.so
  • #42 PL_ProcessPendingEvents
    from /usr/lib/firefox-2.0.0.5/libxpcom_core.so
  • #43 ??
    from /usr/lib/firefox-2.0.0.5/libxpcom_core.so
  • #44 NS_ShutdownXPCOM_P
    from /usr/lib/firefox-2.0.0.5/libxpcom_core.so
  • #45 NS_ShutdownXPCOM
    from /usr/lib/firefox-2.0.0.5/libxpcom.so
  • #46 ??
    from /usr/lib/firefox-2.0.0.5/libgtkembedmoz.so
  • #47 ??
    from /usr/lib/firefox-2.0.0.5/libgtkembedmoz.so
  • #48 gtk_moz_embed_pop_startup
    from /usr/lib/firefox-2.0.0.5/libgtkembedmoz.so
  • #49 ??
  • #50 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #51 ??
  • #52 ??
  • #53 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #54 ??
  • #55 g_object_unref
    from /lib/libgobject-2.0.so.0
  • #56 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #57 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #58 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #59 ??
    from /lib/libglib-2.0.so.0
  • #60 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #61 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #62 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (91416 sec old) ---------------------
[wmv3 @ 0x62b21a4]Extra data: 8 bits left, value: 0
[wmv3 @ 0x62b21a4]Extra data: 8 bits left, value: 0
Not multiplexed? 0xbe
Not multiplexed? 0xba
Not multiplexed? 0xbe
Not multiplexed? 0xba
Not multiplexed? 0xbe
Not multiplexed? 0xba
Not multiplexed? 0xbe
Not multiplexed? 0xba
Not multiplexed? 0xbe
Not multiplexed? 0xba
Not multiplexed? 0xc0
Not multiplexe
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2007-10-24 15:54:18 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 351972 ***