GNOME Bugzilla – Bug 449553
crash in Epiphany Web Browser: Closing Epiphany
Last modified: 2007-06-20 22:48:44 UTC
Version: 2.18.2 What were you doing when the application crashed? Closing Epiphany Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Fedora Memory status: size: 218542080 vsize: 218542080 resident: 84574208 share: 34725888 rss: 84574208 rss_rlim: 4294967295 CPU usage: start_time: 1182363092 rtime: 6015 utime: 5800 stime: 215 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209133344 (LWP 2581)] [New Thread -1264108656 (LWP 2704)] [New Thread -1348080752 (LWP 2633)] [New Thread -1337590896 (LWP 2632)] [New Thread -1231807600 (LWP 2585)] [New Thread -1221317744 (LWP 2582)] (no debugging symbols found) 0x0062b402 in __kernel_vsyscall ()
+ Trace 142483
Thread 1 (Thread -1209133344 (LWP 2581))
----------- .xsession-errors --------------------- error getting update info: Cannot open/read repomd.xml file for repository: fedora ** Message: <info> You are now connected to the wireless network ''. ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) ** Message: GetValue variable 1 (1) ** Message: GetValue variable 2 (2) (epiphany:2707): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 415544 ***