GNOME Bugzilla – Bug 423736
crash in Epiphany Web Browser:
Last modified: 2007-03-28 14:00:21 UTC
Version: 2.16.3 What were you doing when the application crashed? 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.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 649150464 vsize: 649150464 resident: 45457408 share: 26374144 rss: 45457408 rss_rlim: -1 CPU usage: start_time: 1175090127 rtime: 433 utime: 396 stime: 37 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 46912496342336 (LWP 4624)] (no debugging symbols found) 0x0000003bf4a0d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 122915
Thread 1 (Thread 46912496342336 (LWP 4624))
----------- .xsession-errors --------------------- VO: [xv] 592x336 => 592x336 Planar YV12 A: 0.2 V: 0.0 A-V: 0.212 ct: 0.000 1/ 1 ??% ??% ??,?% 0 0 A: 0.2 V: 0.0 A-V: 0.193 ct: -0.001 2/ 2 ??% ??% ??,?% 1 0 A: 0.2 V: 0.1 A-V: 0.153 ct: -0.0 A: 12.5 V: 12.5 A-V: 0.001 ct: -0.009 313/313 6% 4% 1.6% 3 0 A: 12.5 V: 12.5 A-V: 0.004 ct: -0.008 314/314 6% 4% 1.6% 3 0 A: 12.6 V: 12.6 A-V: 0.007 ct: -0.0 Exiting... (Quit) (epiphany:4583): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed (bug-buddy:4584): Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed ** (bug-buddy:4584): WARNING **: Could not load icon for Open Folder (epiphany:4654): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed ** (bug-buddy:4655): 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 ***