GNOME Bugzilla – Bug 547166
crash in Document Viewer: selecting text
Last modified: 2008-08-10 19:56:49 UTC
Version: 2.22.2 What were you doing when the application crashed? selecting text Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-2-amd64 #1 SMP Thu Aug 30 23:43:59 UTC 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: SphereCrystal Memory status: size: 380755968 vsize: 380755968 resident: 42192896 share: 14716928 rss: 42192896 rss_rlim: 18446744073709551615 CPU usage: start_time: 1218373650 rtime: 291 utime: 213 stime: 78 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b804c0732b0 (LWP 3528)] [New Thread 0x40800950 (LWP 3530)] (no debugging symbols found) 0x00002b804763e5ff in waitpid () from /lib/libpthread.so.0
+ Trace 204944
Thread 1 (Thread 0x2b804c0732b0 (LWP 3528))
----------- .xsession-errors (67 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) Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3600003 (Evince Doc) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (<unknown>:2673): GStreamer-CRITICAL **: gst_segment_clip: assertion `segment->format == format' failed (<unknown>:2673): GStreamer-CRITICAL **: gst_segment_clip: assertion `segment->format == format' failed --------------------------------------------------
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 501673 ***