GNOME Bugzilla – Bug 420368
crash in Epiphany Web Browser: closing epiphany
Last modified: 2007-03-20 10:55:35 UTC
Version: 2.16.3 What were you doing when the application crashed? closing epiphany 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.2925.fc6 #1 SMP Sat Mar 10 18:38:39 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: No Accessibility: Disabled Memory status: size: 445747200 vsize: 445747200 resident: 35786752 share: 20979712 rss: 35786752 rss_rlim: -1 CPU usage: start_time: 1174351982 rtime: 241 utime: 220 stime: 21 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 46912496358704 (LWP 3347)] (no debugging symbols found) 0x000000348d20d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 120219
Thread 1 (Thread 46912496358704 (LWP 3347))
----------- .xsession-errors --------------------- ** (rhythmbox:3316): WARNING **: No property volume.disc.capacity on device with id /org/freedesktop/Hal/devices/volume_part_1_size_392544256 Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. ** (gnome-system-monitor:3480): WARNING **: SELinux was found but is not enabled. Unable to connect to yum-updatesd. Please ensure that the yum-updatesd package is installed and that the service is running. (epiphany:3545): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed ** (bug-buddy:3546): WARNING **: Couldn't 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 ***