GNOME Bugzilla – Bug 414747
crash in Epiphany Web Browser: Just starting and then s...
Last modified: 2007-03-05 08:35:36 UTC
Version: 2.16.3 What were you doing when the application crashed? Just starting and then shutting epiphany down causes this error. 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.fc6 #1 SMP Sat Feb 10 15:16:31 EST 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 70101000 Selinux: Enforcing Accessibility: Disabled Memory status: size: 521928704 vsize: 521928704 resident: 36077568 share: 21737472 rss: 36077568 rss_rlim: -1 CPU usage: start_time: 1173055029 rtime: 78 utime: 68 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany' Using host libthread_db library "/lib64/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 46912496383280 (LWP 22720)] 0x00000038a6a0d96f in waitpid () from /lib64/libpthread.so.0
+ Trace 115879
Thread 1 (Thread 46912496383280 (LWP 22720))
----------- .xsession-errors --------------------- ** (bug-buddy:22561): WARNING **: Couldn't load icon for Open Folder warning: the debug information found in "/usr/lib/debug//usr/bin/epiphany.debug" does not match "/usr/bin/epiphany" (CRC mismatch). (epiphany:22607): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed ** (bug-buddy:22608): WARNING **: Couldn't load icon for Open Folder warning: the debug information found in "/usr/lib/debug//usr/bin/epiphany.debug" does not match "/usr/bin/epiphany" (CRC mismatch). (epiphany:22733): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed ** (bug-buddy:22734): 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 ***