GNOME Bugzilla – Bug 573331
crash in Epiphany Web Browser: Nothing in particular th...
Last modified: 2009-02-27 00:24:07 UTC
Version: 2.22.3 What were you doing when the application crashed? Nothing in particular that I am aware of, just regular use such as swithing windows, switching tabs etc. Distribution: Debian 5.0 Gnome Release: 2.22.3 2008-09-18 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Lush Icon Theme: Lush Memory status: size: 266477568 vsize: 266477568 resident: 115269632 share: 32182272 rss: 115269632 rss_rlim: 4294967295 CPU usage: start_time: 1235486967 rtime: 578779 utime: 535663 stime: 43116 cutime:0 cstime: 11 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/epiphany-browser' [Thread debugging using libthread_db enabled] [New Thread 0xb6aa6700 (LWP 2627)] [New Thread 0xac5feb90 (LWP 21225)] [New Thread 0xaeefeb90 (LWP 2722)] [New Thread 0xb0040b90 (LWP 2721)] [New Thread 0xb1072b90 (LWP 2643)] [New Thread 0xb1927b90 (LWP 2642)] [New Thread 0xb2128b90 (LWP 2641)] [New Thread 0xb2929b90 (LWP 2639)] [New Thread 0xb59b1b90 (LWP 2628)] 0xb7f42424 in __kernel_vsyscall ()
+ Trace 212942
Thread 1 (Thread 0xb6aa6700 (LWP 2627))
----------- .xsession-errors (955 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) ** 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) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3000003 (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 543589 ***