GNOME Bugzilla – Bug 548929
crash in Epiphany Web Browser: Pressed CTRL+ to increas...
Last modified: 2008-08-23 13:30:13 UTC
Version: 2.22.3 What were you doing when the application crashed? Pressed CTRL+ to increase size of fonts on page. 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: 154161152 vsize: 154161152 resident: 57225216 share: 25251840 rss: 57225216 rss_rlim: 4294967295 CPU usage: start_time: 1219353417 rtime: 1073 utime: 1011 stime: 62 cutime:0 cstime: 0 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 0xb6b04700 (LWP 7566)] [New Thread 0xb2e5bb90 (LWP 7574)] [New Thread 0xb3f2cb90 (LWP 7572)] [New Thread 0xb4f2eb90 (LWP 7571)] [New Thread 0xb472db90 (LWP 7570)] [New Thread 0xb5aeeb90 (LWP 7567)] (no debugging symbols found) 0xb7ee6424 in __kernel_vsyscall ()
+ Trace 205511
----------- .xsession-errors (629 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:7566): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (epiphany-browser:7566): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed ** (epiphany-browser:7566): 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 0x3200003 (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 ***