GNOME Bugzilla – Bug 545925
crash in Epiphany Web Browser: browsing http;//www.rens...
Last modified: 2008-08-02 17:25:34 UTC
Version: 2.22.3 What were you doing when the application crashed? browsing http;//www.rense.coim. i clicked on the larger button Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 188284928 vsize: 188284928 resident: 94236672 share: 26284032 rss: 94236672 rss_rlim: 4294967295 CPU usage: start_time: 1217623877 rtime: 51106 utime: 44250 stime: 6856 cutime:1 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b69720 (LWP 17014)] [New Thread 0xb2ebeb90 (LWP 17109)] [New Thread 0xb3f98b90 (LWP 17097)] [New Thread 0xb4f9ab90 (LWP 17096)] [New Thread 0xb4799b90 (LWP 17095)] [New Thread 0xb5b5cb90 (LWP 17049)] (no debugging symbols found) 0xb7f26424 in __kernel_vsyscall ()
+ Trace 204397
----------- .xsession-errors (1657 sec old) --------------------- ** 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-browser:17014): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (epiphany-browser:17014): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (epiphany-browser:17014): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3a00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. --------------------------------------------------
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 525357 ***