GNOME Bugzilla – Bug 485647
crash in Document Viewer:
Last modified: 2007-10-31 23:33:49 UTC
Version: 0.8.2 What were you doing when the application crashed? 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.5-76.fc7 #1 SMP Thu Aug 30 13:08:59 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Fedora Memory status: size: 598102016 vsize: 598102016 resident: 152039424 share: 24338432 rss: 152039424 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192021208 rtime: 24707 utime: 23336 stime: 1371 cutime:3010 cstime: 327 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 46912498578304 (LWP 19740)] [New Thread 1094719824 (LWP 20767)] [New Thread 1084229968 (LWP 19741)] (no debugging symbols found) 0x000000361d8c82e6 in poll () from /lib64/libc.so.6
+ Trace 169437
Thread 3 (Thread 1084229968 (LWP 19741))
----------- .xsession-errors --------------------- warning: .dynamic section for "/usr/lib64/libSM.so.6" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libICE.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/usr/lib64/libbonoboui-2.so.0" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libcups.so.2" is not at the expected address warning: difference appears to be caused by prelink, adjusting expectations warning: .dynamic section for "/usr/lib64/libgnutls.so.13" is not at the expected address (wrong library or version mismatch?) --------------------------------------------------
*** This bug has been marked as a duplicate of 316907 ***