GNOME Bugzilla – Bug 501952
crash in Document Viewer:
Last modified: 2007-12-06 10:48:31 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.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: Permissive Accessibility: Disabled GTK+ Theme: Bluecurve-Gnome Icon Theme: gnome Memory status: size: 74518528 vsize: 74518528 resident: 38518784 share: 18542592 rss: 38518784 rss_rlim: 4294967295 CPU usage: start_time: 1196910370 rtime: 284 utime: 268 stime: 16 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 -1208256800 (LWP 10824)] [New Thread -1210356848 (LWP 10825)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 180910
Thread 1 (Thread -1208256800 (LWP 10824))
----------- .xsession-errors (150 sec old) --------------------- Error (55996): Illegal character <76> in hex string Error (55997): Illegal character <0b> in hex string Error (56000): Illegal character <ae> in hex string Error (56002): Illegal character <7d> in hex string Error (56003): Illegal character <10> in hex string Error (56004): Illegal character <69> in hex string Error (56005): Illegal character <ee> in hex string Error (56006): Illegal character <bc> in hex string Error (56007): Illegal character <e0> in hex string Error (56008): Illegal character <e2> in hex string Error (56009): Illegal character <b4> in hex string Error (56010): Illegal character <87> in hex string Error (56011): Illegal character <d7> in hex string Error (56013): Illegal character <fa> in hex string ...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 456255 ***