GNOME Bugzilla – Bug 575985
crash in Document Viewer:
Last modified: 2009-03-19 17:15:00 UTC
Version: 2.22.2 What were you doing when the application crashed? Distribution: Debian squeeze/sid 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: Amaranth Icon Theme: Amaranth Memory status: size: 119873536 vsize: 119873536 resident: 98246656 share: 14282752 rss: 98246656 rss_rlim: 18446744073709551615 CPU usage: start_time: 1237481773 rtime: 1184 utime: 1038 stime: 146 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' [Thread debugging using libthread_db enabled] [New Thread 0xb6a25970 (LWP 8213)] [New Thread 0xb6880b90 (LWP 8215)] 0xb7f0c424 in __kernel_vsyscall ()
+ Trace 213628
Thread 1 (Thread 0xb6a25970 (LWP 8213))
----------- .xsession-errors (8 sec old) --------------------- (gnome-terminal:5868): Vte-WARNING **: No handler for control sequence `device-control-string' defined. ** 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 0x2c00003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e00020 (Archive Ma) 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 574050 ***