GNOME Bugzilla – Bug 541877
crash in Document Viewer:
Last modified: 2008-07-07 13:20:21 UTC
Version: 2.22.2 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 303960064 vsize: 303960064 resident: 29855744 share: 13869056 rss: 29855744 rss_rlim: 18446744073709551615 CPU usage: start_time: 1215434487 rtime: 155 utime: 137 stime: 18 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 "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2afec3c0b860 (LWP 11583)] [New Thread 0x40800950 (LWP 11584)] (no debugging symbols found) 0x00002afebee91336 in poll () from /lib/libc.so.6
+ Trace 202223
Thread 2 (Thread 0x40800950 (LWP 11584))
----------- .xsession-errors (1341 sec old) --------------------- (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 (npviewer.bin:10574): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libclearlooks.so: wrong ELF class: ELFCLASS64 sh: acroread: command not found --------------------------------------------------
*** This bug has been marked as a duplicate of 541876 ***