GNOME Bugzilla – Bug 417483
crash in Epiphany Web Browser: closing the browser.
Last modified: 2007-03-12 15:51:08 UTC
Version: 2.16.3 What were you doing when the application crashed? closing the browser. Distribution: Fedora Core release 6 (Zod) Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc) BugBuddy Version: 2.16.0 System: Linux 2.6.19-1.2911.6.5.fc6 #1 SMP Sun Mar 4 16:05:34 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 653074432 vsize: 653074432 resident: 49127424 share: 26501120 rss: 49127424 rss_rlim: -1 CPU usage: start_time: 1173710658 rtime: 602 utime: 558 stime: 44 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496342320 (LWP 4735)] (no debugging symbols found) 0x0000003bf4a0d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 117997
Thread 1 (Thread 46912496342320 (LWP 4735))
----------- .xsession-errors (7 sec old) --------------------- Initializing nautilus-image-converter extension Initializing nautilus-open-terminal extension seahorse nautilus module initialized (gnome-panel:3087): GConf-WARNING **: Directory `/apps/panel/toplevels/bottom_panel_screen1/screen' was not being monitored by GConfClient 0x8b6e40 (gnome-panel:3087): GConf-WARNING **: Directory `/apps/panel/toplevels/top_panel_screen1/screen' was not being monitored by GConfClient 0x8b6e40 Loading "installonlyn" plugin Select the application/window to dock with button1. Click any other button to abort (epiphany:5211): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed ** (bug-buddy:5212): WARNING **: Could not load icon for Open Folder --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers? *** This bug has been marked as a duplicate of 413350 ***