GNOME Bugzilla – Bug 489409
crash in Document Viewer: viewing a file opend fro...
Last modified: 2007-10-23 14:26:20 UTC
Version: 0.8.2 What were you doing when the application crashed? viewing a file opend from firefox Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 363053056 vsize: 363053056 resident: 48599040 share: 17727488 rss: 48599040 rss_rlim: 18446744073709551615 CPU usage: start_time: 1193147058 rtime: 743 utime: 675 stime: 68 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evince' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912496353712 (LWP 3055)] [New Thread 1084229968 (LWP 3056)] (no debugging symbols found) 0x000000326fe0d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 172225
Thread 1 (Thread 46912496353712 (LWP 3055))
----------- .xsession-errors (1486 sec old) --------------------- localuser:dgoldber being added to access control list SESSION_MANAGER=local/unix:/tmp/.ICE-unix/2618 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. 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. 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. --------------------------------------------------
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 415714 ***