GNOME Bugzilla – Bug 427721
crash in Epiphany Web Browser: I just shut it off.
Last modified: 2007-04-09 01:34:02 UTC
Version: 2.16.3 What were you doing when the application crashed? I just shut it off. 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.fc6xen #1 SMP Mon Mar 19 11:17:46 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 706969600 vsize: 706969600 resident: 114434048 share: 34615296 rss: 114434048 rss_rlim: -1 CPU usage: start_time: 1176043434 rtime: 19580 utime: 18761 stime: 819 cutime:0 cstime: 5 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 46912496436544 (LWP 16297)] (no debugging symbols found) 0x0000003ea880d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 126154
Thread 1 (Thread 46912496436544 (LWP 16297))
----------- .xsession-errors (6 sec old) --------------------- (nautilus:3916): Eel-WARNING **: Trying to add a callback for preferences/background_color that already exists. (nautilus:3916): Eel-WARNING **: Trying to add a callback for preferences/background_filename that already exists. (realplay.bin:18367): Gdk-WARNING **: gdk_propery-get(): invalid length 0 (realplay.bin:18383): Gdk-WARNING **: gdk_propery-get(): invalid length 0 (realplay.bin:18404): Gdk-WARNING **: gdk_propery-get(): invalid length 0 (realplay.bin:18425): Gdk-WARNING **: gdk_propery-get(): invalid length 0 (epiphany:18428): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed ** (bug-buddy:18429): 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 ***