GNOME Bugzilla – Bug 485737
crash in Document Viewer: i had just opened a fold...
Last modified: 2007-10-11 14:16:29 UTC
Version: 0.8.2 What were you doing when the application crashed? i had just opened a folder on the desktop and while browsing files inside it, I clicked on the one i wanted to see .( 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.4-65.fc7 #1 SMP Tue Aug 21 21:50:50 EDT 2007 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Glider Icon Theme: gnome Memory status: size: 361521152 vsize: 361521152 resident: 30347264 share: 15015936 rss: 30347264 rss_rlim: 18446744073709551615 CPU usage: start_time: 1192110690 rtime: 88 utime: 60 stime: 28 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 46912496349616 (LWP 5287)] [New Thread 1084229968 (LWP 5288)] (no debugging symbols found) 0x000000371760d97f in waitpid () from /lib64/libpthread.so.0
+ Trace 169502
Thread 1 (Thread 46912496349616 (LWP 5287))
----------- .xsession-errors (137866 sec old) --------------------- (gnome-panel:2951): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2951): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2951): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid (gnome-panel:2951): Gtk-WARNING **: Icon cache '/usr/share/icons/hicolor/icon-theme.cache' is invalid ...Too much output, ignoring rest... --------------------------------------------------
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 ***