GNOME Bugzilla – Bug 452132
crash in Epiphany Web Browser: navigating to website
Last modified: 2007-06-29 10:08:44 UTC
Version: 2.18.2 What were you doing when the application crashed? navigating to website Distribution: Fedora Core release 6 (Zod) 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: blagCanyon Icon Theme: really-little-guys Memory status: size: 167608320 vsize: 167608320 resident: 23621632 share: 3104768 rss: 23621632 rss_rlim: 4294967295 CPU usage: start_time: 1183073147 rtime: 1 utime: 0 stime: 1 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 -1208633632 (LWP 932)] (no debugging symbols found) 0x0024e402 in __kernel_vsyscall ()
+ Trace 144516
Thread 1 (Thread -1208633632 (LWP 932))
----------- .xsession-errors --------------------- Xlib: unexpected async reply (sequence 0x29877)! Xlib: unexpected async reply (sequence 0x29879)! Xlib: unexpected async reply (sequence 0x29887)! Xlib: unexpected async reply (sequence 0x29e99)! (epiphany:32368): Gtk-CRITICAL **: gtk_widget_set_size_request: assertion `width >= -1' failed Xlib: sequence lost (0x3008d > 0x30075) in reply type 0x6! MozPlugger: Error: Failed to execute m4. MozPlugger: Error: Failed to execute m4. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x4d specified for 0x120fb7e (). AFD changed from -2 to -1 AFD changed from -2 to -1 MozPlugger: Error: Failed to execute m4. (epiphany:933): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed --------------------------------------------------
*** Bug 452133 has been marked as a duplicate of this bug. ***
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 ***